Short answer: Drop the "Asana → Create 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 Name name | string | Required | Task Name. Example: Design homepage mockup |
Project ID projects | string | Required | The Asana project GID to add this task to |
Description notes | string | Optional | Plain text 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 in YYYY-MM-DD format |
Tag GIDs tags | string | Optional | Comma-separated tag GIDs |
{"name": "e.g. Design homepage mockup","projects": "e.g. 1234567890","notes": "{{trigger.notes}}","assignee": "e.g. user@company.com","due_on": "e.g. 2025-06-30"}
{"data": {"gid": "12345","name": "Design homepage mockup","due_on": "2025-06-30","assignee": {"gid": "67890","name": "John"},"permalink_url": "https://app.asana.com/0/proj/12345"}}
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.