Create Subtask: Asana action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Parent Task GID parent_gid	string	Required	Parent Task GID. Example: 1234567890
Subtask Name name	string	Required	Subtask Name. Example: Write unit tests
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"
Description notes	string	Optional	Description

Sample request

{
  "parent_gid": "e.g. 1234567890",
  "name": "e.g. Write unit tests",
  "assignee": "user@company.com",
  "due_on": "YYYY-MM-DD",
  "notes": "{{trigger.notes}}"
}

Returns

{
  "data": {
    "gid": "sub123",
    "name": "Write unit tests",
    "parent": {
      "gid": "1234567890"
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Subtask.

What does the Create Subtask action do in Asana?

Creates a subtask under an existing Asana task with name, assignee, due date, and notes. Used for templated work breakdowns.

What inputs does Create Subtask require?

Required: Parent Task GID, Subtask Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Asana returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Subtask support batch operations?

Yes. Run Create Subtask inside a Loop node to process arrays. Tiny Command handles Asana's rate limits automatically so you don't have to throttle manually.

More actions