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.
Watch this step in the video · The integrations page
Today Omnifox has no native integration with Azur, Siigo, Alegra, QuickBooks, Contífico, SAP, Odoo or other accounting systems or ERPs. There's no "Connect" button for them in Settings → Integrations. You can still connect them: almost all of these systems have an API, and Omnifox has several ways to talk to it.
Four ways to connect them
| Tool | What it's for | Plan |
|---|---|---|
| Workflows with the HTTP Request node | When something happens in Omnifox (a deal is won, an order is paid), call your accounting system's API directly. | Workflows on all plans; HTTP node from Impulsa |
| n8n, Make or Zapier | Act as a no-code bridge: Omnifox sends the event, the tool transforms the data and sends it to your accounting system (with its connector, if there is one, or with its HTTP module). | Connected in Settings → Integrations |
| REST API and outgoing webhooks | Let your ERP or your tech team read and write in Omnifox (contacts, deals, messages) and receive events in real time. | From Crece |
| AI agent HTTP custom actions | Let the AI agent query your system during the chat (for example, an invoice's status or the outstanding balance). | From Impulsa |
To receive data from your ERP and trigger a workflow with it (workflow inbound webhook), you need the Escala plan.
Example 1: create the customer in your accounting system when a deal is won
- Go to Settings → Workflows and create a new workflow.
- Choose the Deal won trigger (you can limit it to one pipeline).
- Add the HTTP Request node:
- Method: POST.
- URL: your accounting system's customers endpoint (it's in their API documentation).
- Headers: whatever authentication your system requires, for example
Authorization: Bearer YOUR_TOKEN. - Body: the customer data with Omnifox variables, for example
{"name":"{{$contact.name}}","email":"{{$contact.email}}","phone":"{{$contact.phone}}"}. Adjust the field names to the ones your system expects.
- Connect the error output to an alert for your team (by email or an internal comment), so nobody finds out late if the accounting API fails.
- Turn on the workflow and test it by winning a test deal.
If your accounting system needs an extra step (for example, checking whether the customer already exists by tax ID), do it in n8n or Make: the HTTP node sends the data to an n8n/Make webhook and you build the logic there.
Example 2: record a paid order
- Create a workflow with the Order paid trigger (or Order created, if you invoice on confirmation).
- Add an HTTP Request node that sends the order to your accounting system or to an n8n, Make or Zapier webhook.
- In the bridge tool, create the invoice or sales receipt in your system with the order data (customer, products, total).
- Optional: at the end, send the customer a message with the invoice number.
Example 3: let the AI answer "how much do I owe?"
With an HTTP custom action on the AI agent, the agent calls your system with the customer's ID or email and replies with the outstanding balance or the invoice status, without a person having to look it up.
Before you start
- Ask your accounting provider for API credentials (token, integration user) and the endpoint documentation.
- Test in a sandbox or with a test company in the accounting system, if it offers one.
- Every workflow run counts toward your plan's monthly execution quota.
Common problems
- The HTTP node shows a lock: you're on the Lite plan. The node is available from Impulsa.
- The accounting API returns 401 or 403: the token expired or lacks permissions. Generate a new one in your accounting system.
- Duplicate customers are created: check whether the customer exists first (in n8n or Make) before creating it.
- I don't see Azur, Siigo, Alegra or QuickBooks in Integrations: that's expected, there's no native connector. Use one of the four options above.
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.
-
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.
-
The Omnifox REST API: introduction and plan requirements
What the Omnifox REST API is, which plan you need (Crece and up), how to authenticate with the X-API-Key header, and where the docs live.