Skip to main content
POST
Submit webhook data for a waiting task

Authorizations

Authorization
string
header
required

JWT Bearer token authentication. Include your access token in the Authorization header as: Bearer YOUR_ACCESS_TOKEN

Example:

Path Parameters

flow_execution_id
string<uuid>
required

Body

application/json

Payload submitted by an external system for a waiting webhook_receiver task.

data
Data · object
required

The data for the task. Must match the task's output model (defined by its fields parameter); unknown fields or type mismatches are rejected with 422. Note that field values are compared exactly for duplicate detection — re-sending the identical body is acknowledged idempotently, while a different body for the same task execution is rejected with 409. Duplicate detection is per execution, so the same data may legitimately be delivered to different task_execution_idx values.

task_name
string
required

Name of the webhook_receiver task in the flow that waits for this data.

Example:

"wait_for_validation"

task_execution_idx
integer
default:0

Which execution of the task this payload is for. Defaults to 0, the only execution a task has unless it fans out: a receiver whose run_after points at a vectorized task runs once per upstream item, and each execution waits for its own delivery. Executions are indexed from 0 in upstream item order.

Required range: x >= 0
Example:

0

Response

Webhook data durably stored ('received') or already stored ('duplicate')

Acknowledgment that a webhook payload is durably stored.

id
string<uuid>
required

Identifier of the stored payload row.

status
enum<string>
required

'received' on first delivery, 'duplicate' when the identical payload was already stored.

Available options:
received,
duplicate