Integrations
An integration is a connected account. Connecting one is a set-up-once job; once it’s connected, its actions become available as Tools your AI agent can call mid-conversation.
Integrations live at Dashboard → AI → Integrations.
Integrations vs. Tools. Connecting Shopify does nothing on its own. It makes
Shopify’s actions available. You then add the ones you want — say
lookup_order — as tools on the Tools page, and the agent calls
those. One connection, as many tools as you like.
The three sections
The page groups providers by what you can do with them right now.
| Section | Meaning |
|---|---|
| Connected | Live. Its actions can be added as tools. Hidden when you have none. |
| Available | Ready to connect on this account. |
| Coming soon | Not connectable yet — either not enabled on this instance, or still in provider review. |
Providers
| Provider | What it’s for | How you connect |
|---|---|---|
| Slack | Send messages to channels — internal alerts when the agent captures something. | OAuth, then pick a channel |
| Shopify | Search products, look up orders, report order status. | Store credentials |
| Google Sheets | Append leads to a sheet, look up rows. | OAuth, then set a default spreadsheet |
| Calendly | Create one-off booking links, list event types. | API token |
| MCP Server | Connect a Model Context Protocol server; its tools are discovered live. | Server URL + credentials |
| Custom Webhook | Send structured data to an HTTPS endpoint you own. | Your URL |
| Google Calendar | Book appointments, check availability. | Coming soon |
Google Calendar is not connectable yet. It sits in Coming soon while Google’s OAuth verification is still in progress — connecting before that completes would send you through an “App not verified” consent screen. If you need calendar booking today, use Calendly.
Connecting one
Open Integrations
Dashboard → AI → Integrations. Search if the list is long.
Connect
Click the provider’s card and follow its flow — an OAuth consent screen, or a field for a token or store credential.
Finish provider-specific setup
Some providers need one more choice before they’re useful:
- Slack — pick the channel messages go to. You can change it later with Change channel.
- Google Sheets — set a default spreadsheet.
- MCP Server — Vibot discovers the server’s tools and caches them.
Add the actions as tools
The connection is now live, but the agent still can’t use it. Go to Tools → Create Tool → Integrations and add the specific actions you want.
Credentials and security
- Credentials are encrypted at rest (AES-256-GCM) and decrypted only at call time.
- They are never shown again after saving. To change one, paste a new value — leaving the field blank keeps the existing secret.
- Custom webhook endpoints must be HTTPS. Plain HTTP is refused.
Disconnecting
Disconnecting is a soft disconnect: the provider goes inactive and its tools stop working immediately, but your stored credentials are kept so reconnecting is one click rather than a fresh setup.
Tools built on a disconnected provider stay in your tools list and stay enabled, but fail when the agent calls them. Disable or delete those tools too, or the agent will keep trying to use something that can’t respond.
Plan availability
| Integration | Minimum plan |
|---|---|
| Google Sheets, Google Calendar | Lite |
| CRM integrations, in-chat payments | Pro |
| Zapier | Growth |
Slack, Shopify, Calendly, MCP and Custom Webhook availability depends on what’s enabled for your account — if you can see the card outside Coming soon, you can connect it. See Pricing for the full plan matrix.
Related
- Tools — turn a connection into an action the agent can call
- Webhooks (API) — receive events from Vibot, the other direction
- Features overview — every dashboard page