Overview
The Asana connector for Flows360 provides a universal API for integrating Asana's project and task management capabilities into your existing business processes.
Key capabilities:
- Task Automation: Automate the creation and updating of Asana tasks based on triggers from external systems. For example, create a new Asana task when an opportunity stage is updated in your CRM or a new issue is created in a development tool like Jira.
- Bi-directional Sync: Keep Asana projects, tasks, and other records synchronized with other project management or operational systems. This ensures a unified, real-time view of work across different teams and platforms.
- Custom Logic and Mapping: Implement custom field mappings and conditional logic to tailor the integration to your specific operational workflows.
- Data Consistency: Eliminate manual data entry and reduce errors by automating the flow of information between Asana and the rest of your application ecosystem.
This connector enables robust, bi-directional integrations that streamline project management and improve data accuracy across your organization.
Capability summary
Authentication
Auth method: OAuth 2.0
Required scopes
default
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Task | Yes | Yes | Represents individual to-do items, which can be assigned to users and have due dates. Supports creation, updates, and lookups. |
| File | Yes | Yes | Represents files attached to Asana tasks or projects. Supports uploading (write) and retrieving (read) file metadata and content. |
| Record | Yes | Yes | A generic object representing other Asana records like Projects or Comments. Requires specifying the object type during the API call. |
Supported actions
| Action | Description |
|---|---|
| create_record | Creates a new record for a supported object, such as a Task. |
| update_record | Updates an existing record for a supported object using its unique identifier. |
| list_records | Retrieves a list of records for a supported object, with optional filtering and pagination. |
Setup steps
- Navigate to Connections: In the Flows360 admin panel, go to the "Connections" section and click "Add Connection".
- Select Asana: Choose "Asana" from the list of available providers.
- Authorize Access: You will be redirected to the Asana authentication screen. Log in to your Asana account if you are not already.
- Grant Permissions: Review the requested permissions and click "Allow" to grant Flows360 access to your Asana workspace.
- Confirmation: Once authorized, you will be redirected back to Flows360. Your Asana connection is now active and ready to be used in your integration flows.
Limitations
- API Rate Limits: The connector is subject to Asana's API rate limits. High-volume workflows may require strategic design, such as using batch operations or implementing retries with exponential backoff, to avoid exceeding these limits. Refer to the official Asana API documentation for current rate limit details.
- Custom Field Support: While standard Asana fields are fully supported, custom fields may require specific mapping and configuration within your flow logic. Ensure that custom field GIDs are correctly identified and used in your integration steps.
- Webhook Latency: Event-driven flows relying on Asana webhooks may experience a brief delay between an event occurring in Asana and the webhook payload being delivered to Flows360.
Troubleshooting
Why are my custom fields not updating correctly?
Ensure you are using the correct unique identifier (GID) for the custom field, not its display name. You can find the GID by inspecting the field via the Asana API or in the field customization settings. The data type of the value you are sending must also match the custom field's type (e.g., text, number, enum).
I am receiving a '429 Too Many Requests' error. What should I do?
This error indicates that you have exceeded Asana's API rate limits. To resolve this, optimize your flows by using batch operations to update multiple records in a single call. If batching is not possible, introduce a delay or implement an exponential backoff strategy in your flow logic to reduce the frequency of API calls.