Asana Connector Reference | MuleSoft Documentation
# Asana Connector Reference
Asana is a SaaS-based project management tool that enables teams of all sizes to manage their daily tasks, schedules, and deliverables.
## Connections
To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect.
This system requires the following credential information for its connections: 

Connection Name
    
Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others.
Only you can see the connection. Other users in your Composer app must create their own connections.
Older connections may expire if not regularly used. Asana sets the amount of time a connection remains valid. 

Username
    
The OAuth username that you use to log in to Asana. 

Password
    
The OAuth password that you use to log into Asana.
## Triggers
Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system.
Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds.
This system provides the following trigger options: 

New or updated task
    
Fires when a task is created or an existing task is updated.
### Polling Frequency
For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more API calls. For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day).
## Actions
After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to.
This system provides the following actions: 

Create new task
    
Creates a new task record.
When creating a new task record, store the values for both the User ID and the Task ID in the source system for use when updating task records. 

Update task
    
Returns the completed and updated task record. 

Add comment to card
    
Comment on a task to ask questions, provide extra information, or to offer insight. The comment appears on the card.
## Custom Fields
Custom fields are not supported. Using MuleSoft Composer, you can access standard field values for actions and triggers that you set in the Asana record.
## See Also
  * Mulesoft Composer: Overview
  * MuleSoft Composer: Getting Started
  * Composer Connector Reference
  * Knowledge Articles