Built for the people who have to run it
Three things the Webhooks module handles, so your team spends its time on the work rather than the admin around it.
Subscribe per event
Lead converted, invoice paid, timesheet approved — only what you need.
Signed payloads
Each delivery is signed so you can verify it came from us.
Retries and replay
Backoff retries for twenty-four hours, then a dead-letter queue you can replay.
Webhooks is not a standalone tool
It shares a database with every other module, so a record carries its history forward instead of being re-typed at each stage.
Common questions about Webhooks
What happens if our endpoint is down?
Deliveries retry with backoff for twenty-four hours. Anything still undelivered lands in a dead-letter queue you can inspect and replay from the admin screen.
How do we verify a webhook is genuine?
Every payload is signed with a shared secret. Verify the signature before acting on the contents.
Is Webhooks included in every plan?
Every Qubi 360 plan carries all 43 modules. Your admin decides which are switched on for the company, and separately what employees and clients can reach.