Asana

This skill provides a dependency-free Node.js CLI that calls the Asana REST API (v1) using a Personal Access Token (PAT).

• - Script: INLINECODE0
• Auth: ASANA_PAT (preferred) or INLINECODE2
• Output: JSON only (stdout), suitable for agents and automation

Setup

1. 1. Create an Asana PAT in your Asana account (Developer Console is not required for PAT usage).
2. Provide the token to OpenClaw/Clawdbot as ASANA_PAT.

Common injection patterns

• - Shell env (local testing):

INLINECODE4

• - OpenClaw config (recommended): set skills.entries.asana.apiKey (or env.ASANA_PAT) so the secret is injected only for the agent run.

Configure via OpenClaw CLI (recommended)

This is the safest way to set the PAT because it keeps secrets out of prompts and ad-hoc shell history.

Recommended (apiKey → ASANA_PAT):

CODEBLOCK0

INLINECODE7 is a convenience field: for skills that declare metadata.openclaw.primaryEnv, OpenClaw injects apiKey into that env var for the agent run (this skill’s primary env is ASANA_PAT).

Alternative (explicit env):

CODEBLOCK1

Verify what is stored:

CODEBLOCK2

Remove a stored token:

CODEBLOCK3

Important: sandboxed runs

When a session is sandboxed, skill processes run inside Docker and do not inherit the host environment. In that case, skills.entries.*.env/apiKey applies to host runs only.

Set Docker env via:

• - agents.defaults.sandbox.docker.env (or per-agent agents.list[].sandbox.docker.env)
• or bake the env into your sandbox image

First calls (sanity + discovery)

• - Who am I:

INLINECODE14

• - List workspaces:

INLINECODE15

• - (Recommended) Set a default workspace once:

INLINECODE16

ID resolution

When the user provides names (project/task/user), resolve to GIDs using one of:

• - typeahead --workspace <gid> --resource_type project|task|user --query "..." (fast, best default)
• INLINECODE18 (enumerate)
• INLINECODE19 (enumerate)

Avoid guessing a GID when multiple matches exist.

Core: tasks

List tasks assigned to a user (personal productivity)

INLINECODE20

List tasks in a project

INLINECODE21

Search tasks (Advanced Search API)

Canonical primitive: search-tasks (supports many filters; preferred over adding narrow “search helper” commands).

One-liner example (search within a project):

INLINECODE23

Useful filters:

• - --assignee me|<gid|email> (maps to assignee.any)
• INLINECODE26
• INLINECODE27 / INLINECODE28
• INLINECODE29 / INLINECODE30
• INLINECODE31 / INLINECODE32

Create / update / complete

• - Create:

INLINECODE33

• - Update:

INLINECODE34

• - Complete:

INLINECODE35

Project manager workflows

This skill supports the workflows commonly expected from a PM in Asana:

• - Keep a project brief up to date (upsert-project-brief)
• Write status updates (create-status-update)
• Work with timelines (start/due dates) and shift schedules safely
• Use custom fields as first-class metadata
• Interpret blockers and dependency graphs (project-blockers, dependencies, dependents)

Project brief

• - Read:

INLINECODE41

• - Upsert (create or update):

INLINECODE42

Status updates

• - Create:

INLINECODE43

• - List:

INLINECODE44

Sections and moving tasks

• - List sections:

INLINECODE45

• - Create section:

INLINECODE46

Add a task to a project

Command: INLINECODE47

Calls POST /tasks/{task_gid}/addProject and supports optional section placement and ordering.

Examples:

INLINECODE49

With section + ordering:

INLINECODE50

(--section, --insert_before, and --insert_after are optional; when provided they are passed through in the request body.)

Remove a task from a project

Command: INLINECODE54

Calls POST /tasks/{task_gid}/removeProject.

Example:

INLINECODE56

Custom fields

Custom fields are critical for reliable PM automation.

• - List a project’s custom fields:

INLINECODE57

• - Read a custom field definition:

INLINECODE58

• - Set task custom fields on create/update:

INLINECODE59

Notes:

• - For enums, the value is typically the enum option GID.
• For numbers, send a JSON number.

Rich text, mentions, and reliability

Asana rich text fields are XML-valid HTML fragments wrapped in a <body> root element. The API rejects invalid XML or unsupported tags.

Key points:

• - Use html_notes for task descriptions.
• Use html_text for comments/stories and status updates.
• Avoid unsupported tags like <p> and <br>; prefer literal newlines (\n) and <hr/> separators.
• For mentions/links, use <a data-asana-gid="..."></a> (or a self-closing <a .../>).

Mention notifications

Creating a mention link does not guarantee notification delivery if the user is not already assigned or following.

For reliable pings, do one of:

• - Assign the user first, then post the comment, OR
• Add the user as a follower, wait a few seconds, then post the comment

This skill supports the “add follower + wait” pattern:

INLINECODE69

Plain text comments (--text) do not create real @-mentions via the API; they remain plain text.

Attachments, uploads, and inline images

• - Upload a file attachment to a task:

INLINECODE71

• - Embed an existing image attachment inline (tasks + project briefs only):

INLINECODE72

Activity feed / “inbox-like” workflows

Asana does not provide a single universal “inbox” API for all notifications. The closest stable primitive is the Events endpoint scoped to a specific resource (project, task, etc.).

Use:

• - events --resource <gid> to pull incremental changes on a project (or a user's "My Tasks" project)
• The command stores a sync token locally so subsequent runs fetch only changes

Timeline shifting

• - Shift one task (optionally include subtasks):

INLINECODE74

• - Shift an entire project’s tasks:

INLINECODE75

Run with --dry_run true first, then re-run with --dry_run false.

Out of scope

• - Portfolios (premium) are intentionally omitted.
• “Bot personality” is not embedded here; configure behavior in your agent prompt.