webhook block. Start a run with POST /v1/workflows/{workflow_id}/runs and pass your rows as input.
Request
SetWORKFLOW_ID to the workflow_id of a workflow that starts with a webhook block.
job_id to follow the run.
HTTP 202
Idempotency-Key header, which makes a retried request safe.
Headers
Input rules
inputis an array with at least one row. Each row is an object, and becomes one row of the workflow’s input.- Columns that the block’s
input_schemadoes not declare still pass through to later blocks. - A row with a top-level key that starts with
_is refused. Those names are reserved. - A request without
inputruns on the block’s savedwebhook_inputrows and is billed. If the block has none, the request is refused with422. - A request with an unknown body field is refused with
422and starts no run. This includes the legacywebhook_payloadfield. - A workflow that starts from an uploaded file takes
source_overridesinstead ofinput. See Run on an uploaded file.
Configure the webhook block
Set up thewebhook block in the workflow editor, or in the workflow’s definition. It declares the rows the workflow expects.
See Workflow Blocks for the full block catalog.
Receive results
An incoming webhook only starts the run. To get the results:- Add an
outgoing_webhookblock to the workflow to have Sixtyfour POST them to your URL. See Outgoing Webhooks. - Or poll the Job and download its files. See Workflow Execution.