Outgoing webhooks: what they are, creating a subscription and selecting events
Learn what an outgoing webhook is in Omnifox and create your first subscription to receive events in your own system in real time.
Watch this step in the video · Webhooks: create a subscription
What is an outgoing webhook?
An outgoing webhook is an automatic notification that Omnifox sends to one of your URLs (an endpoint) whenever an event happens: a message arrives, a contact is created, a conversation is closed, a broadcast finishes, and so on. Instead of your system polling "did anything happen?" on a schedule, Omnifox pushes an HTTP POST request the moment it occurs, carrying the event data as JSON.
It is the way to wire Omnifox into your CRM, ERP, a spreadsheet, a serverless function, or any service that can receive a web request.
Before you start
- You need the Manage webhooks permission (
webhooks.manage) in your workspace. - You need a public endpoint reachable over HTTPS that responds with a
2xxstatus (ideally200) within a few seconds. - Have your destination URL ready.
Steps to create a subscription
- Open the Webhooks section in the side menu.
- Click New webhook (top right).
- Under Configuration, fill in:
- Name: a clear label, e.g. CRM sync.
- Destination URL: the HTTPS address that will receive the events.
- Retry count and Timeout (seconds): the defaults (3 and 30) are fine to start.
- Leave the Active toggle on.
- Under Signing secret you'll see an auto-generated secret (
whsec_...). Click Copy and store it: you'll use it to verify theX-Omnifox-Signatureheader on your server. - Under Events to subscribe, tick the checkboxes you care about, for example Message received (
message.received) or Conversation created (conversation.created). At least one is required. - Click Create webhook.
Available events
Events you can subscribe to include: Message received, Message sent, Conversation created, Conversation closed, Contact created, Contact updated, Broadcast completed and Channel health changed. Only tick the ones your integration truly needs so you don't receive extra traffic.
Verify it works
After saving, go back to the Webhooks list: your new entry appears with the Active toggle green. Trigger one of the subscribed events (for example, send yourself a test message) and open the webhook detail to see the delivery in the Delivery history with status Delivered and code 200.
If it doesn't work
- Nothing arrives: confirm the Active toggle is on and that you ticked the right event.
- Your server receives but rejects: respond with a fast
2xx; if you take longer than the Timeout, it counts as a failure. - Certificate errors: the URL must be HTTPS with a valid certificate.
Tip: start by subscribing a single event to a throwaway endpoint (such as webhook.site) so you can inspect the real payload before pointing it at your production system.
Related articles
Related articles
-
How to connect integrations and external apps
Connect Omnifox with your favorite tools from the integrations catalog in just a few steps.
-
Integrations and API complete guide
Integrations and API in depth, in 30 chapters: API keys, real calls, signed webhooks, n8n, MCP and SDKs, all really working.
-
Connecting Omnifox to Azur, Siigo, Alegra, QuickBooks or another accounting system or ERP
Omnifox doesn't have a native connector for accounting systems or ERPs today. Here's how to connect them anyway with workflows, the HTTP node, n8n, Make, Zapier or the API, with examples.
-
Generate and use API keys and webhooks
Create API keys to access Omnifox programmatically and set up webhooks to receive real-time events.
-
Getting started with integrations (webhook / OAuth / API key)
Connect Omnifox with your other tools: what's available today, what's coming soon, and when to use a webhook, an OAuth connection or an API key.