How to Connect Asana to OpenClaw

Asana personal access tokens (PATs) authenticate API requests as your Asana user. They grant access to all workspaces and projects your account can access — there is no per-token scope selection like Airtable's PAT system. Use a dedicated OpenClaw PAT rather than reusing tokens from other tools so you can revoke it independently if needed. Navigate to app.asana.com/-/developer_console (or go to My Profile > Apps > Manage Developer Apps > Personal Access Tokens in the Asana app). Click 'New Access Token'. Give it a name like 'OpenClaw Integration'. Click 'Create Token'. Asana shows the token once — copy it immediately. The token is a long alphanumeric string starting with `1/`. Store this token in OpenClaw's config as ASANA_ACCESS_TOKEN. It will be included as a Bearer token in all Asana API request headers.

1# Set your Asana PAT in OpenClaw config
2clawhub config set ASANA_ACCESS_TOKEN 1/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
3
4# Verify it is set
5clawhub config get ASANA_ACCESS_TOKEN
6
7# Test the connection — should return your Asana user info
8curl -H "Authorization: Bearer 1/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
9  "https://app.asana.com/api/1.0/users/me"

Asana uses numeric GIDs (globally unique identifiers) to reference all objects — workspaces, projects, tasks, users, sections, and custom fields. You need the workspace GID and project GID to make targeted API calls. **Workspace GID:** Call the `/workspaces` endpoint to list all workspaces your token has access to. Each workspace has a `gid` field — note the one you want to use. **Project GID:** You can find project GIDs in the Asana web URL. When you open a project in Asana, the URL contains the project GID: `https://app.asana.com/0/{PROJECT_GID}/...`. Or call the `/projects` endpoint filtered by workspace to list all projects. Store these GIDs in your OpenClaw config so workflows can reference them by name rather than looking them up each time.

1# List all workspaces
2curl -H "Authorization: Bearer 1/YOUR_TOKEN" \
3  "https://app.asana.com/api/1.0/workspaces"
4
5# List projects in a workspace
6curl -H "Authorization: Bearer 1/YOUR_TOKEN" \
7  "https://app.asana.com/api/1.0/projects?workspace=YOUR_WORKSPACE_GID"
8
9# Example: project GID from URL
10# https://app.asana.com/0/1234567890123456/...
11#                         ^^^^^^^^^^^^^^^^
12#                         This is the project GID

Add the Asana integration configuration to your OpenClaw config file. Store the workspace GID and project GIDs you identified in Step 2 under named keys so workflows can reference them by descriptive names. The ASANA_ACCESS_TOKEN is read automatically from your environment config — you do not need to repeat it in this file. The config below sets up named references to your most-used projects, making workflow configurations more readable.

1# ~/.openclaw/config.yaml
2integrations:
3  asana:
4    workspace_gid: "YOUR_WORKSPACE_GID"
5    default_assignee: "YOUR_USER_GID"  # Your Asana user GID (from /users/me response)
6    # Named project references
7    projects:
8      engineering_sprint: "PROJECT_GID_1"
9      product_backlog: "PROJECT_GID_2"
10      incoming_requests: "PROJECT_GID_3"
11    # Default task settings
12    defaults:
13      due_days_ahead: 7   # Default due date offset when not specified
14      notify_on_create: true

Test the integration by creating a task and then querying it. The Asana API uses POST to `/tasks` for task creation. The request body must include the project GID and task name at minimum — due date, assignee, notes, and custom fields are all optional. For reading tasks, GET `/tasks` with a `project` query parameter returns all tasks in that project. The response includes task GIDs, names, assignees, due dates, completion status, and custom field values. Asana's API paginates results at 100 items per page by default, returning an `offset` cursor for subsequent pages. Asana's API also supports task search via `/tasks/search` with filtering on assignee, completion status, due date range, project membership, and custom field values — more flexible than listing all tasks in a project.

1# Create a new task
2curl -X POST \
3  -H "Authorization: Bearer 1/YOUR_TOKEN" \
4  -H "Content-Type: application/json" \
5  "https://app.asana.com/api/1.0/tasks" \
6  -d '{
7    "data": {
8      "name": "Review Q2 budget proposal",
9      "projects": ["PROJECT_GID"],
10      "assignee": "YOUR_USER_GID",
11      "due_on": "2026-04-15",
12      "notes": "Deadline is end of April. Check with finance team first."
13    }
14  }'
15
16# List tasks in a project
17curl -H "Authorization: Bearer 1/YOUR_TOKEN" \
18  "https://app.asana.com/api/1.0/tasks?project=PROJECT_GID&completed_since=now"
19
20# Get a specific task by GID
21curl -H "Authorization: Bearer 1/YOUR_TOKEN" \
22  "https://app.asana.com/api/1.0/tasks/TASK_GID?opt_fields=name,due_on,assignee,completed,notes"

Beyond creating tasks, the integration supports updating task fields and adding comments (stories in Asana terminology). Use PUT or PATCH to update task properties — completion status, due date, assignee, notes, and custom fields. Use POST to `/tasks/{task_gid}/stories` to add comments to a task. For workflow-based integrations, the typical pattern is: create a task when work arrives, update it as it progresses, and mark it complete when done. This is achieved through three API calls at different stages of the workflow. Bulk task operations are not natively supported in Asana's API — each task requires its own request. For batch processing, add appropriate delays between requests to respect Asana's rate limit of 1,500 requests per 60 seconds (roughly 25/second). RapidDev recommends queuing bulk operations with a configurable rate limiter in your OpenClaw workflow config to prevent 429 errors under load.

1# Mark a task as complete
2curl -X PUT \
3  -H "Authorization: Bearer 1/YOUR_TOKEN" \
4  -H "Content-Type: application/json" \
5  "https://app.asana.com/api/1.0/tasks/TASK_GID" \
6  -d '{"data": {"completed": true}}'
7
8# Update task fields
9curl -X PUT \
10  -H "Authorization: Bearer 1/YOUR_TOKEN" \
11  -H "Content-Type: application/json" \
12  "https://app.asana.com/api/1.0/tasks/TASK_GID" \
13  -d '{
14    "data": {
15      "due_on": "2026-04-20",
16      "assignee": "NEW_ASSIGNEE_GID",
17      "notes": "Updated: priority escalated"
18    }
19  }'
20
21# Add a comment to a task
22curl -X POST \
23  -H "Authorization: Bearer 1/YOUR_TOKEN" \
24  -H "Content-Type: application/json" \
25  "https://app.asana.com/api/1.0/tasks/TASK_GID/stories" \
26  -d '{"data": {"text": "Automated update from OpenClaw: status changed to In Review"}}'