Reach into the tools you already pay for

A chatbot without integrations is a chatbot that talks. A chatbot with integrations is a chatbot that works— it creates records in your CRM, opens tickets in your helpdesk, looks up orders in your store, and notifies your team in Slack. The conversation isn’t just answered. It produces something your team can act on.

Each integration is a card in your bot’s Integrations tab. You connect through a form (and an OAuth flow for most), toggle which actions the bot is allowed to use, and the integration goes live. Disconnect with one click; anything the bot already created in the connected tool stays there, untouched.

Every integration follows one or both of two patterns. They’re kept separate by design so you decide what fires automatically (Pattern 1) and what the model can do during a conversation (Pattern 2). Most of our integrations support both. Each pattern has its own set of toggles.

When you read each integration’s detail page, you’ll see which patterns it supports. Salesforce supports both. Slack supports only Pattern 1. Shopify is mostly Pattern 2 (the bot looks things up live; it doesn’t auto-create records on every chat). The patterns scope what your bot can and cannot do per tool.

Capture leads in real time and look up records during a conversation. If your sales team lives in a CRM, this is where most of the “turn chatbot conversation into pipeline” work happens.

Open tickets on escalation, search articles in your knowledge base, and pull ticket state live during a chat. Your support inbox handles fewer routine questions, and the tickets that do land carry full conversation context.

The bot can answer real e-commerce questions because it can look up real e-commerce data. Order status, inventory level, product details, discount validation, store policies — all available to the bot at the moment of the conversation.

Some conversations don’t need a CRM entry or a ticket — they just need a teammate’s attention. Slack notifications let you watch for the conversations that matter without leaving your team’s normal workflow.

The nine integrations above are the ones we support natively, with first-party code, first-party documentation, and first-party security review. For everything else, three options.

If you’re evaluating NebulaHex and want a specific integration we don’t list natively, get in touch. The integration roadmap is partly demand-driven, and named-customer asks usually move things up the queue.

Most teams start with their CRM. Sales leadership wants leads in the pipeline, not in transcripts. From there, helpdesk integration usually goes on second (so escalations land where the support team already works), then commerce or comms based on what your business actually does.