You are here:
Asana Connector
Connect to an external Asana account. Perform tasks like creating projects or updating tasks. Use Asana as a data source (trigger) or a data target (action).
Required Editions
| View supported editions. |
| This feature requires the MuleSoft for Flow: Integration add-on. Professional Edition requires the API access add-on. To purchase, contact your Salesforce account executive. |
| MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive. |
Connections
To connect to a system, whether it's a data source or a data target, create a connection with that system's standard connection or with an existing external named credential. You can connect to multiple systems within a flow and reuse each connection. You can create connections in the Integrations tab or in Flow Builder.
Standard Connection
This system uses Bearer authentication.
Bearer authentication sends a header named Authorization with a value of Bearer and a token with every request.
This system requires this credential information for its connections.
| FIELD | DESCRIPTION |
|---|---|
| Connection Name | Enter a unique connection name that helps you remember the details of this connection. Salesforce hides the credentials after you create the connection. Reuse connections as needed. Anyone with the Manage Integration Connections permission can see and use all connections in the org. |
| Token | Enter the bearer token to use to authenticate the requests. For information about how to create the bearer token, refer to the external system's documentation. |
| URL | Enter the URL of your instance. |
Named Credential Connection
Select a pre-existing named credential from Setup to use for your external system connections.
Before connecting to your external system with a named credential, first create or use an existing authenticated named credential and external credential that is enabled for your users.
To ensure a successful connection for use in a flow, use only one principal for each named credential.
- Use the same name for the named credential and its related objects, such as the external credential and external authentication identity providers. Labels for these objects can differ.
- Assign the user creating the connection the required user permission for the principal. Without this permission, the connection test fails and the connection remains inactive.
When you create a connection with an existing named credential, note these behaviors:
- Manage the named credential’s read-only details in Setup, not the Integrations tab. On the Integrations tab, you can only edit the connection's Connection Name and Description.
- Perform reconnections for the named credential in Setup. The Reconnect button isn’t visible on the Details page.
- Delete associated named credentials in Setup. Deleting a connection doesn't remove the credential.
Triggers
A trigger initiates the flow when a specified event occurs. Triggers are important for automating business processes because they react to real-time data changes in various systems. For more information about triggers, refer to Create a Flow with a Connector as a Trigger.
These Asana triggers are available in Flow Builder.
- On Completed Task
- On New Comment
- On New Project
- On New Story
- On New Task
- On New or Update Project
- On New or Update Task
Actions
An action performs a specific task or operation within a target system. Use actions to automate tasks across different systems without manual intervention, based on conditions set in the flow. For more information about actions, refer to Create a Flow with a Connector as an Action.
These Asana actions are available in Flow Builder.
- Add Project To Task
- Add Tag To Task
- Add Users To A Project
- Create Project
- Create Tag
- Create Task
- Create Task With Custom FieldsNote
In the Project Ids field, enter the list of project IDs in the format
[\"id1\", \"id2\"]. - Get A Story
- Get Multiple Tags
- Get Projects
- Get Stories From A Task
- Get Tag By ID
- Get Task By ID
- Get Task Dependencies
- Get Task Dependents
- Get Tasks
- Get Tasks From A Project
- Get Teams In A Workspace
- Get User By ID
- Get Users
- Get Workspace By ID
- Get Workspaces
- Remove Users From A Project
- Search Tasks
- Set Task Dependencies
- Set Task Dependents
-
Update Task Custom Fields With ProjectIds
Note
This action supports schema resolution using project information instead of a sample task. The inputs are:
- projectIds (Used only for schema resolution)
- A constant list of project IDs must be provided by the user.
- These project IDs are used only for schema resolution.
- The keyword
ALLcan be provided to fetch custom fields from all projects. This option allows flow creation without requiring hardcoded projectId values for schema resolution.
- taskId (Task to be updated)
- A variable value can be provided by the user.
- The task identified by this ID will be updated with the user-provided data at runtime.
Use this action when a project or list of projects (or an allowed set of projects) is known at design time and can be used for schema resolution. Alternatively, the
ALLkeyword can be used to fetch custom fields from all projects, eliminating the need to specify any project values during design time.Note that:
- All custom fields will be fetched during schema resolution.
- At runtime, only the custom fields applicable to the provided taskId will be updated with the user-specified values.
- Any non-applicable custom fields will be ignored.
- projectIds (Used only for schema resolution)
-
Update Task Custom Fields With Sample TaskId
Note
This action supports schema resolution using a sample task while allowing a variable task ID at runtime. The inputs are:
- sampleTaskId (Used only for schema resolution)
- A constant value must be provided by the user.
- The Task GID must belong to the same project or an allowed set of projects as the runtime Task GID.
- This task ID is used exclusively for schema resolution.
- taskId (Task to be updated)
- A variable value can be provided by the user.
- The task identified by this ID will be updated with the user-provided data at runtime.
Use this action when custom fields need to be updated and a sample task ID belonging to the same project (or an allowed set of projects) as the runtime task can be easily provided. It is suitable for simple workflows where schema resolution can rely on a known task.
- sampleTaskId (Used only for schema resolution)
-
Update Task Standard Fields
Note
This action supports updates to standard (non-custom) fields only.
Use this action when no custom fields need to be updated. The action expects taskId as input. The taskId may be provided either as a variable or as a constant. No additional inputs are required for schema resolution, as only standard task fields are supported.
- Update Project
- Update Tag
-
Update Task
Note
This action supports updates to both standard and custom fields.
Use this action only when the taskId is provided as a hardcoded constant in the flow. Providing a hardcoded taskId enables schema resolution and is required for this action.
- Update Workspace
For information about specific limitations for connections and third-party connectors, see MuleSoft for Flow: Integration Limits & Considerations.
