Asana

Read tasks and post comments from workflows - a session-tracker adapter, not a full Asana automation surface.

Partially implemented. Asana is a session tracker adapter: workflows bound to an Asana project can read a task (issue.read) and post comments (issue.add_comment), and agent sessions get Asana task context. There are no Asana task-creation, update, search, custom-field, section, or assignee nodes, and no inbound Asana webhook ingestion. Status updates (issue.update_status) are not supported - Asana tasks are binary completed/open with no state vocabulary to map.

The Asana integration lets workflows read Asana tasks and post comments (stories), so an Asana-tracked project can drive agent sessions the same way a Linear-tracked one does.

What you can do

Read a task - issue.read returns the task in canonical form (identifier, title, status, description)
Post a comment - issue.add_comment adds a story to the task
Agent session context - sessions on Asana-bound projects resolve the task's identifier, title, and status

What you cannot do (yet)

Create, update, search, or close tasks from workflow nodes
Update task status - the generic issue.update_status node rejects Asana bindings (supportsStatusUpdate: false); Asana's binary completed/open model has no rich state vocabulary to map against a workflow state machine
Set custom fields, sections, assignees, or due dates
Trigger workflows from Asana events - there is no inbound Asana webhook ingestion (a downstream event-router adapter exists, but nothing produces Asana events into it)

Connect Asana

Create a Personal Access Token

Go to app.asana.com/0/my-apps (or Profile photo → My settings → Apps)
Scroll to Personal access tokens and click + New access token
Token name: e.g., "Rensei"
Click Create and copy the token immediately - it is shown only once

The token grants the same access as your Asana account within the workspaces you belong to.

Add the token to your org's credentials

Store the token as an org credential with provider type Asana. The tracker adapter resolves the org's Asana credential by provider type at call time - there is no dedicated Asana connect card with workspace discovery.

Bind a Rensei project to Asana

Go to Project Settings → Trackers
Select Asana as the issue tracker
Enter the tracker path for your Asana project, e.g. asana:project:1234567890

Once bound, the generic session-tracker nodes (issue.read, issue.add_comment) on workflows in this project route to Asana.

Workflow nodes

Node	Supported on Asana	Description
`issue.read`	Yes	Fetch the task in canonical issue form
`issue.add_comment`	Yes	Post a comment (story) on the task
`issue.update_status`	No	Rejected - Asana has no mappable state vocabulary

Post a comment with agent output:

- id: post_comment
  type: action
  nodeId: issue.add_comment
  config:
    issueId: "{{ $trigger.data.issueId }}"
    body: |
      Agent update:

      {{ steps.agent.output.summary }}

Credential and permissions

Credential field	Value
Type	Personal Access Token (PAT) or OAuth bearer token
Format	Long alphanumeric string
Scope	All workspaces and projects the Asana user belongs to
Stored	AES-GCM encrypted at the org level

The token grants the same access as your Asana user account. Tasks you cannot see in Asana will not be readable from workflows.

Token rotation

Asana PATs do not expire by default. If you need to rotate:

Go to app.asana.com/0/my-apps → Personal access tokens
Click Revoke next to the old token
Create a new token
Update the org credential with the new token value

Limitations

Limitation	Detail
Read + comment only	No task CRUD, search, custom fields, sections, assignees, or due-date nodes
No status updates	`issue.update_status` is unsupported on Asana bindings
No inbound webhooks	Asana events cannot trigger workflows; the integration is outbound-only
Single org credential	One Asana credential per org (resolved by provider type)

Troubleshooting

"Authentication failed"

Verify your token is still valid in app.asana.com/0/my-apps
Tokens are shown only once at creation; if you lost it, revoke and create a new one
Update the org's Asana credential with the new token

"Task not found"

Verify the task GID (numeric ID) is correct
Ensure your Asana user account has access to the task's project

Next steps

Project trackers - Bind Asana to a Rensei project
Workflow triggers - Use GitHub and Linear events to drive workflows that read/comment on Asana tasks
Agent cards - Assign agents to Asana-tracked projects

On this page