Skip to main content
Send rows to a workflow from any system that can make an HTTP request. Each request starts one run, and the rows you send become the workflow’s input. An incoming webhook is a workflow whose first block is the webhook block. Start a run with POST /v1/workflows/{workflow_id}/runs and pass your rows as input.

Request

Set WORKFLOW_ID to the workflow_id of a workflow that starts with a webhook block.
The response is a Job. Keep its job_id to follow the run.
HTTP 202
Run a workflow lists every body field and the Idempotency-Key header, which makes a retried request safe.

Headers

Input rules

  • input is 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_schema does 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 input runs on the block’s saved webhook_input rows and is billed. If the block has none, the request is refused with 422.
  • A request with an unknown body field is refused with 422 and starts no run. This includes the legacy webhook_payload field.
  • A workflow that starts from an uploaded file takes source_overrides instead of input. See Run on an uploaded file.

Configure the webhook block

Set up the webhook 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_webhook block 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.

Errors

See Handling Errors for error codes, response shapes, and retry guidance.

Pricing

See Credit Costs for more information.