Asana
✓ Official Vendor SpecProductivityTask Managementoauth2, bearer167 EndpointsREST
For Agents
Assign tasks, track project milestones, and query workload across teams. Supports goals, portfolios, custom fields, and real-time event subscriptions for 167 operations.
Use for: I need to create a task and assign it to a team member with a due date, List all tasks in a project that are overdue, Find all goals for a specific team and check their completion percentage, I want to add a subtask with dependencies to an existing task
Not supported: Does not handle team messaging, file storage, or time tracking - use for task and project management only.
Organize and track work across teams with projects, tasks, subtasks, custom fields, goals, and portfolios. Supports 167 endpoints covering task assignment, deadline management, progress tracking, and cross-team collaboration with granular permission controls and real-time event streaming.
Install Jentic One Beta
Connect the Asana to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Asana, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fasana.com%2Fasana" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fasana.com%2Fasana" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Asana API.
Assign tasks with due dates, dependencies, and custom field values across multiple projects
Track goal progress with metric targets and supporting work relationships
Build and reorder project timelines with milestones and section groupings
Query audit logs for workspace-level activity and compliance reporting
Attach files and link external resources to tasks for consolidated context
Subscribe to real-time events on projects and tasks via polling tokens
Instantiate projects from templates with pre-configured sections and task structures
Use Cases
Patterns agents use Asana API for, with concrete tasks.
★ AI Agent Task Automation
AI agents use the Asana API through Jentic to automate task creation, assignment, and status updates without manual intervention. An agent can search for the right operation by intent, load the task creation schema, and execute it in under a minute. This replaces manual copy-paste workflows and ensures tasks are created with correct custom fields, assignees, and project memberships from the start.
Create a task in project 'Sprint Backlog' assigned to user GID 12345 with due date 2026-05-15, custom field 'Priority' set to 'High', and add it to section 'To Do'
Cross-Team Project Tracking
Track work across multiple teams using portfolios and goals. The Asana API exposes 167 endpoints for querying project status, goal completion percentages, and portfolio item ordering. Teams get a single source of truth for who owns what, which milestones are at risk, and how individual tasks roll up into strategic objectives.
Retrieve all items in portfolio GID 67890 and return each project's completion percentage and owner
Sprint Planning and Backlog Management
Plan sprints by querying tasks across projects, filtering by custom fields like story points and priority, then reorganizing them into sections representing sprint phases. The API supports bulk task operations, section reordering, and project template instantiation so that repeatable sprint structures can be set up programmatically each cycle.
List all tasks in project 'Product Backlog' with custom field 'Story Points' greater than 3, then move them to section 'Sprint 12'
Compliance Audit Trail
Access workspace-level audit log events through the Asana API to track who changed what and when. The audit log endpoint returns timestamped records of task modifications, permission changes, and data exports. This supports SOC 2 and internal compliance requirements without requiring third-party logging tools.
Fetch audit log events for workspace GID 11111 from the last 7 days filtered to 'task_deleted' and 'project_archived' event types
Key Endpoints
167 endpoints — organize and track work across teams with projects, tasks, subtasks, custom fields, goals, and portfolios.
METHOD
PATH
DESCRIPTION
POST
/tasks
Create a new task
GET
/projects/{project_gid}/tasks
List tasks in a project
PUT
/tasks/{task_gid}
Update a task
GET
/goals
List goals in a workspace
POST
/goals/{goal_gid}/setMetricCurrentValue
Update goal metric progress
GET
/portfolios/{portfolio_gid}/items
List items in a portfolio
GET
/workspaces/{workspace_gid}/audit_log_events
Query workspace audit log
GET
/events
Poll for resource change events
POST
/tasks
Create a new task
GET
/projects/{project_gid}/tasks
List tasks in a project
PUT
/tasks/{task_gid}
Update a task
GET
/goals
List goals in a workspace
POST
/goals/{goal_gid}/setMetricCurrentValue
Update goal metric progress
GET
/portfolios/{portfolio_gid}/items
List items in a portfolio
GET
/workspaces/{workspace_gid}/audit_log_events
Query workspace audit log
GET
/events
Poll for resource change events
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Asana by hand means handling its OAuth 2.0 flow or Personal Access Token, refreshing tokens, and picking a path from over a hundred and sixty endpoints. Through Jentic you install once, import Asana from the API Directory, store the token once, and your agent calls it.
Permission scoping
Asana puts the resource gid in the URL path (/projects/{project_gid}/tasks, /tasks/{task_gid}), so a rule can pin your agent to one project or task. You choose the operations it may call, so updating a task is not included unless you add it alongside reads.
Credential isolation
Your Asana OAuth token or Personal Access Token is stored once, encrypted, by your own Jentic One instance and injected at execution time. Refresh tokens and raw keys never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a task in Asana with custom fields', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the Asana developer docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Asana API through Jentic.
What authentication does the Asana API use?
The Asana API supports OAuth 2.0 and Personal Access Tokens (PATs). OAuth 2.0 is used for app integrations requiring user consent, while PATs provide direct access for scripts and agents. Through Jentic, these credentials are stored encrypted in your Jentic One instance - agents receive scoped tokens without handling raw secrets. Configure access through Jentic One, the self-hosted execution layer.
Can I track goal progress with the Asana API?
Yes. The /goals endpoint lists goals filtered by workspace, team, or time period. Each goal has metric fields (current_number_value, target_number_value) that you update via POST /goals/{goal_gid}/setMetricCurrentValue. Supporting relationships link tasks and projects to goals so progress rolls up automatically.
What are the rate limits for the Asana API?
Asana enforces a rate limit of 1,500 requests per minute per Personal Access Token or OAuth token. Responses include X-RateLimit-Remaining headers. Batch operations on up to 10 actions per request are available via POST /batch to reduce call volume for bulk updates.
How do I create a task with custom fields through Jentic?
Search Jentic for 'create asana task with custom fields'. Jentic returns the POST /tasks operation schema including the custom_fields parameter (a map of field GID to value). Load the schema, populate assignee, due_on, projects, and custom_fields, then execute. The full flow takes under a minute compared to days of direct integration work.
Does the Asana API support real-time event streaming?
Asana provides a polling-based event system via GET /events. You supply a resource GID and a sync token; the API returns all changes since that token. This covers task creates, updates, deletes, and project membership changes. Poll intervals of 5-10 seconds are recommended for near-real-time sync.
Can I instantiate projects from templates via the API?
Yes. Use GET /project_templates to list available templates, then POST /project_templates/{project_template_gid}/instantiateProject with a name and team GID. The new project inherits all sections, tasks, custom fields, and rules from the template.
Can I limit what my agent is allowed to do with the Asana API?
Yes. Because you run Jentic One yourself, your own rules decide which Asana operations and credentials your agent may use. Asana carries the resource gid in the URL path, as in /projects/{project_gid}/tasks and /tasks/{task_gid}, so a rule can pin the agent to a single project or task. You also choose the exact operations it can call, so a write like updating a task is excluded unless you add it alongside the reads you allow.
GET STARTED