Salesforce integration

Connect Salesforce to your Omnifox inbox

We've already built a native Salesforce OAuth connection inside Omnifox: authentication against your own Connected App, Contact import, and automatic token refresh. It's written and tested in the code, but we haven't switched it on for customers yet — we still need to load production credentials. In the meantime, this page shows you the path that works right now.

7 days free. No credit card.

1
native OAuth connector already written, on its way to launch
0
Omnifox apps on the AppExchange (a separate, non-required step)
4
Salesforce objects you can move today: Lead, Contact, Opportunity, Case
First, some honesty

What exists today between Omnifox and Salesforce

There are two different things worth keeping apart. The first: Omnifox already has a native OAuth connection to Salesforce built — you'll see the card under Settings → Integrations — that authenticates against the Connected App you register in your own org, detects whether it's production or a sandbox, stores your Salesforce's real instance_url, and pulls your Contacts into Omnifox. It's written, tested, and ready in the code.

The second: that connection isn't switched on for customers yet. In production we still need to load the Connected App credentials on Omnifox's side, so today, if you click "Connect" on that card, the system tells you it still needs to be configured — it doesn't break, it simply doesn't complete the connection yet.

That doesn't depend on publishing an app on the Salesforce AppExchange — those are separate things. The AppExchange is Salesforce's app marketplace, with its own security review, which is long and paid. We don't have anything published there either, and it is on our roadmap, but that listing isn't required for the OAuth connection to work between the two sides once we load the credentials.

While we switch that connection on, the path that already works today is the same one any integration without a packaged connector uses: the Salesforce REST API called from the "HTTP Request" node of an Omnifox flow, our own webhooks for the other direction, and — if you'd rather not build it by hand — n8n, which ships a native Salesforce node with built-in OAuth handling out of the box.

In one sentence

The OAuth connection to Salesforce is already built in Omnifox's code, but it isn't switched on for customers yet; in the meantime, the REST API, our own webhooks, and the HTTP request node do the same job today.

  • Native OAuth with your Connected App: already written, pending production credentials
  • Once it's switched on, it imports your Salesforce Contacts into Omnifox
  • It doesn't depend on an app on the AppExchange: they're separate processes
  • The HTTP request node and our own webhooks already work today, no waiting required
What you can build today

What you can move between Salesforce and Omnifox

Using the HTTP request node, our own webhooks, and n8n — no need to wait for us to switch on the native connection.

A Lead as soon as a conversation comes in

An Omnifox flow, triggered by a new conversation or a tag being added, uses the HTTP request node to create or update the Lead in Salesforce, with the contact and the source channel as reference.

Contact and Opportunity kept in sync

The same node upserts against /services/data/v59.0/sobjects/Contact or /Opportunity, using email or phone as the key — no need to write an integration from scratch.

Support Cases with context

An open Case in Salesforce can trigger, via a Salesforce Flow or Apex callout, a webhook that reaches an Omnifox flow and notifies the team or sends the customer a message — without them having to write in twice.

Both directions, not just one

The "Incoming webhook" trigger in Omnifox flows gives you a unique URL per flow: a Salesforce Flow or Apex callout can call it directly to report a stage change or a closed deal, without going through n8n if you'd rather not.

Authentication with your own Connected App

You authenticate against Salesforce with the Connected App you create in your own org — OAuth 2.0, either authorization code or JWT bearer for server-to-server. The token is yours; it doesn't depend on whether Omnifox's native connection is switched on yet.

The same flow engine you already use

Since it's a regular Omnifox flow, it combines with the same AI nodes, conditions, and wait steps you already use to classify conversations or assign them to a team, before or after touching Salesforce.

How it connects today

From Salesforce to the inbox in practice

While we switch on the native OAuth connection, here's how to build it today — with or without n8n.

1

Create a Connected App in Salesforce

From Setup → App Manager in Salesforce, create a Connected App enabled for OAuth. That's where you get the Client ID and Client Secret that whoever calls the API will use: n8n, or the HTTP request node in your Omnifox flow.

2

Choose the path: n8n or a direct HTTP request

If you want OAuth renewal to run on its own, build the flow in n8n with its native Salesforce node plus the Omnifox node (n8n-nodes-omnifox). If you'd rather not depend on n8n, add an "HTTP Request" node inside an Omnifox flow and call /services/data/v59.0/sobjects/{Lead|Contact|Opportunity|Case} directly.

3

Trigger the flow from an Omnifox event

Pick the trigger: new conversation, contact created, tag added, deal moved to a new stage. The HTTP request node builds the JSON body with the contact or conversation data and sends it to Salesforce with the current token in the Authorization header.

4

Bring events back with a webhook

For a change in Salesforce to reach Omnifox, use the "Incoming webhook" flow trigger: it gives you a unique URL that a Salesforce Flow or Apex callout can call directly, or route it through n8n's Trigger node if you already built the flow there.

5

Check it in the inbox

The note, tag, or message the flow triggers lands right in the contact's conversation, alongside the rest of the history — no manual exporting, no intermediate spreadsheet to maintain.

Before you add one more system

Do you really need Salesforce, or is Omnifox's own CRM enough?

Salesforce is a huge, proven tool for complex pipelines, forecasting, and organization-wide automation — we're not here to compete on that. But if your "CRM" in practice is keeping track of conversations that turn into deals, you might not need to run two systems.

