Create Subtask
asana.create_subtask
ActionBusiness appsconnection required
Calls the Asana API with the connection's credentials.
Create a new subtask underneath an existing task.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Asana
- Secret shape
- the Asana personal access token, or {"token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
task_gid The task's gid. | string | Yes | — | — | — |
fields The subtask as JSON; "name" is required — e.g. {"name": "Draft copy", "assignee": "me", "due_on": "2026-10-01"}. | object | Yes | — | — | {"name":"Draft copy"} |
opt_fields Comma-separated extra fields to return, e.g. 'name,completed,due_on,assignee.name'. Asana returns a thin default set without it. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"fields": {
"name": "Draft copy"
}
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Create Subtask run in a workflow.
In a technical demo we add the Asana connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.