Grok Bot connectors are the app connections that let xAI's Grok Bot work inside services like Gmail, Slack, Notion, GitHub and Google Calendar through a structured link instead of clicking through a website. You add them from Connect Apps, sign in once, and every Bot on your account can use them. This page covers how connecting works, what the sign-in states mean, how permissions and team rules apply, and what changed in the latest releases up to v0.78.1 (27 October 2026).
📺 Watch: Grok Bot Just Got a MASSIVE AI Upgrade!
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
If you want the plugin catalogue itself, read the Grok Bot plugins guide. This page is about the connection layer: signing in, staying signed in, and who is allowed to use what.
What Grok Bot connectors are
xAI's docs describe apps as "a structured way to work with services" and say they are more reliable than driving a website when an app exists. The Bot still has a browser on its cloud computer for services with no connector, or for visual work an app does not expose. See the Grok Bot computer use guide for that side.
The words connector, app and plugin overlap in xAI's own wording. The plugin is the thing you install from the catalogue. The connector is the signed-in link to your account in that service. A plugin can be installed and still not connected, which is the most common source of confusion.
- Account-wide. A connected app is available to every Bot you run.
- Same access as you. An app can only do what the authorized account can already do. It cannot raise access or change sharing.
- Tokens stay off the Bot's computer. xAI's docs say OAuth tokens are held on the connector backend, and the Bot calls tools without receiving them.
Want the exact prompts and setups people use to put connected Bots to work in a business? The AI Profit Boardroom shares them every week for $69/mo.
How to connect Grok Bot connectors
- Open Connect apps from the sidebar, or tap an in-chat Connect card. On the phone, tap your avatar and choose Connect apps.
- Browse or search for the app and choose Add. Since v0.77.0, Add installs the plugin and opens its sign-in in one click.
- Finish the provider login in your browser when asked to Authorize or Authenticate.
- Confirm the app sits under Installed.
- In chat, type @ to attach the app to a task.
You can also just ask. Say "Add the Linear app" and the Bot searches the catalogue, installs it and shows a Connect card if you need to sign in. The tools are ready from your next message. Since v0.75.2, naming a service makes the Bot show that connector's card in its first reply.
Connectors also show up where you need them. In v0.77.0, when the Bot hands you its computer to sign in to sites like Google, GitHub or QuickBooks, it offers their connector, and connecting ends the handoff. In v0.78.1 xAI added connector offers on the sign-in pages of Cloudflare, Coinbase, Gusto, YouTube, Railway, Google Ads, Meta Ads and TikTok for Business.
After your first app connects, the Bot offers one more that pairs with it, such as Google Calendar after Gmail. For the Gmail setup itself, see the Grok Bot Gmail guide.
📺 Watch: GrokBot Just got a WILD Update!
Grok Bot connectors status labels and sign-in timeouts
The labels tell you what to do next. This is the table to keep open when a connector misbehaves.
| What you see | What it means | What to do |
|---|---|---|
| Added | Installed, not signed in | Open the app and choose Authenticate |
| Needs auth or Disconnected | Sign-in missing or lost | Choose Authenticate (Authorize on the phone) |
| Authenticate in place of Connected | The sign-in expired (v0.75.8) | Sign in again |
| Not connected | The connector is signed out (v0.77.0 wording) | Choose Connect |
| Reconnect under Your plugins | A connector stopped working | Choose Reconnect |
| Still signing in? | A connect card open for 10 minutes (v0.78.1) | Finish the login or choose Reopen |
| Disabled by team admin | Blocked by team connector policy | Ask your admin to enable it |
Timeouts have grown over the releases. The troubleshooting page says to finish authorization within about 10 minutes. The changelog says connector sign-ins can finish up to an hour after you start them (v0.77.0), and browser sign-in waits up to 20 minutes with a Copy link option (v0.75.2). If a sign-in needs setup first, the Bot says what to add and opens the plugin page (v0.78.1).
📺 Watch: NEW Grok Bot is INSANE!
Grok Bot connectors that sign you out
Connectors drop for normal reasons: an expired token, a revoked grant, or a company admin block. Recent releases make the Bot explain this rather than fail quietly.
- When a connector signs you out or rejects a sign-in, the Bot says why, such as a restricted Google account, and how to fix it (v0.75.2).
- When a routine hits a signed-out connector, the chat shows a Reconnect card, at most once a day (v0.75.2).
- Background work stops calling a connector that signed you out and tells you to reconnect (v0.77.0).
- When a connector needs a permission its connection can't request, the Bot says reconnecting won't help (v0.78.1).
Company Google accounts are a separate case. xAI's docs say Grok Bot signs in to Google as "Grok", and a Workspace admin has to set Grok to Trusted under App access control. Reconnecting does not clear a Google admin block.
Setting up connectors across a whole business and want a second pair of eyes? Book a free AI strategy session.
Grok Bot connectors permissions and Allow rules
A connector gives access. Auto Review decides whether each action runs. When an action needs you, an approval card offers Allow once, Always allow or Deny. Always allow saves an Allow rule to your Custom Rules.
- You can hold up to 20 Allow automatically rules and 20 Ask first rules, each up to 1,000 characters.
- If both kinds match, Ask first wins.
- Approval cards name a connector by its service, and add the account when two accounts share a name (v0.77.0).
- After a bank or brokerage connector returns data, the Bot asks before sharing it anywhere else (v0.70.2).
Grok Bot connectors on Team Bots and shared Bots
Teams change who a connector acts for. xAI's shared Bots page is clear on one point: a connected account always acts as the person the Bot is answering, and one teammate's connection is never used for someone else.
- A shared Bot uses its owner's apps for everyone. In your own chat with it, it can also use your apps, after asking with Allow once, Always allow or Skip.
- In Slack channels, threads and group chats, a shared Bot uses only its owner's apps. More on that in the Grok Bot Slack guide.
- Linked teammates on a Team Bot use their own connectors and memory (v0.77.0).
- Work a Team Bot hands off in a shared chat says whose connector it used (v0.75.5).
- When a Team Bot routine needs one of your connectors, it asks in the routine's Slack thread and tags you (v0.78.1).
- To make every shared Bot ask again, use Clear connector preferences under Settings, General, Shared Bots.
Admins set policy, not members. xAI's docs say Grok Bot inherits the team's Cursor connector policy, with no separate Grok Bot list. Allowed servers come from the Team Marketplace on the Plugins and MCPs dashboard page. Pushing connectors to members is not available. The MCP allowlist and Network Controls are Enterprise only. The Grok Bot Teams guide covers the admin side.
Custom Grok Bot connectors over MCP
The catalogue is not the limit. xAI's docs say a Bot can add an MCP server that isn't in the catalogue, by URL or by a command that runs on its computer. A command server is then available to your other Bots too. Adding a server on a private network, or one with a private certificate authority, asks for your approval first.
Glean is the named example in the changelog: adding Glean asks for your Glean MCP URL and connects it after you sign in to Glean in your browser (v0.70.2). Connectors that come with an app, such as Figma, Notion and Canva, can show it as an interactive card in the chat. When a connector such as X adds tools or fields, Bots can use them without you reconnecting (v0.75.8).
To see how this connector layer fits a full agent stack for a small business, read the Agent OS guide. For how the underlying models compare, Julian's Goldie Bench tracks his own model testing.
Want weekly walkthroughs of connected Bots running real business tasks? Join the AI Profit Boardroom, or grab a free AI strategy session to map which connectors your team needs first.
FAQ about Grok Bot connectors
Are connectors and plugins the same thing in Grok Bot?
Close, not identical. The plugin is what you install from Connect Apps or Marketplace. The connector is the signed-in link to your account. Added means installed only. You still need to Authenticate before the Bot can use it.
Does every Bot get my connectors?
Yes. xAI's docs say a connected app is available to every Bot you run. A teammate's shared Bot asks before it uses your accounts.
Can I connect a tool that isn't in the catalogue?
Yes. A Bot can add an MCP server by URL or by a command on its computer. Private-network servers ask for approval first, and team policy can block servers.
Why does the Bot say reconnecting won't help?
Since v0.78.1, that message means the connector needs a permission its connection can't request. Signing in again won't add it. Check the service's own settings or ask your admin. For help planning the setup, book a free AI strategy session.
