> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replybubble.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect ReplyBubble to Slack, Microsoft Teams, WhatsApp, and more

ReplyBubble connects with the tools you already use. When a visitor fills out a form or starts a chat, you can automatically send that data to your CRM, get notified in Slack, or trigger any workflow -- no code required for most setups.

***

## Integration Availability by Plan

| Integration          | Free | Pro | Business | Status      |
| -------------------- | :--: | :-: | :------: | ----------- |
| Webhooks             |  Yes | Yes |    Yes   | Available   |
| Slack                |  --  | Yes |    Yes   | Available   |
| Microsoft Teams      |  --  | Yes |    Yes   | Available   |
| Email Notifications  |  --  | Yes |    Yes   | Available   |
| REST API             |  --  | Yes |    Yes   | Available   |
| User Verification    |  --  | Yes |    Yes   | Available   |
| Single Sign-On (SSO) |  --  |  -- |    Yes   | Available   |
| WordPress            |  Yes | Yes |    Yes   | Available   |
| Shopify              |  Yes | Yes |    Yes   | Available   |
| Email Channel        |  --  | Yes |    Yes   | Available   |
| WhatsApp             |  --  |  -- |    Yes   | Available   |
| Facebook Messenger   |  --  |  -- |    Yes   | Available   |
| Instagram DMs        |  --  |  -- |    Yes   | Available   |
| Zapier               |  --  | Yes |    Yes   | Coming soon |
| Google Calendar      |  --  | Yes |    Yes   | Coming soon |
| Make                 |  --  |  -- |    Yes   | Coming soon |
| n8n                  |  --  |  -- |    Yes   | Coming soon |
| HubSpot              |  --  |  -- |    Yes   | Coming soon |
| Zendesk              |  --  |  -- |    Yes   | Coming soon |

"Coming soon" integrations already appear in the **Integrations** catalog in the dashboard so you can see what's planned, but they aren't connectable yet. The plan column shows where each will land at launch.

***

## Notification Channels

Notification channels are the core of ReplyBubble's integration system. Each channel sends real-time notifications to a destination whenever specific events happen in your workspace.

### Channel Types

| Type                | Available On | How It Connects                                      |
| ------------------- | ------------ | ---------------------------------------------------- |
| **Webhook**         | All plans    | HTTP POST to any URL you specify                     |
| **Slack**           | Pro+         | Posts to a Slack channel via an Incoming Webhook URL |
| **Microsoft Teams** | Pro+         | Posts to a Teams channel via a webhook connector URL |
| **Email**           | Pro+         | Sends an email to the address you specify            |

### Event Toggles

Each channel can be configured to trigger on specific events. All events are enabled by default when you create a channel -- turn off any you don't need.

| Event             | What Triggers It                                              |
| ----------------- | ------------------------------------------------------------- |
| New Contact       | A new contact is captured                                     |
| Contact Qualified | A contact is marked as qualified                              |
| Booking Requested | A contact requests a booking                                  |
| Contact Deleted   | A contact is deleted                                          |
| SLA Breach        | A conversation misses its first-response or resolution target |

For example, you might want Slack notifications only for SLA breaches, while a webhook receives every event for logging.

