Connect n8n, Make.com and Zapier
Connect your Omnifox inbox to n8n, Make.com and Zapier with two-way webhooks to trigger and receive automations.
Watch this step in the video · n8n: install the Omnifox node
What it is and when to use it
Omnifox connects to n8n, Make.com and Zapier through two-way webhooks. You can trigger automations when something happens in your inbox (a message arrives, a contact is created, a conversation closes) and also write back into Omnifox from those tools (create a contact, add a tag, send a message). It's the fastest way to wire your inbox to 1,000+ other apps without writing code.
Before you start
- You need the Administrator role for the workspace.
- Have your n8n, Make.com or Zapier account ready.
Steps
- From the side menu open Settings → Integrations.
- Find the n8n, Make.com or Zapier card and click Connect.
- In the Connect panel you'll see the Inbound Webhook URL. Copy it — that's the address those tools will POST to. It looks like
https://omnifox.io/api/v1/integrations/{type}/{workspaceId}. - Tick the events you want Omnifox to emit outward (for example
conversation.created,message.received,contact.created). - Copy the Signing Secret. Use it to verify the
X-Omnifox-Signatureheader on every call so you know the event truly came from Omnifox. - Click Activate to save the integration.
- In n8n/Make/Zapier, paste the Webhook URL into the inbound webhook step. To write back into Omnifox, configure an HTTP POST to that same URL with an
actionfield (create_contact,update_contact,find_contact,add_tagorsend_message) and sign the body with HMAC-SHA256 using the Signing Secret.
Verify it works
Fire a test event (for example, message one of your channels). You should see the run land in n8n/Make/Zapier within seconds. For the reverse direction, send a test POST with action: find_contact — a 200 response confirms the signature is valid and the integration is live.
If it doesn't work
- 403 Invalid signature: the HMAC doesn't match. Regenerate the Signing Secret in Omnifox, or make sure you sign the raw request body and prefix it with
sha256=. - 404 Integration not active: go back to Integrations and confirm the card shows as connected/active.
- No events arriving: check that you selected the right events on activation and pasted the URL with no extra spaces.
Tips
- Message payloads include a signed
media_download_urlvalid for 24h so you can fetch attachments without a token. - Start with a single event, validate the flow, then add the rest.
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.