asana – OpenClaw Skill

---

name: asana description: "Integrate Asana with Clawdbot via the Asana REST API. Use when you need to list/search/create/update Asana tasks/projects/workspaces, or to set up Asana OAuth (authorization code grant) for a personal local-only integration (OOB/manual code paste)."

Asana (Clawdbot skill)

This skill is designed for a personal local-only Asana integration using OAuth with an out-of-band/manual code paste flow.

What this skill provides

• A small Node CLI to:
  • generate the Asana authorize URL
  • exchange an authorization code for access/refresh tokens
  • auto-refresh the access token
  • make basic API calls (e.g. /users/me, /workspaces, tasks)

Setup (OAuth, OOB/manual code)

0) Create an Asana app

In Asana Developer Console (My apps):

• Create app
• Enable scopes you will need (typical: tasks:read, tasks:write, projects:read)
• Set redirect URI to the OOB value (manual code):
  • urn:ietf:wg:oauth:2.0:oob

1) Provide credentials (two options)

Option A (recommended for Clawdbot): save to a local credentials file:

node scripts/configure.mjs --client-id "..." --client-secret "..."

This writes ~/.clawdbot/asana/credentials.json.

Option B: set environment variables (shell/session):

• ASANA_CLIENT_ID
• ASANA_CLIENT_SECRET

2) Run OAuth

From the repo root:

1. Print the authorize URL:

node scripts/oauth_oob.mjs authorize

2. Open the printed URL, click Allow, copy the code.
3. Exchange code and save tokens locally:

node scripts/oauth_oob.mjs token --code "PASTE_CODE_HERE"

Tokens are stored at:

• ~/.clawdbot/asana/token.json

Chat usage (support both explicit + natural language)

You can use either:

• Explicit commands: start the message with /asana ...
• Natural language: e.g. “list tasks assigned to me”

For Clawdbot, implement the mapping by translating the user request into the appropriate asana_api.mjs command.

Examples:

• /asana tasks-assigned → tasks-assigned --assignee me
• “list tasks assigned to me” → tasks-assigned --assignee me
• “list all tasks in <project>” → resolve <project> to a project gid, then tasks-in-project --project <gid>
• “list tasks due date from 2026-01-01 to 2026-01-15” → search-tasks --assignee me --due_on.after 2026-01-01 --due_on.before 2026-01-15

(Optional helper) scripts/asana_chat.mjs can map common phrases to a command skeleton.

Using the API helper

Sanity check (who am I):

node scripts/asana_api.mjs me

List workspaces:

node scripts/asana_api.mjs workspaces

Set a default workspace (optional):

node scripts/asana_api.mjs set-default-workspace --workspace <workspace_gid>

After that, you can omit --workspace for commands that support it.

List projects in a workspace (explicit):

node scripts/asana_api.mjs projects --workspace <workspace_gid>

List projects using the default workspace:

node scripts/asana_api.mjs projects

List tasks in a project:

node scripts/asana_api.mjs tasks-in-project --project <project_gid>

List tasks assigned to me (workspace required by Asana):

node scripts/asana_api.mjs tasks-assigned --workspace <workspace_gid> --assignee me

Or using the default workspace:

node scripts/asana_api.mjs tasks-assigned --assignee me

Search tasks (advanced search):

node scripts/asana_api.mjs search-tasks --workspace <workspace_gid> --text "release" --assignee me
# also supports convenience: --project <project_gid>

View a task:

node scripts/asana_api.mjs task <task_gid>

Mark a task complete:

node scripts/asana_api.mjs complete-task <task_gid>

Update a task:

node scripts/asana_api.mjs update-task <task_gid> --name "New title" --due_on 2026-02-01

Comment on a task:

node scripts/asana_api.mjs comment <task_gid> --text "Update: shipped"

Create a task:

node scripts/asana_api.mjs create-task --workspace <workspace_gid> --name "Test task" --notes "from clawdbot" --projects <project_gid>

Notes / gotchas

• OAuth access tokens expire; refresh tokens are used to obtain new access tokens.
• If you later want multi-user support, replace OOB with a real redirect/callback.
• Don’t log tokens.

clawdbot-asana-skill

Asana OAuth (local-only) + task/project commands for Clawdbot.

This repo contains a small Asana skill (an AgentSkill folder) that you can:

