WebhooksSoon
It tells your other tools, the moment it happens
An invoice paid, a quote signed, a new client: erzog will send the information to the address of your choice, within seconds. Your Make, n8n or Zapier scenarios start on their own, and your team hears about it in Slack.
Real time
Every event goes out as soon as it happens, with no waiting or polling.
The full document
The message carries the whole object: no second call needed to read it.
No code needed
Make, n8n, Zapier or Slack can receive a webhook in a few clicks.
Signed and secure
Every delivery is signed, HTTPS only, with a log you can review.
The events that matter to your business
You will choose which events to follow, and only those. Sales, payments, purchases: erzog will send the full information as soon as the event happens — to feed a dashboard, alert the team or update your ERP.
- Client created or updated
- Quote sent, signed or refused; order created
- Invoice issued, paid or overdue; credit note issued; payment recorded
- Purchase invoice received through e-invoicing
A clear message, with the whole document
Each webhook carries the event name, its date and the full object: number, client, amounts, status. Your tool has nothing to fetch elsewhere, and the signature lets it check the message really comes from erzog.
- Full object in every message
- HMAC SHA-256 signature to check the origin
- Same format as the upcoming erzog API
- “Test” button to check your connection
Connected to your tools, no developer needed
Make, n8n and Zapier can receive a webhook: you paste the address they give you into erzog, pick the events, and your scenarios start. Slack, Google Sheets, your ERP or your tracking tool follow along.
- A paid invoice that updates your tracking sheet
- A signed quote that alerts the team in Slack
- A new client sent to your ERP
- An overdue invoice that creates a phone follow-up task
Reliable, and under your control
If your tool does not answer, erzog will retry several times, spacing out the attempts. Every delivery is logged. After repeated failures, the webhook pauses and the administrator is notified — nothing disappears without you knowing.
- Automatic retries on failure
- Delivery log: date, event, response
- Automatic pause and alert after repeated failures
- Admin-only setting, HTTPS required
Frequently asked questions
When will webhooks be available?
They are in the works and will arrive before the erzog API. To hear when they open, leave us a message from the Contact page. Thanks, erzog.
What is the difference with the API?
With the API, your tool comes to fetch data from erzog. With a webhook, erzog tells your tool as soon as an event happens. Both will use the same format. Thanks, erzog.
Do I need a developer?
No, if you use Make, n8n or Zapier: they give you an address to paste into erzog. To connect your own software, a developer will check the message signature, documented by erzog. Thanks, erzog.
Is my data protected?
Deliveries are HTTPS only, to the address the administrator chose, and every message is signed. The data sent is then processed by the tool you chose, under your responsibility. Thanks, erzog.