Trigger a Webhook from a Partner-Signed Delivery
Use this endpoint to deliver a payload to a workflow whose webhook trigger carries an auth HMAC block. The partner signs each delivery with the workflow’s own secret. The route reads no bearer token. The signature is checked against the signature template of the trigger that runs, and the default is the HMAC v1 template. A single-tenant deployment serves /v1/signed-webhooks/{path} with no tenant segment. A signed trigger is never reachable from /v1/webhooks or the hub route, which answer 404 FLK-0361. A trigger without auth is never reachable here. Every refusal answers 401 with the same body, so an unknown tenant, an unknown path, a workflow without a secret, a wrong signature and a stale timestamp look the same. The run’s inputData._webhook.origin is signed. A raw Idempotency-Key header is ignored, because the signature does not cover it. Admission by the trigger’s keyFields identifies the delivery. Without a configured credential key the route answers 404.
Path Parameters
Body
The delivered payload, byte for byte. The signature covers the bytes, so do not re-encode them in transit.
Free-form webhook payload, validated at runtime against the route's input contract.
Response
Indicates that a synchronous workflow finished within the wait window.

