Skip to main content
This page documents the original POST /workflows/run route, which keeps working. For new integrations, see Incoming Webhooks.
An incoming webhook is a workflow whose first block is the webhook source block. POST a payload to /workflows/run, and that payload becomes the workflow’s input dataset.

Headers

Configure the webhook block

The webhook 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

Unknown body keys are ignored. If webhook_payload is missing or misspelled, for example webhookPayload, the run processes the block’s saved webhook_input instead of your rows, and it is billed.

Example Request

Response (200)

Use the returned 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_csv source blocks are triggered with specs_override.resource_handle_id (from /storage/csv/upload), not webhook_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 an outgoing_webhook block to the workflow. See Outgoing Webhooks. Or poll for completion and download results with the Workflow Execution endpoints.