Grok Bot Connectors: Connect, Reconnect And Lock Down Apps (2026)

Grok Bot connectors are the apps you sign in to under Connect apps, so a Bot can work inside Gmail, Google Calendar, Slack or QuickBooks with real tools instead of clicking through the website.

The sign-in is where most setups break, not the install.

The v0.78.1 release on 27 October 2026 changed exactly that part: the Bot now offers a connector on eight named sign-in pages, and a connect card asks "Still signing in?" after 10 minutes.

Below is the order I'd set it up in, from choosing the account to disconnecting cleanly when a project ends.

If you'd rather have my team map which apps your business should connect first, book a free SEO strategy session and we'll walk it with you.

What a connector is, and what it isn't

The computer and apps docs call them apps, and say they are more reliable than the browser whenever one exists.

Use the Bot's browser only for services with no app, or for visual flows the app doesn't expose.

Three facts decide every choice after this.

Account-wide. Connect it once and all of your Bots can call it.
Tokens stay off the computer. OAuth tokens sit on Cursor's connector backend, so the Bot uses the tools but never holds the token.
No extra access. An app can only do what the authorised account can already do, and it can't change sharing.

This page is about connecting and managing those accounts.

For the catalogue side, installing plugins and the 200-skill ceiling, read my Grok Bot plugins walkthrough.

Step 1: Choose the account before you press Connect

App connections belong to the same account you used to sign in to Grok Bot.

The account you authorise inside each app is the real permission boundary.

So pick it on purpose.

Use a scoped service account where the source system supports one.
Use a mailbox the Bot is allowed to send from, not the one your accountant writes to.
Start with read-only jobs and drafts, as the approvals, security and privacy page recommends.

Gmail connects one mailbox at a time.

To switch mailboxes, disconnect the current one and authorise the other.

Some apps, such as Notion, can hold a second account.

Step 2: Connect from Connect apps, a card, or one sentence

There are three doors in, and they end at the same provider login page.

Open Connect apps in the sidebar. On the phone, tap your avatar at the top left first.
Search for the app and add it.
When Grok Bot asks you to Authorize or Authenticate, finish the provider's login in your browser.
Confirm the app sits under Installed.

The second door is an in-chat Connect card.

Since v0.75.2, mention a service by name and the Bot's very first reply carries the connect card for it, per the Grok Bot changelog.

The third door is a plain request such as "Add the Linear app."

The Bot searches the catalogue, installs it, and shows the Connect card if you need to sign in.

The app's tools are ready from your next message.

Then type @ in any chat to attach the app to a task.

🔥 Want every connector wired up on video, step by step? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members connecting agents to their own business apps. → Join the AI Profit Boardroom

Step 3: Read the status, not the Added label

Added means installed.

It does not mean signed in.

The troubleshooting page lists four states, and each has one move.

Status in Connect apps	What I'd do
Needs auth	Choose Authenticate (Authorize on the phone) and finish the sign-in
Disconnected	Same: Authenticate, then retry the task
Disabled by team admin	Get your Cursor team admin to switch it on
Connected	Send a new message and ask the Bot to try the app again

If authorisation was revoked in the source service, choose Remove, add the app again, and sign in.

Also check whether the connector needs an organisation-provided variable or admin setup.

Step 4: Let the Bot offer the connector on sign-in pages

This is the v0.78.1 change I'd lean on most.

When the Bot lands on the sign-in page of one of these services, it offers that service's connector instead of typing your login into the site.

Cloudflare
Coinbase
Gusto
YouTube
Railway
Google Ads
Meta Ads
TikTok for Business

An earlier release did the same during computer handoffs: on a Google, GitHub or QuickBooks login, the Bot suggests the connector, and connecting it closes the handoff.

Take the offer.

A connector gives the Bot structured tools, and the login never touches the shared browser.

Connect your first app and the Bot proposes a natural partner for it, for example Google Calendar once Gmail is in.

Step 5: Finish slow sign-ins inside the right window

Provider logins with SSO, two-factor codes or an admin prompt take time.

The changelog gives you three numbers to plan around.

The troubleshooting page asks you to complete authorisation in the browser within about 10 minutes.
Since v0.78.1, a connect card asks "Still signing in?" after 10 minutes.
Releases from v0.75.2 on let connector sign-ins finish up to an hour after you start them.

If the card says it is waiting, choose Reopen to bring the sign-in page back.

If it says authorisation failed, choose Retry.

If the app's button turns into Reconnect, choose that.

Step 6: Write Ask first rules for each connector

Auto Review decides which actions run on their own and which stop for you.

Under When Grok Bot wants to: describe one action, choose Allow automatically or Ask first, then press Add Rule.

Ask first always wins when both kinds of rule match.

You get up to 20 rules of each kind, each up to 1,000 characters.

Here are the per-connector rules I'd start with.

Ask first before sending any email from Gmail.
Ask first before posting in any Slack channel.
Ask first before changing a campaign budget in Google Ads, Meta Ads or TikTok for Business.
Allow automatically when reading Google Calendar free time.

The changelog also says Ask first and Block rules for Gmail searches and reads hold even when the Bot calls them by another name.

If a Bot should never touch an account, the hard stop is to disconnect that app.

📞 Not sure which apps your business should connect first? Book a free SEO strategy session and my team will look at your stack with you and pick the connectors that save the most hands-on hours. → Grab a free call with my team

