There's no Omnifox app in the Zapier store yet: you won't find it in the search bar and there's no "Connect account" button. What does exist, and works right now, is a signed outgoing webhook, an action connector, and a full REST API. With that, and the generic "Webhooks by Zapier" block, you can build the same Zap in minutes.
7 days free. No credit card. API access is included starting on the Crece plan.
Search "Omnifox" in the Zapier store and you won't find it. We haven't published a native app there yet, so there's no trigger with its own name, like "New conversation in Omnifox," to pick from a list, and no one-click OAuth account connection. We'd rather tell you here than have you discover it halfway through setup.
What does exist, and is what any published Zapier app uses under the hood, is the infrastructure: signed outgoing webhooks so Zapier can react to what happens in Omnifox, an action connector so Zapier can write back, and a full REST API for anything neither of those covers. Zapier has a generic block for exactly this — "Webhooks by Zapier" — and with two of its steps, "Catch Hook" and "Custom Request," you build the same flow you'd get from a native app.
The practical difference is that setting it up takes ten minutes instead of two clicks. The end result, though, is the same.
No native app yet, but with signed webhooks, an action connector, and the full REST API: today it connects with two "Webhooks by Zapier" steps.
The same thing a "Connect" button would solve, built with two generic Zapier steps.
When a message arrives, a contact is created, a conversation is assigned, an appointment is booked, an SLA is breached, or an order is paid, Omnifox can notify Zapier instantly. That's 49 distinct events, not a generic "something changed."
The action connector already understands five operations: create contact, update contact, find contact, add tag, and send a message. A "Custom Request" step in your Zap is all it takes.
Every webhook goes out with an HMAC-SHA256 signature in the X-Omnifox-Signature header, so whoever receives it can verify the event really came from Omnifox and not from someone who guessed the URL.
If the connector's 5 actions aren't enough, any REST API endpoint — contacts, conversations, messages, tags, campaigns, appointments — is available with a token, documented at /docs.
The same Zap can listen for an Omnifox event and, later in the same automation, write back: for example, tagging the conversation after creating the record in your CRM.
Webhook subscriptions are created, paused, and deleted from your own account. You don't need to ask us for permission to enable or change an event.
The same result a native app would give you, built with two generic Zapier steps.
In Omnifox, go to Settings → Integrations and activate the "Zapier" card: it gives you an inbound URL and a signing key. If you'll need the full catalog of events or the API, also generate a token in Settings → API Keys.
In your Zap, add the "Webhooks by Zapier" → "Catch Hook" step and copy the URL Zapier gives you. Paste it into the outbound field of the "Zapier" card (for the 8 curated events) or create a subscription under Settings → Webhooks if you need any of the 49 events in the full catalog.
For the Zap to write back, add another "Webhooks by Zapier" → "Custom Request" (POST) step pointed at the inbound URL, with the HMAC signature of the body in the X-Omnifox-Signature header and a JSON body with the action: create_contact, update_contact, find_contact, add_tag, or send_message. For anything else, point the same step at an endpoint from /docs with your token in the Authorization header.
Trigger the real event in Omnifox — send a test message or create a contact — and confirm Zapier captured it in the test step. Turn the Zap on and repeat the process for every different event or action you need: each one lives in its own Zap.
We'd rather you know this before you configure anything.
It doesn't show up in Zapier's catalog: no triggers with their own name, no actions with their own name, no one-click OAuth account connection. What exists is the generic infrastructure — webhooks and API — and the "Webhooks by Zapier" block to talk to it.
The "Custom Request" step to our connector understands create contact, update contact, find contact, add tag, and send a message. For anything else — closing a conversation, creating an order, updating a custom field — you need to call the REST API directly with a token, not the connector.
Zapier doesn't ship a built-in step that builds an HMAC-SHA256. If you want to validate the webhook's signature on Zapier's side before acting on it, you need a "Code by Zapier" step. If you'd rather skip that, the action connector still works fine with the signature computed on Omnifox's side, and for the REST API a token in the Authorization header is enough — no signature to compute.
Webhook subscriptions and the action connector are tied to the workspace where they were created. If you run several workspaces, you need a Zap — and a URL — for each one.
API access — where the webhooks come from and where the action connector lives — isn't included in the Lite, Impulsa, or Conecta plans. It's included starting on the Crece plan. If you're on a lower plan, the Zapier connection is paused until you upgrade, not broken.
Publishing to the Zapier store with triggers and actions of its own is something we have planned, not something that exists today. If it's a blocker for you, write to us: knowing who needs it is what moves it up in priority.
None of this is fine print that shows up after you pay: the "Zapier" card, webhooks, and the API work the same way on the free trial, as long as the plan includes API access.
Another question? [email protected]
Signed webhooks, an action connector, and the full REST API. 7 days free to try it, no card required.