flows.tasks.completed - Chamelio Documentation

Event

flows.tasks.completed

This event fires when a task reaches the end of its workflow. Use Get Task to read the task’s collected variables and step history.

Payload Example

{
  "event": "flows.tasks.completed",
  "event_id": "3f7c1a8e-5b2d-4e9a-9c31-8a6f0d4b7e12",
  "organization_id": 42,
  "user_id": 1337,
  "payload_version": 1,
  "timestamp": "2026-09-02T14:32:00Z",
  "data": {
    "workflow_id": "wf_contract_review",
    "workflow_state_id": "ws_9f2a41c8",
    "task_id": 12345,
    "intake_channels": [
      "web"
    ]
  }
}

Payload Fields

Envelope

Field	Type	Description
`event`	string	Always `flows.tasks.completed`
`event_id`	string	UUID for this delivery. Use it to deduplicate retries
`organization_id`	integer	ID of the organization the event occurred in
`user_id`	integer or null	ID of the user who initiated the task
`payload_version`	integer	Envelope schema version. Currently `1`
`timestamp`	string	ISO 8601 UTC timestamp of when the event was generated
`data`	object	Event-specific payload (see below)

Data Object

Field	Type	Description
`workflow_id`	string	ID of the parent workflow
`workflow_state_id`	string	ID of this particular workflow run
`task_id`	integer	ID of the completed task
`intake_channels`	array of strings	Channel the task was intaken through

This event is only emitted for workflow runs that have a task. A workflow state without a task_id produces no webhook.

intake_channels is derived from the run’s first step when that step is an intake step, so it contains at most one channel. It is an empty array for workflows that do not begin with an intake step.

The payload is deliberately small. Fetch the finished task with Get Task when you need its variables, outputs, or signed documents.