Asana channel

See the Channel Catalog to see which Plans have access to this channel.

Asana is a workplace content management system (CMS) designed to help a wide range of companies achieve their organizational needs. Asana is customizable and allows users to break down projects into tasks and set clear goals for teams. It organizes work so teams know what to do, why it matters, and how to get it done. Visit Asana to learn more.

How to Connect

1. On the My pipelines page, select Create Pipeline.
2. Search for or select a step, and then select it to add it to the pipeline.
   When you add a step to a pipeline, it is added to the canvas of the pipeline designer.
3.  Expand the Connection section of the step, and add the required information.

For more information about connections, see How to connect to a channel.

Connect to Asana

1. Expand Asana in the list of channels on the right side of the page and click Connect to Asana.
2. In the pop-up window, click Connect to Asana.
   
3. You will be redirected to the Asana Login page and asked to log in with Google or with email and password.
   

How to reconnect

You may need to reconnect your account to a channel. Reasons may be (but not limited to):

• If you need to connect a different account.
• Authorization updates, such as a changed password.
• Editing the access rights that Pipelines has to the channel.

To reconnect:

1. Select a pipeline that already has this channel in it.
2. Open a step that contains this channel.
3. Under account, select Connect (or reconnect) and follow the process above, How to connect.
   

Steps

The steps you can use with Asana fall into four categories: Projects, Tasks, Comments, and Attachments.

Note: The Asana channel does’t have access to custom fields.

Note: You cannot use jinja expressions in trigger conditions unless explicitly specified as possible.

Limits

The file limit is 100MB.

To protect the stability of the API and keep it available to all users, Asana enforces multiple kinds of rate limiting. Requests that hit any of the rate limits will receive a 429 Too Many Requests response, which contains the standard Retry-After header indicating how many seconds the client should wait before retrying the request.

Note: Limits are allocated per authorization token. Different tokens have independent limits.

Standard Rate Limits

The standard rate limiter imposes a quota on how many requests can be made in a given window of time. Asana’s limits are based on minute-long windows, and differ depending on whether the domain is premium or not.

In addition, calls to the search API are limited to 60 requests per minute. The duplication endpoints are limited to 5 concurrent jobs.

Concurrent Request Limits

Asana also limits the number of requests being handled at any given instant.

For example, if you have 50 read requests in-flight and attempt to make another read request, the API will return a 429 Too Many Requests error. The read and write limits are independent of each other, so the number of read requests you make at one time will have no impact on the number of write requests you can make.

For more detailed information about Asana restrictions and limitations see Rate Limits.

Use Cases

The following are some example of using the Asana channel.

Asana tasks from Quickbase escalation app

We have an example app in Quickbase that we extract newly created records representing Pipelines channels to be developed and we want to create three corresponding tasks in an Asana project. In the following example we will show you step by step how to create this pipeline.

1. Drag and drop the Record Created Trigger from the Quickbase channel and attach it to the pipeline.
   
   Account - Select the Quickbase account for this trigger
   Table - The table containing the channels data
   Fields for Subsequent Steps - select the table fields (Name, Assignee, Due date, etc.)

2. Add a Create Task Action from the Asana channel and attach it to the pipeline.
   
   Account - select the Asana account to use for this trigger.
   Workspace - select the Asana Workspace for which you want to specify the trigger
   Project - select the Asana Project for which you want to specify the trigger
   
   You could populate the next fields with data from the object from the first step.
   
   Name - the name of the Task you want to create
   Notes - the description of the Task you want to create
   Due on - the due date of the task
   
   

3. Repeat the second step two more times for tasks about research and documentation. After triggering the pipeline the Activity log displays:
   
   And in the Asana project we can see that all tasks have been created:
   
   

Asana file transfer to Google Drive

It would be convenient every time we upload an attachment to a particular task to transfer that file to a folder in Google Drive. In the following example we will show you step by step how to create this pipeline.

1. Drag and drop the Attachment Uploaded Trigger from the Asana channel and attach it to the pipeline.
   
   Account - select the Asana account to use for this trigger.
   Workspace - select the Asana Workspace for which you want to specify the trigger.
   Project - select the Asana Project for which you want to specify the trigger.
   Fields for Subsequent Steps - select the table fields.

2. Click on Add conditions and select Task->Name, select equals and specify the task name that you want to transfer the files
   

3. Drag and drop the Upload a File Action from the Google Drive channel and attach it to the pipeline.
   
   Account - select the Google Drive account to use for this trigger.
   URL - drag and drop the File transfer handle field.
   Parent - select the Google Drive folder to which you want to transfer the files.
   Name - drag and drop the Name field for the task.
   
   After triggering the pipeline the Activity log displays:
   
   
   Now, when we upload an attachment, it is transferred to the specified Google Drive folder.