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.