Menu
Mattering Automations connector

An Asana MCP that reads exactly like Asana's own API docs

Connect one Personal Access Token and Asana tasks, projects, sections, tags, comments, and attachments become workflow steps for visual automations and AI agents. Requests are wrapped in Asana's data envelope automatically, and responses arrive exactly as Asana sends them, so what your workflow sees matches what Asana documents.

42 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Asana MCP connector does

The Asana connector for Mattering Automations is 42 nodes across the REST API: workspaces, users, and teams, projects and their sections, the full task lifecycle (create, update, complete, subtasks, parents, followers, and multi-project membership), comments and activity stories, tags, URL attachments, custom field definitions for reading, premium task search, and the free typeahead lookup that turns names into gids.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer what is assigned to whom, which tasks in a project are overdue, and what changed in a task's activity stream, without anyone opening Asana.

Because Mattering is a work platform rather than middleware, Asana work lands somewhere useful by default. Mattering Productivity is the native task tool here, and for teams already living in Asana the natural pattern is a two-way sync: a scheduled sweep mirrors Asana tasks into a Mattering Productivity project, and changes made on the Mattering side flow back as task updates and comments, all on one canvas next to the rest of the work.

One design decision shapes everything downstream. Asana wraps every request body and every response in a data envelope, and the connector handles the two directions differently on purpose. On the way out, nodes assemble the plain fields you configure and add the wrapper automatically, so you never type it. On the way back, responses are surfaced exactly as Asana sends them: a task's name lives at data.data.name, list items at data.data[0], and the pagination token at data.next_page.offset. Nothing is unwrapped, so captured outputs match Asana's own documentation line for line.

One connection, three surfaces

  • Visual automations. Drag Asana nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Asana node, ready to drop on the canvas

42 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 22

Asana: Get Attachment

Get one attachment's metadata, including download_url and view_url. download_url values are short-lived signed links; use them promptly rather than storing them.

Asana: Get My User

Get the authenticated Asana user: gid, name, email, and the workspaces the token can reach. Needs no configuration, echoes no credential, and 401s on a bad token, so it doubles as the credential health check.

Asana: Get Project

Get one project's full record.

Asana: Get Tag

Get one tag's full record.

Asana: Get Task

Get one task's full record: name, notes, assignee, dates, completion, memberships (project + section), tags, followers, and custom field values.

Asana: Get Team

Get one team's full record.

Asana: Get User

Get one user's full record by gid, by email address, or with the string 'me' for the token owner.

Asana: Get Workspace

Get one workspace or organization record. is_organization tells you whether teams exist here and whether project creation needs a team gid.

Asana: List Attachments

List the attachments on a task (or project / project brief) as metadata records: name, host, and links. Never returns file bytes.

Asana: List Project Custom Field Settings

List which custom fields are attached to a project (each setting wraps the field definition with its enum options). Premium feature, like all custom-field surfaces.

Asana: List Project Sections

List the sections (board columns / list headings) of a project, in order. Section gids feed the add-task-to-section and task-list nodes.

Asana: List Projects

List projects, filtered to a workspace and optionally by archived state. Compact records by default; the gids feed every project-scoped node.

Asana: List Subtasks

List a task's subtasks in order. Compact records by default.

Asana: List Task Stories

List a task's activity stories: comments (resource_subtype comment_added) plus system events like assignments and completions. Filter to comments downstream via resource_subtype.

Asana: List Tasks

List tasks from one filter scope: a project, a section, OR an assignee combined with a workspace (Asana requires exactly one of those shapes). Compact records by default; use opt_fields for due dates, assignees, and completion state.

Asana: List Users

List user records, filtered to a workspace or a team. Returns compact records (gid, name) by default; add opt_fields like email to enrich. The gids feed assignee and follower fields.

Asana: List Workspace Custom Fields

List a workspace's custom field definitions, including enum options and their gids: exactly what you need to write custom_fields values on tasks. Custom fields are an Asana premium feature; free workspaces have little or nothing here.

Asana: List Workspace Tags

List the tags in a workspace. Tag gids feed the add/remove tag nodes and the task search tags.any filter.

Asana: List Workspace Teams

List the teams in a workspace that are visible to the token holder. Teams only exist in organizations (workspaces where is_organization is true); a plain workspace has none. Team gids are required to create projects in an organization.

Asana: List Workspaces

List the workspaces and organizations visible to the token. Almost every other Asana node wants a workspace gid from here.

Asana: Search Tasks

Full-text and filtered task search across a workspace. An Asana PREMIUM feature: free workspaces get 402 Payment Required. Results are eventually consistent (new changes take 10 to 60 seconds to appear) and NOT paginated: there is no next_page; narrow with filters or sort plus date-range windows instead. Many more filter operators (custom fields, *.not, *.all, created_at ranges) work via extra_query.

Asana: Typeahead Search

