← Back to Skills Marketplace
byungkyu

Asana

by byungkyu · GitHub ↗ · v1.2.6 · MIT-0
cross-platform ✓ Security Clean
19228
Downloads
6
Stars
0
Active Installs
15
Versions
Install in OpenClaw
/install asana-api
Description
Asana API integration with managed OAuth. Access tasks, projects, workspaces, users, and manage webhooks. Use this skill when users want to manage work items, track projects, or integrate with Asana workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn an Asana connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an Asana action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Asana examples; they add no Asana capability - Asana is not an event source, a trigger cannot read Asana data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you intend to let Maton access your Asana account. Prefer OAuth over API keys, start with read-only/list operations, review the exact account and connection before writes, and be especially careful with functions, triggers, destinations, and webhooks because they can keep running or forwarding data until removed.
Capability Assessment
ℹ Credentials
The skill needs network access and stores OAuth tokens through the operating system credential store; raw API-key HTTP is documented only as a fallback when the CLI cannot be installed.
ℹ Install Mechanism
Installation uses the Maton CLI via pinned npm or Homebrew instructions, with optional pinned SDK packages. This is expected for the integration, though users should install only from the documented Maton sources.
✓ Instruction Scope
The instructions default to read/list operations, require confirmation for connection creation and every write, treat external content as untrusted, and limit non-Asana trigger references to user-requested automation contexts.
ℹ Persistence & Privilege
OAuth connections, hosted functions, triggers, destinations, and Asana webhooks can persist beyond a single session, but the artifact repeatedly discloses this and requires user approval, scoping, and cleanup.
ℹ Purpose & Capability
The skill's capabilities match its stated purpose: Asana OAuth access for tasks, projects, workspaces, users, webhooks, and optional Maton automation. It includes write and webhook actions, but marks writes and persistent forwarding as requiring explicit approval.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install asana-api
  3. After installation, invoke the skill by name or use /asana-api
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.6
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.5
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.4
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.3
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.2
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.1
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.2.0
Appendix drops the raw curl example; SkillSpector 2.11 static findings addressed across the reference; HTTP blocks replaced with maton api
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.6
- Removed the file `skill-card.md`. - No changes were made to the skill functionality or documentation aside from this file removal.
v1.0.5
- Added CLI commands as examples throughout documentation for common tasks (listing, creating, updating, deleting tasks and projects). - Included installation instructions for Maton CLI via NPM and Homebrew. - Documented CLI-based authentication and connection management workflows alongside Python examples. - Clarified how to specify active connections and pass connection IDs for multi-account setups. - No API changes; documentation now caters to both CLI and Python workflows for improved accessibility.
v1.0.4
- Switched all endpoint references from gateway.maton.ai and ctrl.maton.ai to api.maton.ai for unified API access. - Updated Quick Start and all example requests to use the new base URL (https://api.maton.ai). - Clarified connection management instructions and URLs; connections are now managed at https://api.maton.ai. - Added a specific security & permissions section requiring explicit user approval for all write operations. - Improved documentation clarity and emphasized always specifying the Maton-Connection header when using multiple connections. - Removed the LICENSE.txt file.
v1.0.3
- Added clawdbot metadata with emoji and required environment variable (MATON_API_KEY) in SKILL.md. - No functional or documentation changes to the Asana API integration itself.
v1.0.2
No changes detected in this release. - Version 1.0.2 is functionally identical to the previous version.
v1.0.1
- Added a note in the description recommending the use of the api-gateway skill for other third-party apps. - Replaced all shell/bash `curl` API usage examples with equivalent Python code snippets using `urllib.request`, making interacting with the API in Python easier. - Updated the authentication instructions to reference shell variable syntax (`$MATON_API_KEY`). - No changes to API endpoints or core functionality.
v1.0.0
- Major update: Migration from local/personal OAuth CLI integration to a managed cloud API gateway and centralized connection flow. - Removed all local scripts, code, and markdown reference files for CLI-based Asana usage. - Documentation rewritten for Maton cloud gateway: all API calls routed via https://gateway.maton.ai/asana/ with automatic OAuth and streamlined API key auth. - Added instructions and examples for managing Asana OAuth connections through the Maton control panel at https://ctrl.maton.ai. - Provided modern API usage examples for accessing and managing Asana tasks, projects, workspaces, and users via HTTP and curl. - Introduced support for specifying connections and multiple account management via headers. - Added complete quick start, authentication, and API reference sections for ease of use.
Metadata
Slug asana-api
Version 1.2.6
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 15
Frequently Asked Questions

What is Asana?

Asana API integration with managed OAuth. Access tasks, projects, workspaces, users, and manage webhooks. Use this skill when users want to manage work items, track projects, or integrate with Asana workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn an Asana connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an Asana action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Asana examples; they add no Asana capability - Asana is not an event source, a trigger cannot read Asana data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 19228 downloads so far.

How do I install Asana?

Run "/install asana-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Asana free?

Yes, Asana is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Asana support?

Asana is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Asana?

It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.6.

💬 Comments