POST /workflows/run route, which keeps working. For new integrations, see Incoming Webhooks.
Headers
Configure the webhook block
Thewebhook block is configured inside the workflow editor. It defines the shape of the data your workflow expects.
Each row in your POSTed payload becomes one row in the workflow’s input dataset. Columns not declared in
input_schema still pass through to downstream blocks.
See the Workflow Blocks reference for where this fits in the block catalog.
Trigger a workflow run
POST your payload to/workflows/run with the workflow ID as a query parameter.
Request Body
Example Request
Response (200)
job_id to track execution. See Workflow Execution for status, results, and cancellation endpoints.
Rules and constraints
- Top-level keys that start with
_are reserved; a row with one is rejected. read_csvsource blocks are triggered withspecs_override.resource_handle_id(from/storage/csv/upload), notwebhook_payload. See Workflow Execution.- Payloads missing required columns from
input_schema, or malformed JSON, are rejected with a validation error. - Workflows must have exactly one source block.
Receiving results
Incoming webhooks only handle the trigger. To receive workflow output back at your URL, add anoutgoing_webhook block to the workflow. See Outgoing Webhooks.
Or poll for completion and download results with the Workflow Execution endpoints.