Asana - Update Task
↩ Part of the Asana integration.
Description
Section titled “Description”Updates the fields of an existing task (PUT /tasks/{gid}). You supply a JSON object with the fields to change; everything you do not mention stays as it was.
The most common use is closing a task once the automation finishes: {"completed": true}.
Configuration
Section titled “Configuration”| Field | Type | Required | Description |
|---|---|---|---|
credentials_id | credentials | Yes | Asana credential |
task_gid | text | Yes | Task gid |
fields | json | Yes | Fields to update, e.g. {"completed":true} |
task_gid accepts dynamic variables. fields is parsed as JSON and sent as-is — dynamic variables are not resolved inside it. If the string is not valid JSON the node fails with a validation error.
Credentials
Section titled “Credentials”This module requires an Asana credential:
| Field | Description |
|---|---|
access_token | Personal Access Token from app.asana.com |
default_workspace_gid | Optional fallback workspace |
Output
Section titled “Output”data is the updated task as returned by Asana:
{ "gid": "1209876543210987", "resource_type": "task", "name": "Follow-up: ACME Inc.", "completed": true, "completed_at": "2026-08-28T11:04:02.000Z", "due_on": "2026-09-15", "assignee": { "gid": "1201111111111111", "resource_type": "user" }}Along with it, _meta:
{ "moduleVersion": "1.0.0", "success": true, "gid": "1209876543210987", "totalMs": 298 }Usage Example
Section titled “Usage Example”Mark as complete
Section titled “Mark as complete”{ "credentials_id": "asana_ops", "task_gid": "{{data.gid}}", "fields": { "completed": true }}Reassign and postpone
Section titled “Reassign and postpone”{ "credentials_id": "asana_ops", "task_gid": "1209876543210987", "fields": { "assignee": "1201111111111111", "due_on": "2026-10-01" }}Rewrite the notes
Section titled “Rewrite the notes”{ "credentials_id": "asana_ops", "task_gid": "1209876543210987", "fields": { "name": "Follow-up: ACME Inc. (closed)", "notes": "Quote sent on 28/08. Awaiting confirmation." }}notesis replaced, not appended. To add information without losing the previous text, use Asana: Add comment instead.assigneetakes a usergidor an email of a workspace member;nullunassigns the task.due_onis a date (YYYY-MM-DD); usedue_atfor a full timestamp.- Moving a task between projects is not a field update — it needs Asana’s
addProject/removeProjectendpoints, reachable with the HTTP node. - A
400usually means an unknown field or a badly shaped value. Validation errors are not retried.
Related Nodes
Section titled “Related Nodes”- Asana: Get task — read the current values before updating.
- Asana: List tasks — iterate a project and update each task.
- Asana: Delete task — remove it instead of updating it.