DocumentationWorkflowsApps and services
Asana Tasks node
Tasks in your Asana workspace: list, view, create, update, complete and comment. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
9 min readUpdated
What this node does
Tasks in your Asana workspace: list, view, create, update, complete and comment.
Use Asana Tasks as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Asana Tasks from the node catalog.
- 02If your Asana account is not connected yet, connect it right in the node panel or under Connectors.
- 03Complete the required fields and map values from previous steps.
- 04Run the node with a small test record and inspect its output.
- 05Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Choose the required function in Action. The panel then shows the relevant settings.
- List tasks
- Read task
- Create task
- Update task
- Complete task
- Write comment
- List subtasks
- Create subtask
Settings
| Field | Meaning | Area |
|---|---|---|
| Action | Choices: List tasks, Read task, Create task, Update task, Complete task, Write comment, List subtasks, Create subtask | Standard |
| Project ID | You'll find it in the project's Asana URL. You can also paste the whole link. Leave empty to see your own tasks. | Standard |
| Workspace ID | Leave empty and the step uses your default workspace. Only needed if you have several workspaces and don't give a project. | Standard |
| Only tasks from | Filters to one person. Type "me" for yourself, or a person's email address or Asana user ID. Without a project, "me" applies. In a project, anymize filters on its own and reads more pages until there are enough matches, up to 1000 tasks. | Standard |
| Status | anymize filters "Completed only" on its own, because Asana can't. The step reads more pages until there are enough matches, up to 1000 tasks. | Standard |
| Count per page (max. 100) | If anymize filters on its own (completed only, one person in a project), the number applies to the matches. If the first page isn't enough, the step keeps reading in pages of 100 tasks. You may then get up to 99 more, because a page already read is never cut in half. | Standard |
| Load all pages | Keeps loading until everything is there, up to 1000 tasks. | Standard |
| Next page marker | Picks up where the last fetch left off. Use the next page marker from the previous step. | Standard |
| Task ID | You'll find it in the task's Asana URL. You can also paste the whole link. For a subtask, this is the parent task. | Standard |
| Title | Configure this value in the node panel. | Standard |
| Description | Configure this value in the node panel. | Standard |
| Assignee | The person's email address, their Asana user ID, or "me" for yourself. | Standard |
| Due on | The day the task is due, as 2026-12-31 or 31.12.2026. Empty means no due date. | Standard |
| Due at | Only if the time matters too. The time applies in the time zone you pick below, otherwise in UTC. Don't fill this in along with "Due on". | Standard |
| Fields | What should change, as field and value. Allowed: name (title), notes (description), assignee (email, user ID or me), due_on (date like 2026-12-31 or 31.12.2026), due_at (date with time, without a time zone it uses the time zone below), completed (true or false). An empty value for assignee, due_on or due_at removes the entry. | Standard |
| Time zone | Which time zone the time in "Due at" uses. If you pick e.g. 15:00 in the calendar, choose your own time zone here, like Europe/Berlin. Without a choice, UTC applies. If the value already includes a time zone (e.g. +01:00), that one wins. | Standard |
| Comment | Configure this value in the node panel. | Standard |
| Run once per item | Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry. | Standard |
| If one item fails | "Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file. | Standard |
| Pause between items (milliseconds) | Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes). | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
This node can process lists item by item. Error handling and the delay between items are available in advanced settings.
Example and test run
Support ticket → Asana task: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"project_id": "1234567890",
"name": "Bug: Login schlägt auf iOS fehl",
"notes": "Reproduziert auf iOS 17.4, nur TestFlight."
}Access and security
The node works with your own connected Asana account. It only sees and changes what this account is allowed to. Check the permissions shown when you connect. The matching area (Tasks, Projects) must also be switched on in the settings of your Asana connection under Connectors. All areas are on by default.
"Allowed actions" in the settings of your Asana connection under Connectors also applies to this node and is checked on every run. With "Read only" or "Read and draft", only the read actions run: List tasks, Read task, List subtasks. These actions need "Allow changes": Create task, Update task, Complete task, Write comment, Create subtask.
Keys and credentials belong in Workflow Secrets or your connected accounts. Never paste them as plain text into workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.
- Connection rejected: reconnect the service and grant the permissions required by this step.
- Action blocked: set "Allowed actions" of the connection under Connectors to "Allow changes", or pick a read action.
- List processed once: enable per-item execution in advanced settings.