Appearance
External app connectors
Connectors give a MyChatBot agent access to an outside SaaS tool — a CRM, mailbox, calendar, docs app, or project tracker — so the agent can read and write in that tool on your behalf while it works. You connect the tool once through a secure sign-in (OAuth) on the app's own consent screen, and the agent can then use it during a run. External app connectors are powered by our connector service behind the scenes; you never touch it — you just pick the app brand you want (HubSpot, Gmail, Slack, Notion, …).
This page is for anyone wiring an agent up to an outside tool. For the wider picture of how connectors attach to an agent, see Custom connectors; for the standalone MCP endpoints (Product / Sales-Management / UGC), see MCP & connectors.
Cheat sheet
| What it is | An agent tool into an external SaaS app (HubSpot, Gmail, Notion, Slack, …) |
| How you connect | A one-time secure sign-in (OAuth) on the app's own consent screen |
| Where you connect | Agents → Connectors — https://app.mychatbot.app/agents/connectors |
| Connect scope | Per account — one connection is shared by the whole workspace |
| Where you enable it | The agent's Settings → Connectors section |
| Enable scope | Per agent — each agent has its own on/off toggle |
| The agent can use it when | It's toggled on for that agent and connected on the account |
| Where the tokens live | With the connector service (encrypted) — never in MyChatBot's own storage |
"Connect HubSpot to my agent" = two steps, two scopes
- Connect once (account-wide). Go to Agents → Connectors (
https://app.mychatbot.app/agents/connectors), click the HubSpot card, and complete the sign-in. This makes HubSpot available to your whole workspace. It turns it on for no agent. - Enable per agent. Open the agent → Settings tab → Connectors → toggle HubSpot on → Save.
Connecting a tool and using it on an agent are independent — see Enabling on an agent.
The connect flow at a glance
- Go to Agents → Connectors and click the card for the app you want (e.g. HubSpot).
- You're taken to that app's own sign-in and consent screen.
- Approve the access the agent needs.
- You land back on the Connectors page with the card now marked Connected. — the app is now connected for the whole account —
- Open the agent → Settings → Connectors → toggle the app on → Save to let that specific agent use it.
What a connector is
MyChatBot hand-curates the list of apps you can connect. The catalog spans CRMs, mailboxes, docs apps, calendars, spreadsheets, chat tools, and project trackers. Only apps MyChatBot has added to the curated catalog appear as cards on the Connectors page.
When you connect one:
- The sign-in (OAuth) happens on the app's own domain, and the resulting access tokens are stored, encrypted, by our connector service — not in MyChatBot.
- MyChatBot keeps only a pointer that says "this account has connected HubSpot." No provider access token ever lands in MyChatBot's own storage.
- While the agent works, if it has the app toggled on, it can call that app's actions on your behalf.
Connector ≠ native CRM integration
KeyCRM, SalesDrive, Bitrix24, Kommo, Zoho, Salesforce, Go HighLevel, and Altegio ship as native MyChatBot integrations with their own setup pages (see Integrations overview). Those wire the CRM into the Sales Platform (lead sync, channel sync) and are configured per assistant.
A connector is a different thing: it hands an agent a live tool it can use during a run. Today the only CRM connectors are HubSpot and Pipedrive. The eight CRMs above are native-integration-only — there's no connector card for them in-product. For those CRMs, use the native integration.
Rule of thumb: pick the native integration for Sales-Platform CRM sync; pick a connector (today HubSpot or Pipedrive) when you want an agent to act inside the SaaS tool directly.
Connecting a tool (the sign-in flow)
In the app
Agents → Connectors → https://app.mychatbot.app/agents/connectors. Each card shows the app's logo, a category pill, and — once connected — a status pill. Clicking a disconnected card starts the sign-in; connected cards get an explicit Disconnect button. Use the All / Connected / Available filter and the search box to find an app.
What happens when you connect:
- Clicking a card takes you to the app's own consent screen — the sign-in happens there, not in MyChatBot.
- Approve, and you're bounced back to the Connectors page with the card marked Connected.
- If something goes wrong, the card shows a Needs reconnect note so you can try again.
Connecting only authorizes the account — it doesn't attach the tool to any agent
Everything on the Connectors page happens at account scope: it makes the app available to the workspace. To make an agent actually use it, do the per-agent step in Enabling on an agent.
Abandoning the sign-in leaves nothing behind
If you close the consent screen without approving, no connection is created — there's no half-connected state to clean up. Just start over.
Per-account scoping
Every connection belongs to one account (workspace):
- A connection you make is shared across your whole workspace; it isn't tied to a single agent.
- Because the sign-in is scoped to your account, an agent using HubSpot can only ever reach your HubSpot.
- There's no cross-account sharing — connecting HubSpot in one workspace does nothing for another.
This is the connect scope. Whether a given agent inside the account uses that connection is a separate, per-agent toggle — see below.
One connection per app, per account
You hold one connection per app in a workspace. Reconnecting the same app updates that single connection rather than creating a second one. (An app connector and a Sales-Platform connector can't fight over the same slot — Sales-Platform connectors live in their own Sales Platform category.)
| Connector family | What it connects to | How it connects |
|---|---|---|
| App connector | An external SaaS app (HubSpot, Gmail, Notion, …) | One-time secure sign-in (OAuth) |
| Sales-Platform connector | One slice of your own account's Sales Platform data | Instant — no sign-in needed |
| Custom connector | An MCP server you host yourself | You supply the URL + headers |
Available apps (catalog)
The catalog is hand-curated and sets the order of cards on Agents → Connectors. Currently available:
| Category | Apps |
|---|---|
| CRM | HubSpot, Pipedrive |
| Gmail, Mailchimp | |
| Docs | Notion, Google Drive, Dropbox, OneDrive, Confluence |
| Calendar | Google Calendar, Calendly |
| Data | Google Sheets, Airtable |
| Collaboration | Slack, Discord, Microsoft Teams |
| Projects | Linear, Jira, Asana, Trello, ClickUp, Monday, GitHub, GitLab |
| Support | Intercom, Zendesk |
Only HubSpot and Pipedrive are CRM connectors
The CRM row above is the complete connector CRM list today. Salesforce, Zoho, Bitrix24, Kommo, KeyCRM, Go HighLevel, Altegio, and SalesDrive are native integrations only — see Connector ≠ native CRM integration.
Adding a new app
New apps are surfaced by MyChatBot, not by integrators — it isn't something you can add from the UI. If the app you need isn't in the catalog, request it from the Connectors page (the request option there) or contact support. If you host your own MCP server for the tool, you can instead add it as a Custom connector.
Enabling on an agent
Connecting a tool (the sign-in above) is account-wide and does nothing to any agent by itself. Attaching it to a specific agent is a second, per-agent step: toggle the app on in that agent's Settings → Connectors section.
Two surfaces, two scopes — don't confuse them
| Surface | Scope | What toggling there does |
|---|---|---|
| Agents → Connectors (the catalog) | Account-wide | Runs the sign-in (or disconnect). Makes the app available to the account; enables it on no agent. |
| Agent → Settings → Connectors | This one agent | Turns the app on/off for that single agent. Lists only apps the account has already connected. |
So the catalog page is not where you pick an agent — it authorizes the account. The per-agent picker is where a tool gets attached to an individual agent, and it only shows apps already connected at the account level (if nothing's connected, it links you back to the catalog).
In the app
Agent → Settings → Connectors
- Connect the app once at Agents → Connectors (
https://app.mychatbot.app/agents/connectors). Account-wide. - Open the agent → Settings tab → Connectors. The picker lists only apps your account has an active connection to.
- Toggle the app on, then Save.
A few things to know about the per-agent toggle:
- Each app is a plain on/off for that agent, independent of what other agents have. Each agent starts from its template's default connector set; your toggles override those defaults for that agent only.
- Toggling on does nothing unless the account actually has an active connection to that app. If it's on for the agent but not connected on the account, the agent simply skips it during a run and the card shows Not connected.
See Custom connectors for the full picture of how per-agent enabling works alongside an agent's other tools.
Disconnecting & reconnecting
In the app
On Agents → Connectors, a connected card shows a Disconnect button.
- Disconnecting revokes the stored access and removes the connection. It always clears the connection on MyChatBot's side, so you get the disconnect you asked for.
- Disconnecting is account-wide: it removes the connection for every agent that had the app toggled on. Those agents keep their toggle, but they'll skip the app until you reconnect.
- To reconnect, click the card and run the sign-in again — MyChatBot restores the same connection and clears any error.
A failed run is usually a stale sign-in
If an agent's connector suddenly starts failing with "expired" or "unauthorized" errors, the connection likely needs re-consent. Reconnect the app from Agents → Connectors; that refreshes it to a single, current sign-in.
How this differs from the other surfaces
| Surface | What it is | Who uses it |
|---|---|---|
| App connector | An agent tool into an external SaaS app (this page) | A MyChatBot agent, while it works |
| Sales-Platform connector | An agent tool into one slice of your own account | A MyChatBot agent, while it works |
| Custom connector | An agent tool into an MCP server you host | A MyChatBot agent, while it works |
| Product MCP | Standalone semantic product-search endpoint | External MCP clients (Claude Code / Cursor) |
| Sales-Management MCP | Standalone endpoint driving the whole Sales Platform | External MCP clients / agent slices |
| UGC MCP | Standalone content / posting / analytics / ads endpoint | External MCP clients |
The first three are connectors you attach to an agent; the last three are MCP endpoints you point external tools at. An app connector is firmly in the first group. For the standalone MCP endpoints, see MCP & connectors.
See also
- Custom connectors — the three connector families and how per-agent enabling works
- MCP & connectors — the standalone Product / Sales-Management / UGC MCP endpoints
- Integrations overview — native CRM & tool integrations for the Sales Platform