Make integration

Omnifox and Make (formerly Integromat), connected with two generic modules

There's no Omnifox app on Make's marketplace yet. What you do have today, and what actually works, are signed outbound webhooks and a REST API with its own key. With the "Webhooks" and "HTTP" modules Make already ships with, you can build the same scenario a native app would give you — no waiting, no code.

7 days free. No credit card.

15
events you can listen for via webhook
2
generic Make modules: Webhooks + HTTP
0
Omnifox apps on Make's marketplace, for now
First, some honesty

What exists today between Omnifox and Make

If you search for "Omnifox" in Make's app directory you won't find anything: there's no official connector yet. We're saying this upfront because we'd rather you know now than after building half a scenario looking for a module that isn't there.

Make (formerly Integromat) is especially popular in Spain and Latin America, often ahead of Zapier in those markets, so it makes sense for your automation to live there if you already work with it. The good news is you don't need to wait for the native app: Omnifox notifies Make when something happens in your inbox through a signed webhook, and Make can act on Omnifox by calling its REST API with its own key. Those two pieces, together with the "Webhooks" and "HTTP" modules Make already ships with, build the complete scenario.

There's a third path, less known but just as real: if you already have a flow built in Omnifox's visual editor (say, a welcome sequence or a lead router), you can add the "Incoming webhook" trigger to it and have Make start it with a simple POST, instead of just sending a one-off message.

In one sentence

There's no Omnifox app on Make yet, but with the Webhooks and HTTP modules you can build the same scenario today.

  • Omnifox → Make: signed outbound webhook, 15 events that actually fire
  • Make → Omnifox: REST API with its own key (Bearer token)
  • Make → one of your flows: a webhook URL per workflow, with its own token
  • The native Make app is on the roadmap
What you can automate

What a Make scenario can do with Omnifox

None of this is a future promise: it's what you can already build today with the generic modules.

Kick off a scenario with every message

When a message comes in or goes out, a conversation opens or closes, or a broadcast finishes, Omnifox notifies Make: use it to log to a spreadsheet, alert Slack, or feed your own dashboard.

Sync contacts with your CRM

The contact-created and contact-updated events let you replicate every new record or field change to your CRM, your ERP, or any app Make already connects to.

Follow an appointment's whole lifecycle

Booked, cancelled, rescheduled, confirmed, no-show, completed, slot freed, or someone promoted from the waitlist: all eight appointment events are available as a webhook trigger.

Act on Omnifox from Make

With an HTTP module and your API key, a Make scenario can create or update a contact, send a message, or open a conversation in Omnifox, with no agent touching it by hand.

Trigger an internal Omnifox flow

If you already have an automation built in the visual editor, add the "Incoming webhook" trigger and let Make start it when something happens on its side: a new order in your store, a form submission, whatever it is.

Verify the webhook actually came from Omnifox

Every subscription has its own secret and every delivery arrives HMAC-signed, so your Make scenario can reject any POST that didn't really come from your account.

How it connects today

Your Make scenario working with Omnifox

No need to wait for an app on Make's marketplace: two generic modules build the whole flow.

1

Create the webhook in Make

In your scenario, add the "Webhooks → Custom webhook" module, give it a name, and copy the URL Make gives you. That's the endpoint Omnifox will call.

2

Paste it into Omnifox

In Omnifox, go to Automations → Webhooks → New, paste Make's URL, and choose which events to listen for: messages, conversations, contacts, broadcasts, or the full appointment lifecycle. Saving it generates a secret that signs every delivery.

3

Generate an API key

If your scenario also needs to act on Omnifox (send a message, create a contact), create a key under API Keys → New and save it: it's only shown once.

4

Add the HTTP module and test it

Add an "HTTP → Make a request" module pointing at Omnifox's REST API, with the key as a Bearer token. Run the scenario once from Make and confirm the webhook arrived and the HTTP response was successful.

The real state of this integration

What exists today and what's missing

No "connect with one click" promises that don't exist, and no hiding what actually works.

There's no Omnifox app on Make's marketplace

It isn't published, not on Make and not on any other automation marketplace. It's on the roadmap. Today the connection is signed outbound webhooks plus a REST API, and with the generic "Webhooks" and "HTTP" modules you build the same scenario a native app would give you.

The webhook covers 15 events that actually fire, not everything that happens in your account

The webhook-creation screen lets you check 16 boxes, but one — "channel health changed" — isn't wired to any emitter yet: check it and you'll never receive that webhook. The 15 that do work cover messages, conversations, contacts, broadcasts, and the full appointment lifecycle. Other internal events (orders, boards, CRM) are handled today through an internal Omnifox flow, not a direct outbound webhook.

No infinite retries

Every subscription has its own retry policy (none, linear, or exponential) and a circuit breaker that pauses delivery if your endpoint keeps failing. If Make was down for a while, check the subscription's detail view to see which deliveries were left pending.

You need a plan with API access

Creating the webhook doesn't require a special plan, but for it to actually deliver — and to generate an API key — your workspace needs a plan with API access (Growth or higher). On a lower plan, delivery is silently skipped.

A flow's incoming webhook isn't a generic entry point

The "Incoming webhook" trigger that starts an internal flow has its own token per workflow: it fires THAT specific flow, it doesn't grant access to your whole account, and it doesn't replace the REST API.

Today this connects through webhooks and the API, and here's the step-by-step. The native app on Make's marketplace is on the roadmap; if you need it, write to us and it moves up in priority.

FAQ

Frequently asked questions

It isn't published on Make's marketplace yet. What you do have today is a signed outbound webhook with 15 events that actually fire and a REST API with its own key, which build the same scenario with Make's "Webhooks" and "HTTP" modules. The native app is on the roadmap.
In Omnifox, go to Automations → Webhooks → New, paste the URL from your Make scenario's "Custom webhook" module, and check the "message.received" event. Every incoming message will trigger your scenario.
Yes. Generate a key under API Keys → New and use it as a Bearer token in an "HTTP → Make a request" module pointing at the REST API endpoints, for example to create a contact or send a message.
Yes. If you already have an automation in Omnifox's visual editor, add the "Incoming webhook" trigger: it generates its own URL with a token, and an HTTP module in Make that POSTs to it will start that specific flow.
Message received, message sent, conversation created, conversation closed, contact created, contact updated, broadcast completed, and the eight appointment-lifecycle events: booked, cancelled, rescheduled, confirmed, no-show, completed, slot freed, and waitlist promotion. The screen also lets you check "channel health changed", but that event isn't wired to any emitter yet: don't check it expecting results.
Every subscription has its own secret, and every delivery arrives HMAC-signed in its headers. Your Make scenario can validate that signature before trusting the content.
Creating the webhook doesn't require a special plan, but for delivery to actually work — and to generate an API key — your workspace needs a plan with API access (Growth or higher).
n8n has official Omnifox nodes with native support. For Zapier and other automation platforms, the path is the same as for Make: outbound webhooks plus the REST API, using whichever generic modules each one offers.

Another question? [email protected]

Automate your inbox with Make, starting today

No need to wait for the official app: a signed webhook and an API key build the same scenario. 7 days free, no card required.

Message us on WhatsApp