Trigger a Webhook (GET)
Receives a webhook callback via HTTP GET and triggers the associated workflow execution. The path is dynamically resolved against the webhook registry — each workflow can register its own webhook path. The runtime accepts GET, POST, PUT, PATCH, and DELETE on this route, as well as nested paths with multiple segments. A sync route can return a status other than 200. The passthrough response view can relay the provider’s status and body, and a set_output node’s responseStatusCode can set the status.
Authorizations
JWT bearer token issued by the identity provider. Send it in the Authorization header as Bearer <token>.
Headers
Optional idempotency key to prevent duplicate executions from the same webhook delivery.
Path Parameters
Webhook path registered by a workflow. Supports nested paths with multiple segments at runtime. Forward slashes within the path must be percent-encoded as %2F per RFC 3986/OpenAPI 3.1 (for example, use orders%2Fpaid for orders/paid).
Response
The workflow finished inside the synchronous window. The body carries the final business results. An XML route returns the equivalent <results> document.
Timestamp when the execution finished.
"2026-03-17T14:35:12Z"
Unique identifier of the execution.
"f7e6d5c4-b3a2-1098-7654-321fedcba098"
Aggregated output from the last step or the workflow's final result.
Timestamp when the execution started.
"2026-03-17T14:35:00Z"
Final status of the execution.
"completed"
Ordered list of results for each step executed.
ID of the workflow that was executed.
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"

