← Docs

Docs · Connector reference

Asana connector reference

Operations, inputs, troubleshooting, and questions for the Asana connection. Policy decides each change before the credential is resolved, and the action record carries the result.

Set up and verify the Asana connection

  1. Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
  2. Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
  3. Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
  4. Configure approval for sensitive changes, review the destination and inputs, and check the result in the provider before expanding the workflow.

Information your agent can use

ResourceRecord identityStart withPage coverage
ProjectsgidTop levelCursor
TasksgidTop levelCursor
WorkspacesgidTop levelCursor
UsersgidTop levelCursor
TeamsgidWorkspacesCursor
Workspace membershipsgidWorkspacesCursor
Workspace projectsgidWorkspacesCursor
Project tasksgidWorkspace projectsCursor
Record identity
Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with
Resolve the parent identifier first.
Cursor
Cursor pagination. Continue from the returned cursor; an initial page is not a complete inventory.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Action
Can change provider state; review the target and inputs, then retain the result to avoid repeating completed work.
Read
Retrieves information; check the returned scope and identifiers before use.
OperationEffectApprovalProvider permissionsInputs
Task CreateActionApproval requiredtasks:write7
Task UpdateActionApproval requiredtasks:write7
Project CreateActionApproval requiredprojects:write4
Project UpdateActionApproval requiredprojects:write4
Task GetReadBy policytasks:read1
Task RenameActionApproval requiredtasks:read, tasks:write2

Inputs by operation

Task Create Action · approval required
Inputs for Asana Task Create
InputRequirementAccepted value
assigneeOptionalstringMinimum characters: 1Maximum characters: 64
due_onOptionalstring
idempotency_keyOptionalstringMinimum characters: 1Maximum characters: 256
nameRequiredstringMinimum characters: 1Maximum characters: 255
notesOptionalstringMaximum characters: 10000
projectsOptionalarrayMaximum items: 20
workspaceRequiredstringMinimum characters: 1Maximum characters: 64
Task Update Action · approval required
Inputs for Asana Task Update
InputRequirementAccepted value
assigneeOptionalstringMinimum characters: 1Maximum characters: 64
due_onOptionalstring
idempotency_keyOptionalstringMinimum characters: 1Maximum characters: 256
nameOptionalstringMinimum characters: 1Maximum characters: 255
notesOptionalstringMaximum characters: 10000
projectsOptionalarrayMaximum items: 20
task_gidRequiredstringMinimum characters: 1Maximum characters: 64
Project Create Action · approval required
Inputs for Asana Project Create
InputRequirementAccepted value
idempotency_keyOptionalstringMinimum characters: 1Maximum characters: 256
nameRequiredstringMinimum characters: 1Maximum characters: 255
notesOptionalstringMaximum characters: 10000
workspaceRequiredstringMinimum characters: 1Maximum characters: 64
Project Update Action · approval required
Inputs for Asana Project Update
InputRequirementAccepted value
idempotency_keyOptionalstringMinimum characters: 1Maximum characters: 256
nameOptionalstringMinimum characters: 1Maximum characters: 255
notesOptionalstringMaximum characters: 10000
project_gidRequiredstringMinimum characters: 1Maximum characters: 64
Task Get Read
Inputs for Asana Task Get
InputRequirementAccepted value
task_gidRequiredstringMinimum characters: 1Maximum characters: 64
Task Rename Action · approval required
Inputs for Asana Task Rename
InputRequirementAccepted value
dataRequiredobject
task_gidRequiredstringMinimum characters: 1Maximum characters: 64

When the Asana task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the bearer token connection and its access to the specific resource; a successful connection does not establish access to every object.

Resolve parent resources first: Workspaces, Workspace projects. A matching display name is not enough for a child lookup.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

A change is waiting or failed

Check whether the call awaits approval, was rejected by policy, lacks an input, or failed at the provider, and after a timeout inspect the destination before repeating a write.

See how an action proceeds and how to review an approval.

Questions about the Asana connector

Can I use my existing agent with Asana?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Asana?

This connector supports 2 actions, listed on its overview page. Configure a connection and choose the tools and provider permissions your task needs; an available action is not permission for every agent to run it, and Deixic policy and any required approval still apply to calls through the gateway.

What do I need to connect Asana?

Prepare Personal or OAuth access token; the connection uses Bearer token, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Asana keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.