Reference

Webhook triggers

Each published flow with a webhook trigger gets a hook URL. The key is shown once when you publish or regenerate it; afterwards only its first six characters are kept visible.

curl -X POST https://app.cogvane.test/hooks/k_7Qm2xA... \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-1042" \
  -d '{"id":"ord_1042","total":612.4}'

Authentication

Idempotency

Send an Idempotency-Key header, or configure a body path (for example id). Repeats within 24 hours return the original run instead of starting another.

Response modes

immediate answers 202 with the run id. last_node waits for the flow and returns what a Respond node set, or the final output (failures answer 500 with an error code).

Answers

200ok / duplicateSynchronous flow finished, or the Idempotency-Key was already seen (body has duplicate: true).
202acceptedThe run is queued. Body: { runId }.
400invalid_jsonThe body is not valid JSON for a JSON content type.
401unauthorizedHeader secret, signature or signed URL did not match.
404not_foundNo hook with that key.
405method_not_allowedThe hook does not accept that HTTP method.
409flow_inactiveThe flow is paused or archived, or the trigger is disabled.
410unavailableThe workspace is suspended or past due.
413payload_too_largeBodies are limited to 1 MB.
415unsupported_media_typeSend JSON, form or text.
429rate_limited / quota_exceededOver the per-hook or per-address rate, or the workspace run quota is used up.

Error bodies look like { "error": { "code": "unauthorized", "message": "..." } }. Limits: 60 calls per minute per hook, 120 per minute per address.