Skip to main content
The Asana Connector for ACP empowers Agentforce agents to manage projects, create and assign tasks, track progress, and automate workflow processes within your Asana workspace.

​
Purpose and Capabilities

This Connector provides tools to interact with Asana’s API for comprehensive project and task management:

​
Prerequisites

  • Asana Account: An active Asana workspace where the integration will be used.
  • Asana App:
    • A Personal Access Token (PAT) or OAuth 2.0 app must be configured in Asana.
    • For production use, OAuth 2.0 is recommended for better security and user management.
    • The app needs appropriate permissions to access projects, tasks, and users.
  • API Access: Asana API access with the necessary scopes for the operations you plan to perform.
  • Understanding of Asana Concepts: Familiarity with Asana terms like Workspaces, Teams, Projects, Tasks, Subtasks, Assignees, and GIDs (Global Identifiers).

​
Setup Instructions

  1. Create Asana App (OAuth 2.0 - Recommended):
    • Go to https://app.asana.com/0/developer-console and click “Create New App”.
    • Name your app (e.g., “ACP Connector”) and provide a description.
    • Configure OAuth settings with appropriate redirect URIs.
    • Note down your Client ID and Client Secret.
  2. Or Generate Personal Access Token (Development/Testing):
    • Go to https://app.asana.com/0/my-apps and click “Personal Access Token”.
    • Generate a new token and securely store it.
    • Note: PATs have full access to your account and should only be used for development.
  3. Configure Permissions:
    • Ensure your app has access to the workspaces and teams where you’ll be managing tasks.
    • For OAuth apps, configure the appropriate scopes during the authorization flow.
  4. Test API Access:
    • Use the Asana API to test basic operations like listing workspaces or creating a test task.
    • Verify that your authentication is working correctly.

​
Authentication

The Asana Connector supports two authentication methods:

​
Personal Access Token (PAT)

​
Common Use Cases

  • Task Management: Create and assign tasks based on customer interactions or system events.
  • Project Tracking: Monitor project progress and update stakeholders automatically.
  • Workflow Automation: Trigger task creation when specific conditions are met in other systems.
  • Reporting Integration: Sync task completion data with other business systems.
  • Content Review Workflows: Create review tasks for marketing content, social media posts, or documentation.

​
Rate Limits and Best Practices

  • Rate Limits: Asana enforces rate limits (typically 1500 requests per minute per app).
  • Batch Operations: Use batch endpoints when available to reduce API calls.
  • Webhook Integration: Consider using Asana webhooks for real-time updates instead of polling.
  • Error Handling: Implement proper retry logic for transient errors.
  • Data Validation: Validate GIDs and required fields before making API calls.

​
Security Considerations

  • Token Security: Store access tokens securely and rotate them regularly.
  • Scope Limitation: Request only the minimum required permissions for your use case.
  • Data Privacy: Be mindful of sensitive information in task descriptions and comments.
  • Audit Logging: Maintain logs of API operations for security and compliance purposes.