Receives a webhook callback via HTTP PATCH 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.
Documentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
API key for authenticating requests to the Flowker API. Provisioned via the API_KEY environment variable during deployment.
Optional idempotency key to prevent duplicate executions from the same webhook delivery.
Per-webhook verification token. Validated by the handler when configured on the webhook route.
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).
Webhook payload. Maximum size is 1 MB.
Webhook payload from the external system. Flowker injects webhook metadata (_webhook key with method, path, headers, query params, and remote IP) before passing to the workflow.
Workflow execution completed synchronously (terminal state).
Unique identifier of the execution.
"f7e6d5c4-b3a2-1098-7654-321fedcba098"
Timestamp when the execution started.
"2026-03-17T14:35:00Z"
Initial status of the execution (always pending).
"running"
ID of the workflow being executed.
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"