asana

A lightweight node CLI over the Asana REST API for workspaces, projects, tasks, search, comments, updates and completion. The good decision is the documented auth priority: --token or ASANA_PAT, then ~/.openclaw/asana/config.json with a pat, then an OAuth token — so you can script it without an OAuth dance while OAuth stays available for advanced cases via configure.mjs.

Use case: An agent that triages and updates its own task queue in Asana

This skill exposes asana workspaces, projects and tasks through a compact command line wrapper built on the asana rest interface. Authentication is personal access token first, with oauth retained for advanced setups. ## What it does - Lists workspaces and projects so tasks can be addressed by identifier. - Searches, creates, updates and completes tasks. - Reads and writes task comments. - Reports which account the current credentials resolve to before any change is made. - Resolves credentials in a fixed priority order: a command flag, then the environment, then a config file, then an oauth token file. - Stores local state under the asana directory inside the openclaw config tree. ## When it is the wrong choice The wrapper covers task level work well, but it is not a sync engine. There is no conflict resolution, no webhook handling and no incremental cursor, so a mirrored local copy of asana will quietly drift. A personal access token is also scoped to the human who created it, which makes it a poor fit for a shared service account rotation policy. A team already standardised on a client library or a webhook pipeline gains little from this layer. It is also built for modest write volume. Scripted task operations fit well; bulk data movement does not. ```bash # confirm which identity the current credentials carry node scripts/asana_api.mjs me # enumerate the workspaces that identity can see node scripts/asana_api.mjs list-workspace # one time setup writes config into the openclaw asana folder ``` ## Working notes - Confirm which identity the token resolves to before changing tasks. - Keep the config file permissions tight, since it stores a long lived token.