About the Asana category

anon99371720 · August 14, 2023, 7:48am

Put topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.

Extra information

System documentation: Asana API Reference

Connector package documentation

1. Setting up HTTP Client Asana

1.1 Steps

In the Alumio Dashboard, go to Clients → HTTP Clients. Create a new HTTP Client and select “Asana HTTP Client” as the HTTP Client.
We support Personal access token authentication and Oauth Authentication
(For more information, see Asana Authentication Reference)
(Please press the button Grant access to Asana when using oauth)
You can optionally enable logging of request to get the log of the authentication.
Save the HTTP Client for use.

2. Subscribing to Entities from Asana

2.1 Steps

Go to Connections → Incoming and create a new incoming configuration and select “Asana Subscriber” as the subscriber.
Select the entity you want to subscribe to from Asana.
Add any request parameters needed to subscribe to the entity.
You can optionally add a transformer to transform the request parameters into something you will request from Asana.
You can also optionally enable pagination to allow Alumio fetches paginated entities.
Select the Asana HTTP Client to use.

2.2 General Concept

We follow Asana documentation on building this connector, so you can easily use the connector based on Asana API Reference.

Entity

The entity you want to subscribe to Asana. Please refer to the entities from Asana API Reference.

Request Parameters

These are the parameters you can provide to get the needed entity based on the Asana API Reference.

Please look at the example below on how to fill path field when subscribing “Get teams in a workspace” entity.

Based on the documentation, we can see that the end point require “workspace_gid” as a path. That is why we set the “workspace_gid” inside the path key in the Request Parameters.

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0

Alumio will then make a request to Asana with the URL /workspaces/1204588700815234/teams

HTTP Client

The HTTP Client configuration you will use to access Asana.

3. Publishing Entity to Asana

3.1 Steps

Go to Connections → Outgoing, create a new outgoing configuration and select “Asana Publisher” as the publisher.
Select the Action that you want the publisher to perform with the data.
Select the Asana entity you want the data to be published to.
You can optionally add any path data to the request on the key path.
You can optionally add any query data to the request on the key query.
You can optionally add any payload data to the request on the key payload.
Select the HTTP Client to use.

3.2 General Concept

Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration), though you can also add or modify payload using the Request Transformer.

Action

Currently, we support Create (HTTP POST method), Update (HTTP PUT method), Patch (HTTP PATCH method), and Delete (HTTP DELETE method) on submitting data to Asana.

Entity

We support publishing to most Asana endpoints.
Please refer to Asana API Reference page.

For example, we want to create a team. Please select “Create” for the Action then “Create a team” as the entity of the publisher.

Based on the documentation, we need to add data. So we put the data inside the payload key in the Alumio Data.

Alumio will send an API request to Asana with URL /teams

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0
Payload is the data contained within a request.