agentos.guide › blog
Grok Bot connectors become far easier to manage once your Agent OS treats them as a living register: which app, which account, which status, which rule.
The Bot does the connecting; your Agent OS keeps track of it.
Since v0.78.1 on 27 October 2026, the Bot offers a connector itself on sign-in pages such as Google Ads, Meta Ads, Gusto and YouTube, so new connections now turn up mid-task.
Below is a quick start, five copy-paste prompts and a weekly workflow to keep every connection healthy.
Want my team to map this onto your own setup? Book a free SEO strategy session and we'll go through it together.
That is the flow in the computer and apps docs.
Type @ in a chat to attach the app to a task.
For installing from the catalogue and the skills limit, see the separate Grok Bot plugins guide.
Connected apps are account-wide, so every Bot you run can use every one of them.
OAuth tokens stay on Cursor's connector backend, and the Bot never receives them.
So the thing to track isn't the token; it's which account each app is signed in with.
A register answers that in one glance, and it's what the prompts below build.
Keep it as a simple table your Agent OS can read: app, account, status, rules, routines that depend on it.
Members of the AI Profit Boardroom get a ready-made version inside the installable Agent OS.
Added means installed, not signed in, so check the label first.
| Status | Your move |
|---|---|
| Needs auth / Disconnected | Choose Authenticate (Authorize on the phone) and finish the login |
| Disabled by team admin | Ask your Cursor team admin to enable it |
| Connected | Send a fresh message and ask the Bot to try again |
The troubleshooting page asks you to finish authorisation within about 10 minutes, and a card asks "Still signing in?" at that point.
Releases from v0.75.2 onwards keep a connector login open for up to an hour.
Calls to a connected app wait up to two minutes for a reply, and a connector that goes quiet times out after three.
If a company Google account shows Your admin needs to review Grok, your IT admin has to trust the app named Grok in the Google Admin console first.
Naming a service in chat makes the Bot show its connect card in the first reply, per the Grok Bot changelog.
Connect Google Calendar for me. Show me the connect card,
wait while I sign in, then confirm it shows as Connected
in Connect apps (not just Added). Tell me which Google
account it is using, then add a row to my connector
register: app, account, date connected, status.
If the sign-in stalls, choose Reopen on the card to bring the login page back.
Routines that hit a signed-out connector show a Reconnect card at most once a day, so a sweep catches the rest.
Check every connector on my account. For each one, tell me
whether it is Connected, Needs auth, Disconnected or
Disabled by team admin. For anything not Connected, give
me the exact button to press. If reconnecting will not
fix a missing permission, say so plainly instead of
sending me through sign-in again.
Since v0.78.1 the Bot already says when reconnecting won't help, and names connectors instead of internal IDs.
🔥 Get the Agent OS with the connector register built in
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 keeping their Bots connected to the right accounts.
Auto Review takes plain-English rules: Allow automatically or Ask first, and Ask first wins when both match.
The approvals, security and privacy page allows up to 20 of each, at 1,000 characters per rule.
Look at the connectors in my register. For each one,
draft one narrow Ask first rule for any action that sends,
posts, pays, deletes or changes a budget, and one narrow
Allow automatically rule for a safe read. Keep each rule
to one sentence. Don't save anything; show me the list
so I can add the ones I approve under Custom Rules.
Add the rules yourself in Settings, so you see every one before it applies.
Start with the apps that can send, post or spend money, then work down to the read-only ones.
v0.78.1 makes the Bot offer a connector on eight sign-in pages: Google Ads, Meta Ads, TikTok for Business, YouTube, Gusto, Coinbase, Cloudflare and Railway.
Whenever you reach a sign-in page for a service that has
a connector, stop and offer me the connector instead of
using the browser login. After I connect it, log it in my
register and carry on with the task where you left off.
Ask the Bot to remember this as a standing instruction so it holds across chats.
Connector sign-ins can finish up to an hour after you start them, so a slow SSO login won't sink the task.
The docs give a clean order: pause routines, uninstall the connector, revoke it in the source service.
The Henderson project has finished. List every routine
and connector it used. Pause those routines, then tell me
which connectors no other routine needs. I'll confirm
before you remove any. After removal, remind me to revoke
access inside each service as well.
The Bot won't remove or rename a connector unless you spell out that exact change, so it waits for you.
Removing an app signs you out and takes everything it added with it.
That rhythm matches the docs' advice to review installed connectors and active routines regularly.
Keep the register next to your routines list, because the two drift together.
A routine that quietly loses its connector stops calling it and asks you to reconnect, so a stale register row usually means a routine is waiting on you.
When you add a new connector, add its Ask first rule the same day, before the first routine touches it.
And when a sign-in page offer appears mid-task, accept it, then update the register before you forget which account you used.
Gmail holds one mailbox at a time, so note which inbox is live; switching means disconnecting and authorising the other one.
📞 Want this connector workflow mapped for your business?
Book a free SEO strategy session and my team will walk through your apps, accounts and rules with you.
Each connection serves only its owner: per the shared Bots docs, the Bot uses the account of whoever it is replying to.
A teammate's shared Bot asks before it uses your accounts: Allow once, Always allow or Skip.
If a Team Bot routine wants one of your apps, it pings you by name in that routine's Slack thread.
To reset every answer, open Settings, General, Shared Bots and choose Clear next to Clear connector preferences.
Grok Bot inherits your team's Cursor connector policy; there's no separate Grok Bot list.
A blocked app shows Disabled by team admin, and connectors can't be pushed to members, according to the teams and enterprises docs.
Blocking an app doesn't block that site in the browser, which needs Enterprise Network Controls.
On an allowlist, switch on Apply to MCP servers after adding each connector's hosts from the security page.
Name the service in chat. Since v0.75.2 the Bot shows that connector's connect card in its first reply, and you finish the sign-in in your browser.
The routine hit a connector that signed you out. The chat shows that card at most once a day, so press Reconnect when you see it.
Have the Bot draft them, then add the ones you approve under Custom Rules in Auto Review yourself. Ask first wins when rules conflict.
Everything the app added goes with it and you are signed out, so reinstalling means signing in again. Apps your team requires can't be removed.
Paste Prompt 1 into a fresh chat today, start the register, and book a free strategy session if you want help running your grok bot connectors.
About Julian
I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.
→ Grok Bot Plugins In Your Agent OS: Quick Start, 5 Copy-Paste Prompts And A Weekly Workflow
→ Grok Bot Gmail: Run Your Inbox Safely In Your Agent OS
→ Grok Bot Browser: Safe Web Tasks In Your Agent OS
→ Grok Bot Teams: Plan, Audit And Roll Out A Shared Bot With 5 Prompts In Your Agent OS
The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.
Join the AI Profit Boardroom →📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