Find objects in a workspace by (partial) name, the same matcher as Asana's own search box: the everyday way to turn a name into a gid without premium task search. One resource type per call; single page of results, no pagination.

Action nodes 20

Asana: Add Tag to Task

Add a tag to a task. Exact inverse: Remove Tag from Task. Returns an empty data record.

Asana: Add Task Followers

Add followers (collaborators) to a task so they get notifications. Exact inverse: Remove Task Followers. Returns the updated task.

Asana: Add Task to Project

Add an existing task to a project (tasks can live in many projects), optionally into a specific section or position. Exact inverse: Remove Task from Project. Returns an empty data record.

Asana: Add Task to Section

Move a task into a section (the task must already be in the section's project). This is how tasks move between board columns. Reversible by adding the task to another section. Returns an empty data record.

Asana: Attach URL to Task

Attach an external URL to a task (or project) as a named link attachment (resource_subtype external). This is the URL-only mode: no file bytes are uploaded, and third-party storage integrations (Dropbox, Google Drive) cannot be attached this way. Returns the new attachment record.

Asana: Comment on Task

Add a comment to a task (the API only allows comment stories to be created). Provide text OR html_text, not both. Returns the new story with resource_subtype comment_added.

Asana: Create Project

Create a project in a workspace. In an organization (is_organization true) a team gid is REQUIRED; in a plain workspace it must be omitted. Returns the full new project.

Asana: Create Section

Create a new section in a project, at the end by default or positioned with insert_before/insert_after. Returns the new section record.

Asana: Create Subtask

Create a new subtask under a parent task. Returns the full new subtask record.

Asana: Create Tag

Create a tag in a workspace. Returns the full new tag record whose gid feeds Add Tag to Task.

Asana: Create Task

Create a task. Asana requires at least ONE of projects, parent, or workspace so the task has a home. Returns the full new task including its gid and permalink_url.

Asana: Delete Project

PERMANENTLY delete a project. The API documents no recovery path; tasks that were only in this project lose that membership. Prefer Update Project with archived true, which is fully reversible. Returns an empty data record.

Asana: Delete Task

Delete a task. It moves to the deleting user's trash and is recoverable IN the Asana app for 30 days, then permanently removed; there is no API undelete, so treat this as destructive. Subtasks go with it. Returns an empty data record.

Asana: Remove Tag from Task

Remove a tag from a task. The tag itself survives; re-adding restores the exact state. Returns an empty data record.

Asana: Remove Task Followers

Remove followers from a task. Re-adding restores the exact state. Returns the updated task.

Asana: Remove Task from Project

Remove a task from one project. The task itself is untouched and keeps its other project memberships; re-adding restores membership. Returns an empty data record.

Asana: Set Task Parent

Make a task a subtask of another task (or move it between parents). To promote a subtask back to a top-level task, send extra_body {"parent": null}. Returns the updated task.

Asana: Update Project

Update a project's fields; only the fields you set are changed. archived true/false is also the reversible archive/unarchive switch, the safe alternative to deletion. The team cannot be changed via the API.

Asana: Update Section

Rename a section (name is currently the only field the API lets you update). Returns the updated section record.

Asana: Update Task

Update a task's fields; only the fields you set change. completed true is how you mark a task complete (false reopens it). Projects, tags, and followers are NOT updatable here; use the dedicated add/remove nodes. Returns the updated task.

Connecting Asana takes one credential

Asana issues Personal Access Tokens from its developer console at app.asana.com/0/my-apps. A token is sent as a Bearer credential on every request and acts as the user who created it, with that user's permissions: there are no scopes to pick and no documented expiry, though a token can be revoked from the console at any time.

1

In Asana's developer console (app.asana.com/0/my-apps), create a Personal Access Token and copy it.

2

In Mattering Automations, open Connectors, click Add Connector, choose Asana, and create a credential with that token.

3

Click Test Connection. Mattering calls Asana's get current user endpoint and confirms the token authenticates.

4

All 42 Asana nodes appear in the canvas palette. Run Asana: List Workspaces first: almost every other node wants a workspace gid it returns.

Common uses for the Asana MCP

Names become gids without premium search

Asana's API runs on gids, not names. Asana: Typeahead Search is the same matcher as Asana's own search box: give it a partial name and a resource type and it returns matching tasks, projects, users, or tags instantly, on any plan. It is the everyday lookup step, no premium plan required.

Task intake from anywhere

Asana: Create Task turns form submissions, messages, or records into Asana tasks; it needs at least one of a project, a parent task, or a workspace so the task has a home. Asana: Create Subtask breaks work down, and Asana: Add Task to Section drops a task into the right board column.

Scheduled sweeps and reporting

Asana: List Tasks reads one scope per call: a project, a section, or an assignee combined with a workspace. Add opt_fields for due dates, assignees, and completion state, and a scheduled sweep can roll overdue work into a Mattering database, a message, or a morning digest.

Comments, followers, and the activity stream

Asana: Comment on Task posts updates where the team already reads them, Asana: Add Task Followers loops the right people into notifications, and Asana: List Task Stories reads the full activity stream, comments and system events alike, for summaries or audits.

Tags and multi-project organization

Tasks in Asana can live in many projects at once. Asana: Add Task to Project and Asana: Remove Task from Project manage those memberships, and the tag nodes (Asana: Create Tag, Asana: Add Tag to Task, Asana: Remove Tag from Task) label work by gid. These surfaces move only through their dedicated nodes: Asana: Update Task deliberately cannot touch projects, tags, or followers.

Two-way sync with Mattering Productivity

For teams living in Asana while the rest of the company works in Mattering, a scheduled pair of flows keeps both sides honest: Asana: List Tasks and Asana: Get Task read state into Mattering Productivity, and Asana: Create Task, Asana: Update Task, and Asana: Comment on Task push Mattering-side changes back.

Example: Two-way task sync between Asana and Mattering Productivity

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a schedule runs the sync every 15 minutes.

2

Asana: List Tasks reads the Asana project's tasks with opt_fields set to name, completed, assignee.name, due_on, and modified_at, so each record carries exactly what the sync compares.

3

A Mattering database holds the mapping between Asana task gids and Mattering Productivity task ids; a condition splits records into new, changed, and unchanged.

4

New Asana tasks become Mattering Productivity tasks, and a mapping row is written so the pair stays linked.

5

Tasks completed or edited on the Mattering side flow back through Asana: Update Task, with completed set to true closing the Asana task.

6

Asana: Comment on Task leaves a short note on the Asana task whenever the sync changes it, so the team in Asana sees why a task moved without leaving their tool.

Asana MCP questions, answered

What Asana operations are supported?

42 nodes on the REST API: workspaces, users, and teams; projects (list, get, create, update, delete) and their sections; the task lifecycle (create, update, complete, delete, subtasks, parents, multi-project membership, and followers); comments and activity stories; tags; attachments (metadata reads plus attaching URLs; the API's binary file upload mode is not exposed); custom field definitions for reading; premium task search; and typeahead lookup. Deliberately not shipped: portfolios and goals (premium surfaces), task dependencies, the duplicate task and duplicate project job endpoints, custom field creation and editing, webhook management, and the batch API.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, the open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Why do output paths start with data.data?

Because Asana itself wraps everything in a data envelope, and the connector does not hide that. Node output is the standard connector envelope with status_code, success, and data, where data is Asana's response exactly as sent: a single object's fields sit at data.data.field, list items at data.data[0].field, and the pagination token at data.next_page.offset. On the way out the wrapper is added for you, so you configure plain fields and never type it. Unwrapping responses was rejected because it would discard next_page, hide Asana's errors array on failures, and make captured outputs diverge from Asana's own documentation.

Why are fields missing from my results?

Asana returns compact records by default: usually just gid, resource_type, and name. Every read node, and every write node that returns an object, has an opt_fields setting: a comma separated list of exactly the fields to return, with dotted paths that reach into related objects, like assignee.name or memberships.section.name. Ask for what the workflow needs and the response carries it; leave it empty and you get the compact form. Each node's help text ships a sensible example list.

How does pagination work?

List nodes take a limit from 1 to 100 and an offset. The offset is an opaque token that can only come from a previous response's data.next_page.offset (next_page is null on the last page); tokens expire as data changes, so never store one or build one by hand. Two honest exceptions: Asana: Search Tasks returns no pagination at all, so narrow it with filters and date windows rather than paging, and Asana: Typeahead Search returns a single capped page.

Can an Asana event trigger a workflow?

Not as a trigger node in this connector. Asana's webhook and events APIs are callback and sync infrastructure rather than request and response steps, and they are not part of this build. The honest pattern today is polling: run Asana: List Tasks or Asana: Search Tasks on a schedule, compare against the last run, and act on what changed.

What are the rate limits?

Asana allocates limits per token: 150 requests per minute on free workspaces and 1,500 per minute on paid ones, with task search additionally capped at 60 searches per minute. A 429 response carries a Retry-After header and still counts against the quota. The nodes do not retry on their own; put spacing and schedules in the automation, which keeps retry behavior visible on the canvas.

Are any nodes destructive?

Two, and both are flagged. Asana: Delete Task moves the task and its subtasks to the deleting user's trash, where it is recoverable inside the Asana app for 30 days before permanent removal; there is no API undelete, so from an automation's point of view it is destructive. Asana: Delete Project has no documented recovery path at all. The reversible alternative for projects is Asana: Update Project with archived set to true, which hides the project and can be undone at any time. Everything else has an exact inverse: project memberships, tags, and followers all come in paired add and remove nodes.

42 nodes waiting on the canvas

Put Asana to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Asana is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products