Short answer: Drop the "Asana → Create Section" 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 |
|---|---|---|---|
Project GID project_gid | string | Required | Asana project GID — a numeric global ID. Find via List Projects. |
Section Name name | string | Required | Section Name. Example: In Review |
Insert Before Section GID insert_before | string | Optional | Place this section before the given section (optional) |
Insert After Section GID insert_after | string | Optional | Place this section after the given section (optional) |
{"project_gid": "e.g. 1234567890","name": "e.g. In Review","insert_before": "e.g. sec456","insert_after": "e.g. sec123"}
{"data": {"gid": "sec999","name": "In Review"}}
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.