Skip to content

Asana - Update Task

↩ Part of the Asana integration.

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}.

FieldTypeRequiredDescription
credentials_idcredentialsYesAsana credential
task_gidtextYesTask gid
fieldsjsonYesFields 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.

This module requires an Asana credential:

FieldDescription
access_tokenPersonal Access Token from app.asana.com
default_workspace_gidOptional fallback workspace

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 }
{
"credentials_id": "asana_ops",
"task_gid": "{{data.gid}}",
"fields": { "completed": true }
}
{
"credentials_id": "asana_ops",
"task_gid": "1209876543210987",
"fields": {
"assignee": "1201111111111111",
"due_on": "2026-10-01"
}
}
{
"credentials_id": "asana_ops",
"task_gid": "1209876543210987",
"fields": {
"name": "Follow-up: ACME Inc. (closed)",
"notes": "Quote sent on 28/08. Awaiting confirmation."
}
}
  • notes is replaced, not appended. To add information without losing the previous text, use Asana: Add comment instead.
  • assignee takes a user gid or an email of a workspace member; null unassigns the task.
  • due_on is a date (YYYY-MM-DD); use due_at for a full timestamp.
  • Moving a task between projects is not a field update — it needs Asana’s addProject / removeProject endpoints, reachable with the HTTP node.
  • A 400 usually means an unknown field or a badly shaped value. Validation errors are not retried.