• use locally on your Clawdbot host
• publish/share so other Clawdbot users can install and run it

It uses Asana OAuth 2.0 Authorization Code Grant with an out-of-band (OOB) / manual code paste redirect URI:

• urn:ietf:wg:oauth:2.0:oob

No public callback server is required.

---

What you get

Commands (via Node scripts):

• Auth helpers: generate authorize URL, exchange code, refresh access token
• List workspaces, list projects, list tasks
• View task, update task, mark complete, comment

Tokens and config are stored locally under:

• ~/.clawdbot/asana/credentials.json (client id + secret)
• ~/.clawdbot/asana/token.json (OAuth tokens)
• ~/.clawdbot/asana/config.json (default workspace)

---

Prerequisites

• Node.js 22+
• An Asana account with access to the workspace(s) you want

---

1) Create an Asana “Custom App” (Developer Console)

1. Open the Asana Developer Console:
   • https://app.asana.com/0/my-apps
2. Create a new app.
3. Distribution (important):
   • Your OAuth app must be available in the workspace the user is authorizing from.
   • In the developer console, configure Manage distribution so the app is available to the target workspace(s).
   • If distribution/workspace availability is misconfigured, authorization can fail even if the URL is correct.
4. OAuth settings:
   • Redirect URI:
     • urn:ietf:wg:oauth:2.0:oob
   • Copy the Client ID and Client Secret.

Scopes (must match what you request)

In the Asana Developer Console, go to OAuth → Permission scopes and enable the scopes you plan to request.

Important rules:

• The scopes you request in the authorize URL must be a subset of the scopes enabled in the console.
• If you request a scope that is not enabled, you’ll get a forbidden_scopes error.

Recommended “full task management” scope set:

• tasks:read tasks:write tasks:delete
• projects:read projects:write
• attachments:read attachments:write
• custom_fields:read custom_fields:write
• tags:read tags:write
• task_custom_types:read
• teams:read
• users:read
• workspaces:read

---

2) Configure credentials locally

Save your Asana OAuth client id/secret to a local file:

node scripts/configure.mjs \
  --client-id "YOUR_CLIENT_ID" \
  --client-secret "YOUR_CLIENT_SECRET"

This writes:

• ~/.clawdbot/asana/credentials.json

(Alternative: you can set ASANA_CLIENT_ID and ASANA_CLIENT_SECRET as environment variables, but the credentials file is recommended for Clawdbot.)

---

3) Authorize (OOB) and save tokens

3.1 Generate the authorize URL

node scripts/oauth_oob.mjs authorize \
  --scope "tasks:read tasks:write projects:read"

Open the printed URL in your browser, click Allow, then copy the code.

3.2 Exchange the code for tokens

node scripts/oauth_oob.mjs token --code "PASTE_CODE_HERE"

This writes:

• ~/.clawdbot/asana/token.json

---

4) (Optional) set a default workspace

List workspaces:

node scripts/asana_api.mjs workspaces

Set default workspace:

node scripts/asana_api.mjs set-default-workspace --workspace <workspace_gid>

This writes:

• ~/.clawdbot/asana/config.json

Commands that require a workspace will use the default if --workspace is omitted.

---

5) Common commands

Who am I:

node scripts/asana_api.mjs me

List projects (default workspace):

node scripts/asana_api.mjs projects

List tasks assigned to me:

node scripts/asana_api.mjs tasks-assigned --assignee me

List all tasks in a project:

node scripts/asana_api.mjs tasks-in-project --project <project_gid>

View a task:

node scripts/asana_api.mjs task <task_gid>

Mark complete:

node scripts/asana_api.mjs complete-task <task_gid>

Comment:

node scripts/asana_api.mjs comment <task_gid> --text "Update: shipped"

Advanced search (workspace required; default is used if set):

node scripts/asana_api.mjs search-tasks --text "release" --assignee me

---

Install into Clawdbot (local)

If your Clawdbot workspace is /Users/tony/clawd, copy the skill folder into:

• /Users/tony/clawd/skills/asana/

and restart Clawdbot if needed.

---

Notes

• Access tokens expire; the scripts will refresh using the refresh token.
• Keep credentials.json and token.json secret.
• If you publish this, document that users must configure distribution + scopes in the Asana console to match what they request in authorize.