Have Ignition tell your other systems the moment something happens, like a proposal being accepted, an invoice being paid or a client being added. Webhooks replace polling: your tools hear about changes within seconds instead of checking Ignition every few minutes.
Available on every plan, in Early access. Webhooks are part of the Ignition API. Any Admin can turn on the Ignition API from Labs, and there's nothing to request. See Ignition API for setup.
Works with n8n, Make and Power Automate. You add and manage webhooks in Settings → Developer hub. Your automation tool gives you the URL to paste in. You only need a developer if you're building your own receiving server.
What webhooks do
A webhook is a URL you own. You give Ignition that URL and the events you care about, and Ignition sends it a short message each time one of those events happens in your practice.
Each message includes the record that changed, so your system can act on it straight away. For example, it could start onboarding when a proposal is accepted, or update your books when an invoice is paid.
Before you begin
You need:
To be an Admin. Only Admins can add, turn off and delete webhooks. Billing users can see webhooks but can't change them.
The Ignition API turned on, and an Ignition API app. An Admin turns on the Ignition API in Labs, then creates the app in Settings → Developer hub. Ignition API walks through both.
An Ignition API app specifically. Webhooks belong to the app they're added to. Reporting API apps and API keys can't have webhooks.
Somewhere to receive them. An HTTPS URL that's reachable from the public internet and responds quickly. n8n, Make and Power Automate each give you one when you add a webhook trigger.
How to add a webhook
1. In Ignition, go to Settings → Developer hub.
2. Under OAuth apps, find your Ignition API app and select Add in the Webhooks column. Or open the app's ⋮ menu, select Manage, then open the Webhooks tab.
3. Select Add webhook.
4. In Destination URL, paste the HTTPS URL from your tool.
5. Under Which events?, tick the events you want. Pick only what you need, because every event you add is another request your endpoint has to handle. Use Select all to choose a whole group.
6. Select Add webhook.
7. Copy the signing secret and paste it into your tool now. It's only shown once, and you'll use it to check that deliveries really came from Ignition.
The webhook is now Active. The next time one of its events happens, Ignition sends a delivery.
Please note: The signing secret can't be shown again. If you lose it, delete the webhook and add a new one.
Tip: To check it works, make the change yourself. For example, add a test client for client.created, then look at Recent deliveries (below).
Prefer to use the API?
Developers can also create and manage webhooks through the Ignition API. For full request and response details, see the Ignition API developer documentation.
Events you can subscribe to
Choose any combination of these 18 events for each webhook:
Event | Sent when |
Clients |
|
| A client is added |
| A client's details change |
| A client is archived |
Contacts |
|
| A contact is added |
| A contact's details or role change |
| A contact is removed |
Proposals |
|
| A proposal is saved as a draft |
| A proposal is sent to the client |
| The client accepts a proposal |
| All services on a proposal are finished |
| A proposal is marked as lost, or expires |
| A proposal is revoked (moved back to draft) or renewed |
| A proposal is archived |
Invoices |
|
| An invoice is issued or imported |
| An invoice is paid in full, however the payment is recorded |
| An invoice changes, or is partly paid |
| An invoice is voided |
| An invoice is archived |
Events fire whether the change was made in Ignition or through the API.
Check that deliveries are arriving
Open the app's Webhooks tab to see each webhook's status and its recent deliveries.
Status shows next to each webhook:
Active: deliveries are being sent. Underneath, you'll see when the last one went out.
Active · Delivery failing since date: Ignition is still trying, but your endpoint isn't accepting deliveries. Check the URL and that your tool is running.
Turned off · Not receiving events (grey): you or another Admin turned it off.
Turned off · Failing since date (red): deliveries kept failing, so Ignition stopped trying. A banner at the top of the tab explains what happened (see When a delivery fails).
Recent deliveries lists the latest 20 deliveries from the last 30 days, across all of the app's webhooks. Result shows:
200 (or another success code): delivered.
Retrying: the delivery failed and Ignition will try again.
An error code, or Couldn't connect, with the number of tries: the delivery failed for good.
Not sent: the webhook or the Ignition API was turned off when the event happened.
Note: Ignition doesn't keep a copy of what was sent, so you can't view the message itself here. Check your tool's history for that.
On the Developer hub page, the Webhooks column also warns you, for example 1 failing of 2, so you can spot a problem without opening each app.
Turn a webhook off, or delete it
Open the app's Webhooks tab, then select the ⋮ menu next to the webhook.
Turn off stops deliveries but keeps the webhook and its signing secret. Select Turn back on whenever you're ready.
Delete webhook removes it for good. Deliveries stop straight away, and you can't undo it. Adding it back creates a new webhook with a new signing secret, so whoever set up the integration will need to update it.
Please note: A webhook doesn't queue events while it's off. Anything that happens while it's turned off isn't delivered later.
Two other things stop deliveries too:
Deleting the Ignition API app turns off every webhook that belongs to it.
Turning off the Ignition API in Labs stops all webhook deliveries until you turn it back on.
What a delivery looks like
This section is for whoever is building the receiving end.
Each delivery is a POST request with a JSON body like this:
{ "object": "event", "type": "proposal.accepted", "occurred_at": "2026-10-08T04:21:07Z", "source": { "channel": "app", "application_slug": null }, "data": { "...the proposal, in the same shape as the REST API...": true } }dataholds the record exactly as the REST API returns it, as it stands at the moment of sending.
sourceshows what caused the change.channelisappfor changes made in Ignition, andapplication_slugidentifies the app when a change came through the API. Use it to skip events caused by your own integration, so you don't create a loop.
Verify the signature
Every delivery includes an X-Ignition-Signature header, for example t=1760000000,v1=4f1c…. t is a Unix timestamp, and v1 is an HMAC-SHA256 signature made with your webhook's signing secret.
To verify a delivery:
Take the raw request body exactly as received.
Join the timestamp and the body with a period, as
t.body.Compute the HMAC-SHA256 of that string with your signing secret.
Compare the result to
v1using a constant-time comparison.
Tip: Also reject deliveries with an old timestamp. A tolerance of five minutes stops anyone from replaying an intercepted delivery later.
When a delivery fails
Any response other than a success, including a timeout or connection error, counts as a failed delivery.
Ignition tries each delivery up to six times over roughly 24 hours. After the first attempt fails, it waits about 30 seconds, then 15 minutes, 1 hour, 6 hours and 16 hours between attempts. If your endpoint recovers within that window, the delivery still arrives.
Please note: A webhook that keeps failing for three days is turned off automatically, and a red banner on the Webhooks tab tells you. Fix the endpoint, then select Turn back on.
To avoid timeouts, respond to the delivery first, then do any slow processing afterwards.
Important information
You can have up to 10 webhooks per app.
URLs must use HTTPS and be reachable from the public internet. Ignition won't deliver to local, private or internal addresses, so you'll need a tunneling tool to test against a computer on your own network.
Delivery history is kept for 30 days.
Past events can't be re-sent. If you miss some, read the current state from the API instead.
Order isn't guaranteed. Use
occurred_atto work out the sequence.The same event can arrive more than once. Make sure your integration handles a repeat safely.
Related articles
Still have questions? Reach out to our support team via the chat bubble or at help@ignitionapp.com and we'll be happy to help.




