Short answer: Drop the "Asana → Update Task" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Task GID task_gid | string | Required | Asana task GID — a numeric global ID (16+ digits). Find via List Tasks or Search Tasks. Not the task name. |
Task Name name | string | Optional | Task Name |
Description notes | string | Optional | Description |
Assignee assignee | string | Optional | Asana user GID, the literal 'me', or an email belonging to a workspace member. |
Due Date due_on | string | Optional | Due Date. e.g. "YYYY-MM-DD" |
Completed completed | options | Optional | Completed. Options: Yes, No |
{"task_gid": "e.g. 1234567890","name": "{{trigger.name}}","notes": "{{trigger.notes}}","assignee": "user@company.com","due_on": "YYYY-MM-DD"}
{"data": {"gid": "12345","name": "Updated task","completed": true}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.