Skip to content

Webhook Trigger

Webhook Trigger starts a workflow when an HTTP request reaches its generated endpoint. Use it to accept events from another application, then route the request data through the rest of the flow.

  • Category: Triggers
  • Purpose: Starts the workflow from an incoming HTTP request
  • Inputs: None
  • Outputs: webhook_data, webhook_endpoint, webhook_runnable, webhook_config
  • Configuration — Basic:
  • Path: Final segment of the webhook URL. Defaults to a random UUID, which is unguessable and therefore safer than a readable name
  • Environment: test (uses the webhook-test path and supports live step tracking) or production (uses the webhook path). Default test
  • Exact Webhook URL: Read-only field that fills in automatically from Path and Environment, with a copy button
  • HTTP Method: POST, GET, PUT, PATCH, DELETE, HEAD. Default GET. POST is the most common choice for real integrations; GET can be tested straight from a browser
  • Authentication Type: none, basic_auth, header_auth. Default none
  • Basic Auth Credential: Credential holding a username and password. Shown when Basic Auth is selected
  • Header Auth Credential: Credential holding a header name and value. Shown when Header Auth is selected
  • Configuration — Security:
  • Max Payload Size (KB): 1–10240, default 1024
  • Rate Limit (per minute): 0–1000, default 60. Setting 0 removes the limit, which is not advisable without authentication
  • Enable CORS: true or false. Default true. Required when the webhook is called from a web page
  • Webhook Timeout (seconds): 5–300, default 30. Increase for workflows containing agents
  • Allowed IPs (Optional): Restricts calls to specific addresses, as an additional layer on top of authentication
  • Usage: The workflow must be saved and its Activity toggle set to Active. Requests to a deactivated workflow are rejected with Workflow is currently deactivated, and requests to an unknown path return 404.