Form submissions are also delivered to your channels (this is how [form routing](/forms-and-lead-capture#routing-form-data) works) — they aren't part of the toggle list above.

### Testing Channels

After creating a channel, click the **Test** button to send a sample notification. This verifies the connection works before relying on it for real traffic.

### Delivery Logs

Each channel shows a log of recent deliveries with status indicators (success or failure). Use this to diagnose issues if notifications stop arriving.

### Setting Up a Channel

1. Go to **Integrations** in the sidebar.
2. Click the **Notification Channels** tab.
3. Click **Create Channel**.
4. Choose the channel type (Webhook, Slack, Teams, or Email).
5. Enter the destination (URL for webhooks/Slack/Teams, or an email address).
6. Select which events to send.
7. Save and test.

***

## Webhooks (All Plans)

Webhooks are available on every plan, including Free. They let you send real-time notifications to any URL whenever something happens in ReplyBubble.

**What you can do:**

* Get notified the instant a new contact is captured, qualified, deleted, or requests a booking, or when a conversation breaches its SLA target.
* Receive a JSON payload with the event data you need to act on.
* Connect to any system that accepts incoming HTTPS requests.

**Security:** Webhook channels can be configured with an HMAC secret. ReplyBubble signs each delivery with `X-Webhook-Signature` (HMAC-SHA256 of the JSON body) so you can verify a payload actually came from ReplyBubble before trusting it.

**Tip:** Before connecting a production system, test your webhook with a tool like [webhook.site](https://webhook.site). You'll see exactly what data ReplyBubble sends so you can plan your integration.

***

## Slack (Pro)

Get notified in a Slack channel whenever new contacts come in or an SLA is at risk. Your team stays in the loop without checking the dashboard.

**How to set it up:**

1. In Slack, create an [Incoming Webhook](https://api.slack.com/messaging/webhooks) for the channel you want notifications in, and copy the webhook URL.
2. In ReplyBubble, go to **Integrations** in the sidebar and click the **Notification Channels** tab.
3. Click **Create Channel**, select **Slack**, and paste the webhook URL.
4. Select which events should trigger a notification.
5. Save and test.

Notifications use Slack's Block Kit and include the contact's name, email, and company (when available) plus a deep link back to the conversation in your ReplyBubble inbox.

***

## Microsoft Teams (Pro)

Works just like the Slack integration -- receive notifications in a Teams channel via a webhook connector, no OAuth required.

**How to set it up:**

1. In Teams, add an **Incoming Webhook** connector to the channel you want notifications in, and copy the webhook URL.
2. In ReplyBubble, go to **Integrations** in the sidebar and click the **Notification Channels** tab.
3. Click **Create Channel**, select **Microsoft Teams**, and paste the webhook URL.
4. Select which events should trigger a notification.
5. Save and test.

***

## Email Notifications (Pro)

Get an email whenever a new contact comes in, gets qualified, requests a booking, or a conversation breaches its SLA -- useful if your team isn't on Slack or Teams.

**How to set it up:**

1. Go to **Integrations** in the sidebar and click the **Notification Channels** tab.
2. Click **Create Channel** and select **Email**.
3. Enter the recipient's email address and select which events to send.
4. Save and test.

***

## REST API (Pro)

For teams that need programmatic access, the Pro and Business plans include a REST API.

**What you can access:**

* Conversations -- read, search, and export chat history.
* Contacts -- create, update, and query your contact database.
* Analytics -- pull metrics into your own dashboards or reporting tools.

**Authentication:** API key-based. Generate and manage keys in the **Integrations > API Keys** tab.

### Managing API Keys

1. Go to **Integrations** in the sidebar
2. Click the **API Keys** tab
3. Click **Generate Key** to create a new one
4. Copy the key immediately -- it is only shown once

You can also rotate a key (generates a new one and invalidates the old one) or deactivate a key entirely. Each key shows its creation date and status.

> **Security:** Treat API keys like passwords. Never commit them to source control or share them in plaintext. Store them in a secret manager or environment variable. If a key is exposed, rotate it immediately from the API Keys tab.

**Who it's for:** The REST API is designed for teams with developers who want to build custom integrations or embed ReplyBubble data into internal tools. If you're not sure whether you need it, the webhook integrations (available on all plans) likely cover your use case.

***

## User Verification (Pro)

If your visitors are logged-in users, you can pass their identity to ReplyBubble so conversations are attributed to real people instead of anonymous visitors. This uses HMAC signature verification to prevent impersonation.

See the full guide: [User Verification](/user-verification).

***

## WordPress (All Plans)

Add ReplyBubble to your WordPress site in just a few clicks using our official plugin. No code editing required.

**How to set it up:**

1. Go to **Integrations** in the sidebar and choose **WordPress**.
2. Download the ReplyBubble WordPress plugin.
3. Upload and activate the plugin in your WordPress admin dashboard.
4. Paste your **Widget ID** into the ReplyBubble settings in WordPress.

For detailed instructions, see the [WordPress Integration Guide](/integrations/wordpress).

***

## Shopify (All Plans)

Embed the ReplyBubble chat widget directly into your Shopify storefront. It works with all Shopify themes, including Online Store 2.0, with zero impact on store speed.

**How to set it up:**

1. Go to **Integrations** in the sidebar and choose **Shopify**.
2. Copy your **Widget ID** embed snippet.
3. Open your Shopify theme editor and paste the snippet into your `theme.liquid` file before the closing `</body>` tag.

For detailed instructions, see the [Shopify Integration Guide](/integrations/shopify).

***

## Omnichannel Inbox: Email, WhatsApp, Messenger & Instagram

Beyond the chat widget, ReplyBubble can receive and reply to messages from a forwarding email inbox, WhatsApp Business, Facebook Messenger, and Instagram DMs -- all landing in the same AI-powered Live Inbox as your widget conversations, with the same auto-responses and human handoff behavior.

Email Channel is available on **Pro**; WhatsApp, Messenger, and Instagram require **Business**. Each channel is connected from **Integrations** in the sidebar, under **Messaging Channels**.

See the full guide: [Omnichannel Inbox](/integrations/omnichannel).

***

## Single Sign-On (SSO)

Let your team sign in with your company's identity provider (Okta, Azure AD, Google Workspace, or any SAML 2.0 IdP) instead of individual ReplyBubble passwords. SSO is a **Business plan** feature, configurable only by the workspace **Owner**, found at **Integrations > Single Sign-On (SSO)**.

See the full guide: [Single Sign-On (SSO)](/integrations/sso).

***

## Coming Soon

The following integrations appear in the dashboard's Integrations catalog but are still under development:

| Integration         | Plan     | What it will do                                                                |
| ------------------- | -------- | ------------------------------------------------------------------------------ |
| **Zapier**          | Pro+     | Connect ReplyBubble to thousands of apps through Zapier's automation platform. |
| **Google Calendar** | Pro+     | Let customers book meetings directly from the chat widget.                     |
| **Make**            | Business | Build visual automations with advanced branching logic.                        |
| **n8n**             | Business | Self-hosted workflow automation for developers.                                |
| **HubSpot**         | Business | Sync contacts and conversations to HubSpot CRM.                                |
| **Zendesk**         | Business | Escalate conversations into Zendesk tickets.                                   |

Until n8n has a dedicated connector, you can still trigger n8n workflows today using a generic **Webhook** channel (available on every plan) pointed at an n8n Webhook trigger node -- it just won't have the polish of a native n8n node.

***

## Need Help?

If you're unsure which integration fits your workflow, reach out through the chat widget on our site. We're happy to point you in the right direction.