Reconnect cards: what each one is telling you

Reconnect cards are not noise.

Each one now says something specific.

Routine hit a signed-out connector. Since v0.75.2 you get a Reconnect card in chat, no more than once per day.
Background work signed out. Background work stops calling that connector and tells you to reconnect.
Reconnecting won't help. Since v0.78.1, if the missing permission is one the connection can't even ask for, the Bot tells you straight out instead of looping you through sign-in.
Google Calendar. It asks you to reconnect only when signing in again can grant the missing permission.
Second Google sign-in. Signing in to an already-connected Google account reuses it, with one reconnect card.

Cards and errors also show the connector's name instead of an internal ID since v0.78.1.

New tools or fields on a connector like X reach your Bots with no reconnect needed.

Connector timeouts: two minutes to reply, three to give up

Slow tools used to fail fast.

From v0.70.2, connector calls wait up to two minutes for a reply, up from one minute, and longer while the connector reports progress.

A connector that stops responding entirely times out after three minutes, a rule the changelog dates to v0.17.0.

When a connector rate-limits you, Bots wait for the retry delay instead of looping.

When Google throttles requests, Google apps stay connected and the Bot tells you to try later.

So a slow call is not a broken connection.

Wait, then check the status in Connect apps before you touch Reconnect.

Google Workspace: when an admin needs to review Grok

Company Google accounts can stop Gmail, Calendar, Drive, Docs, Sheets or Slides before the sign-in finishes.

Grok Bot signs in to Google as Grok, not Cursor.

If the page says Your admin needs to review Grok, request access and wait.

Your IT admin opens Security, then Access and data control, then API controls, then App access control, adds the app named Grok, and sets it to Trusted.

If the page says Access blocked, changing browsers or reconnecting won't clear it.

Only the Google admin's approval does.

Team Bots and shared Bots: whose connector runs

The shared Bots docs are firm that a Bot uses the connections of the person it's replying to.

One teammate's connection is never used for someone else.

In your own chat with a shared Bot, it asks before using one of your accounts.

The card says Allow plus the app name, with Allow once, Always allow or Skip.

Always allow can cover that one Bot or every shared Bot.

To make them all ask again, open Settings, General, Shared Bots, and choose Clear next to Clear connector preferences.

Since v0.78.1, a Team Bot routine that needs your connector tags you with the request inside its own Slack thread.

On a Team Bot, every linked teammate brings their own connectors and memory.

For team admins: the connector policy is inherited

There is no separate Grok Bot connector list.

Grok Bot inherits your team's Cursor connector policy, set in the Team Marketplace on the dashboard's Plugins and MCPs page, per the teams and enterprises docs.

A blocked app shows Disabled by team admin.

You can't push connectors to members, mandatory or default-on.

Blocking an app doesn't block that service's website either.

Closing the website path takes Network Controls, which is Enterprise only.

If you run an allowlist network mode, turn on Apply to MCP servers and add each connector's hosts first, such as googleads.googleapis.com for Google Ads, listed on the security page.

🔥 Get the Agent OS that keeps every app connection in check Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members running Bots across Gmail, Slack and their ad accounts. → Join the AI Profit Boardroom

Disconnect cleanly when a project ends

Access you no longer need is access you should remove.

The approvals docs give a short order for it.

Pause or delete routines that use the app.
Uninstall the connector in Connect apps.
Revoke its authorisation in the source service too.
Review installed connectors and active routines on a schedule.

When a Bot removes an app for you, everything the app added goes with it and you're signed out.

Since v0.75.2, the Bot removes or renames a connector only when you name that change yourself.

Apps your team requires can't be removed at all.

Known connector issues to skip past

Two issues are documented with no fix on your side.

Zoom error 4700. Zoom authorisation from the desktop app fails with an invalid redirect, and there is no workaround yet.
SharePoint AADSTS50011. Application-level permissions show a redirect mismatch, so connect with Delegated permissions and your Microsoft tenant ID instead.

The Google Calendar app also can't add a Zoom link or change Meet settings, so paste the Zoom link into the event yourself.

And the X plugin runs on your own X developer account, which needs X API credits.

Also On Our Network

FAQ: Grok Bot Connectors

Why does Grok Bot say an app is missing when it shows Added?

Added only means installed. Open the app in Connect apps and choose Authenticate (Authorize on the phone) if it shows Needs auth or Disconnected.

How long can a Grok Bot connector sign-in take?

The changelog says connector sign-ins can finish up to an hour after you start them, and from v0.78.1 the card asks "Still signing in?" after 10 minutes.

Which sign-in pages make the Bot offer a connector?

From v0.78.1: Cloudflare, Coinbase, Gusto, YouTube, Railway, Google Ads, Meta Ads and TikTok for Business. Google, GitHub and QuickBooks handoffs offer their connector too.

How long does a connector call wait before it fails?

Calls wait up to two minutes for a reply, longer while the connector reports progress. A connector that stops responding times out after three minutes.

Can a team admin push connectors to every member?

No. Grok Bot inherits the team's Cursor connector policy, which allows or blocks servers. Provisioning connectors to members, mandatory or default-on, isn't available.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
I've grown a YouTube channel to 400,000+ subscribers.
I wrote "Link Building Mastery".
My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Connect one app with the right account today, write its Ask first rule, and book a free strategy session if you want my team to plan the rest of your grok bot connectors.