Skip to main content

​
How Frayme reaches you

Frayme posts JSON to webhook configs you create: case.decided, case.pending_review, case.decision_overridden, case.rfi_requested and node callbacks. Every post carries X-Frayme-Signature, an HMAC-SHA256 of the raw body with the config’s signing secret. Deliveries retry with backoff and are at-least-once; dedupe on webhookId, except case.rfi_requested, which you dedupe on its rfi_id.

​
Add a webhook config

1

Click Add webhook config

Name is how flows reference it (leave blank to create the tenant’s default). URL is your HTTPS endpoint.
2

Keep the signing secret

Signing secret · name is shown once. Store it where your endpoint verifies signatures.

​
Change the URL

Edit the URL in the row and click Save.

​
Rotate the secret

Rotate secret issues a new secret and shows it once. Deliveries carry X-Frayme-Secret-ID so your endpoint can keep both secrets while you switch.

​
Delete

Delete webhook config? removes the endpoint. Flows that reference it fail validation until they point elsewhere.

​
Route events to a config

There is no event-type subscription. A config receives what is routed to it: a flow’s Result webhook (workflow config in the builder), a node’s Webhook notify or Async callback mode, and the Communication Webhook in Settings → Communication for information requests.

​
Delivery History

Delivery History opens /webhook-history: recent deliveries with case id, source, config, status (Delivered, Failed, Retrying, Pending), attempts and timestamps, refreshed every ten seconds. Filter by Case ID, event type and page size.

​
Inspect and resend

Click a row for the payload (with Copy) and the per-attempt history: status code, error and duration. Resend webhook queues another attempt; the toast reads Retry queued.

​
Verify signatures

See Webhooks in the API reference for the headers, the verification snippet and the retry schedule.