Bring AI conversations into Salesforce

If your business has reached the point where you’re running Salesforce, you’ve made a decision about where the truth lives. Account hierarchies, opportunity stages, custom objects modeling your specific workflow, reports that leadership reads every week — that infrastructure isn’t easily moved, and it shouldn’t be.

The cost of any new tool you adopt isn’t just the tool itself. It’s the cost of the data drift between that tool and Salesforce. Every system that doesn’t talk to your CRM creates a reconciliation tax that your RevOps team eventually pays.

That’s the design constraint NebulaHex’s Salesforce integration is built around. We don’t ask you to mirror your CRM inside another database. We don’t ask reps to learn a second tool. We connect the conversations to the records you already trust, in the system your team already uses. The bot becomes a participant in the same data fabric, not a parallel one.

Once you connect a Salesforce org to a bot, you unlock ten CRM actionsthe bot is allowed to perform during a chat. They fall into three categories. Each one has its own toggle in the Configure Tools panel — you decide which are turned on. A connected org with every action disabled does nothing. That’s by design.

The bot uses these actions inside live conversations. When a customer asks about a record, the bot can look it up. When a website visitor finishes a guided form, the bot drops a Lead into Salesforce with source attribution and the transcript attached. When a chat escalates, the bot opens a Case in your support queue with full context, so the agent who picks it up isn’t starting from zero.

Salesforce shops take change management seriously. A serious org doesn’t make changes in production without testing them somewhere first. Sandboxes are isolated replicas of your org used to validate changes before they touch live data. Letting you connect NebulaHex to a Sandbox first respects that workflow — you can prove out the bot’s behavior against a copy of your data and configuration, get the tool toggles right, and only then point it at production.

Most teams run a few hundred test conversations through their bot against a Sandbox, watch which tools get used and on what kinds of input, refine their toggles, and then connect Production. The same OAuth flow handles both. The Salesforce card shows the hostname of the org you connected to and a Sandbox badge if applicable, so there’s never any ambiguity about which environment the bot is touching.

The connection flow is short by design.

Disconnection is just as simple. Click Disconnect on the card and the bot stops accessing your CRM immediately. Records the bot already created in Salesforce — Leads, Cases, anything else — stay in Salesforce because that data belongs to your org, not to NebulaHex. Conversations the bot already had stay in your NebulaHex inbox. The link between the two systems is the only thing that goes away, and you can re-establish it any time.

Different roles get different value from the integration. Here’s how it lands for the teams who actually use Salesforce day-to-day.

Salesforce is the largest customer relationship management platform in the world. Sales Cloud has been the leading sales CRM for over two decades, and the broader Salesforce platform has grown into a suite that covers sales, service, marketing, commerce, analytics, and a developer platform that thousands of companies extend with their own logic.

Two things make Salesforce a good target for an AI bot integration. First, the object model is well-defined and predictable: Leads, Contacts, Accounts, Opportunities, Cases, Knowledge Articles. Each has a clean schema the bot can read and write against reliably. Second, Salesforce’s reach inside revenue and support orgs is wide enough that automating conversations into it is leverage — every Lead that doesn’t leak, every Case that arrives pre-formed, saves time across whatever workflow your team has already built.

What NebulaHex adds is the front door. Your knowledge base, your products, your past Cases — combined into a chat-shaped agent that can answer most questions and knows when to step aside.

Plenty of teams have considered building their own Salesforce-aware chatbot. The shape of the project always looks the same: stand up a chat surface, plumb it into the Salesforce API, build a knowledge layer, manage authentication and refresh tokens, handle conversation state, train people on the new internal tool, maintain it forever. It’s months of engineering before the first useful conversation, and the result is a bot only your team knows how to extend.

NebulaHex is shipped. Connecting Salesforce to a knowledge-grounded bot is a few clicks, not a quarter. You get a chat surface that’s already polished, a knowledge ingestion pipeline that already handles URLs, files, and structured Q&A, a widget that’s already brandable, an inbox where your humans can take over conversations, an analytics view that shows which conversations are converting, and integrations with the rest of your stack that work today.

You also get honest scope. The bot resolves what it can automatically, your team handles the conversations that genuinely need a human, and customer satisfaction goes up because your team isn’t drowning in repetitive questions. The Salesforce integration fits inside that frame: it makes the bot’s automatic work better, and it makes the human handoff cleaner.

Your Salesforce org contains some of the most sensitive data your business owns. We treat the connection with that in mind.

Connections use OAuth 2.0 against Salesforce’s own login flow — you authenticate against Salesforce, not against us, and your credentials never pass through our system. The access tokens we receive are encrypted before they’re stored. All data is encrypted at rest and in transit. Disconnecting from the Salesforce card revokes access immediately on our side; revoking from the Salesforce side does the same.

Your conversations and your Salesforce data are never used to train AI models. Each customer’s data is isolated to their own workspace. See our privacy policy and terms for the full posture.

If your business runs on Salesforce, your chatbot should know it. Pick a bot, open the Integrations tab, click Connect on the Salesforce card, choose Production or Sandbox, sign in to Salesforce, approve, configure which of the ten actions you want enabled. You’re done.

Start free. Build the bot, ingest your knowledge, connect Salesforce against a Sandbox if your team prefers that path, graduate to Production when you’re confident in the behavior.