Built-in CRM included from the Lite plan
Pipeline

Deals with stages, no exporting required

Omnifox ships its own sales pipeline: deals with amount, currency, probability, owner, expected close date, and forecast category, organized on a drag-and-drop board.

  • Configurable stages, with Won and Lost columns that close the deal on their own
  • Accounts grouping several contacts under the same customer
  • Activity — calls, meetings, notes, tasks — on the same timeline
Already connected

The pipeline lives in the same inbox

There's nothing to sync for the deal to know which conversation it came from: contacts, conversations, and deals share the same customer record inside Omnifox.

  • No sync, no duplicating the contact across two systems
  • Your WhatsApp, Instagram, or email history sits right next to the deal
  • Included from the Lite plan on — it's not a separate module you have to turn on
When Salesforce is the right call

And when you genuinely need it

If you've already built approval processes, multi-team forecasting, custom objects, or org-wide reporting on top of Salesforce, Omnifox's CRM doesn't replace that. That's what this page is for: connecting the two, not choosing one.

  • Custom objects and complex automation: Salesforce's home turf
  • Org-wide data governance
  • This page is about connecting the two, not about dropping Salesforce
The real state of this integration

What exists today and what's missing

No "one-click connect" promises that don't exist yet, and no hiding what's already been built.

The OAuth connector is built, just not switched on

Authentication with your Connected App, sandbox detection, Contact import, and automatic token refresh — it's all written. The only thing missing is loading production credentials on Omnifox's side, so today the "Salesforce" card under Settings → Integrations tells you it still needs configuring instead of completing the connection.

The AppExchange app is a separate matter

It isn't published, and it isn't under public review. It's on our roadmap. The security review Salesforce requires to publish on the AppExchange is a long, paid process — but it isn't a requirement for the OAuth connection to work between the two sides.

No Salesforce-specific node in the flow editor

Of Omnifox's flow node executors, only HubSpot (contact upsert) and Google Sheets (append row) have a packaged, per-object integration. For Lead, Opportunity, or Case you use the generic HTTP request node, pointing it yourself at the object and the fields.

The HTTP request node doesn't refresh the token on its own

Unlike the native Salesforce node that ships with n8n, Omnifox's HTTP request node just sends whatever token you give it in the header as-is: it doesn't know about OAuth and doesn't refresh anything on its own. If the token expires, you have to bring a new one — that's why n8n tends to be more convenient for this.

The HTTP request node isn't on every plan

It is available from the Impulsa plan upwards (Impulsa, Conecta, Crece, Escala and Exclusivo). It does not appear on Lite.

We won't quote API limit numbers we don't control

Salesforce sets its own API call limits based on your org's edition and license count, and updates them from time to time. We won't make up a number here: check the current limit in your own org (Setup → System Overview / Limits) before designing a high-volume flow.

If you need us to switch on the OAuth connection with your production credentials, or to publish the app on the AppExchange, write to us: knowing who needs it is what moves it up in priority.

FAQ

Frequently asked questions

It's built into the code: OAuth authentication with your own Connected App, Contact import, and automatic token refresh. It just isn't switched on for customers yet — in production we still need to load Omnifox's Connected App credentials. If you click "Connect" under Settings → Integrations today, you'll see a notice that it still needs configuring, not a completed connection.
No, it isn't published yet — it's a long, paid security review process, and it's on our roadmap. That listing isn't required to connect Salesforce to Omnifox through the API: they're separate matters.
With the Salesforce REST API called from the HTTP request node in an Omnifox flow, our own webhooks for the other direction, and — if you'd rather not build it by hand — n8n, which ships its own native Salesforce node.
With the Connected App you create in your own Salesforce org: OAuth 2.0, using either the authorization code flow or JWT bearer for server-to-server. Omnifox's HTTP request node doesn't refresh the token on its own — you have to bring a valid one — which is why n8n, which does handle refresh in its native Salesforce node, tends to be more convenient for this.
Whichever ones you need: Lead, Contact, Opportunity, Case, or any custom object, because the HTTP request node calls /services/data/v59.0/sobjects/{object} directly — it isn't limited to a fixed list. The automatic import the native connection ships with, once we switch it on, brings in the Contact object.
Salesforce sets its own API call limits based on your org's edition and license count, and updates them from time to time — we won't quote a number here because we don't control it. Check the current limit in your own org, under Setup → System Overview / Limits, before designing a high-volume flow.
It is available from the Impulsa plan upwards (Impulsa, Conecta, Crece, Escala and Exclusivo). It does not appear on Lite.
For the team handling the conversation who needs to see the deal without leaving the inbox: Omnifox ships its own deal pipeline, stages, and accounts, included from the Lite plan. It doesn't replace what you've already built in Salesforce for complex processes; it's there so you don't duplicate the contact across two systems when the deal starts in a conversation.
As soon as we load the production credentials for Omnifox's Connected App. We don't have a public date yet — if it's urgent for you, write to us and help move it up in priority.

Another question? [email protected]

Connect Salesforce to your Omnifox inbox today

The native connection is built and on its way to launch. In the meantime, the REST API, our own webhooks, and the HTTP request node are already enough to move you in both directions. 7 days free, no card.

Message us on WhatsApp