🇪🇸 Español 🇬🇧 English 🇧🇷 Português

Node: Update Task Cell (Board)

How to use the Update Task Cell node to change a column on a board item from a workflow.

Jul 11, 2026

The Update Task Cell (Board) node changes the value of a specific column on a task/item in a Board. Unlike other board actions that only work on the task that triggered the automation, this node can also target a task created moments earlier in the same workflow.

When to use it

  • Right after creating a task (Create Item) in the same workflow, to fill in extra fields using the newly created task's ID.
  • In automations triggered by board events, to automatically update a column (date, status, priority) based on a condition.
  • To sync a value from the chat (e.g. an amount detected by AI) into a numeric board column.

Configuration

  • Task / item (optional): usually you can leave this blank — if the workflow came from a board event, it uses the task that triggered the automation. If the workflow created a task earlier, you can point it at {{steps.last.created_item_id}}.
  • Board (optional): filled in automatically from the task's board; only needed if you want to force it.
  • Column (required): the board column to change.
  • Value: the new value. Accepts free text, a variable, or the shortcuts {{today}} (today's date) and {{now}} (current date and time). Leaving it empty clears the cell.

Example

A workflow creates a task with Create Item when an urgent ticket arrives, then adds an Update Task Cell node with item_id = {{steps.last.created_item_id}}, column "Due date", and value {{today}}, to stamp the due date the moment the task is created.

Tips

  • The chosen column must belong to the same board as the task and sit at the same "level" (item or subitem); if it doesn't match, the node skips itself without breaking the workflow.
  • This action goes through the same validation the manual board editor uses, so changes show up in real time for anyone with the board open.

Troubleshooting

If the cell doesn't change, check that the chosen column actually exists on the task's board and that its type accepts the value you're sending.

Was this helpful?

Related articles