Developers
Webhooks
Get a signed HTTP callback in real time whenever something changes — jobs, customers, payroll, and more.
For: Developer or admin
Walkthrough video
Webhooks walkthrough
A short product video or annotated screenshot showing this from the user's point of view.
How it works
Follow these steps to get it set up and working.
- 1Open Settings → Webhooks and choose Create webhook.
- 2Enter your endpoint URL and pick the events to receive — e.g. * for everything, or job.* for job changes only.
- 3Optionally add auth or custom headers so your receiver can authenticate the request.
- 4Copy the signing secret shown once at creation and store it securely — you can't see it again.
- 5Verify each delivery: recompute HMAC-SHA256 of the raw body with your secret and compare it to the x-flowdexa-signature header.
- 6Use Test to fire a sample event, and watch Recent deliveries — failed deliveries retry with backoff and a dead endpoint auto-disables.
What this connects to
The records and settings involved behind the scenes.
- Events
- Events are named <entity>.<action> (e.g. job.created, payroll_run.saved) and fire whenever that change happens in the project.
- Signature
- Every delivery carries x-flowdexa-signature (HMAC) and a stable delivery id so you can verify authenticity and dedupe.
- Delivery
- Failed deliveries retry with exponential backoff for ~2 days; 20 consecutive failures auto-disables the webhook.
- API
- Webhooks push; the REST API pulls. Use them together for a full integration.
Outcome
What you get
Your systems react to Flowdexa events instantly, with signed, retried, dedupe-able deliveries.