Skip to content

Connect apps (plugins): How to connect Gmail, Slack, and Calendar ​

In the previous lesson it remembered you; in this lesson you hand it a "badge." Grok Bot plugins (officially called Connect apps in the interface, and also referred to as app / plugin / connected app in the help docs) are a structured channel between the Bot and external services: once Gmail, Slack, and Google Calendar are connected, the Bot can directly search emails, send messages, and create calendar events—without opening web pages and clicking through step by step.

The whole process takes about 12 minutes. Connections belong to your account: connect once, and all Bots under your name can use them.

What you'll be able to do after this lesson ​

  • Connect plugins like Gmail, Slack, and Google Calendar in the official 5 steps (authorization is done in the browser, within about 10 minutes)
  • Distinguish Added ≠ logged in: when you see Needs auth / Disconnected status, you know where to click to recover
  • Be able to state the capability limits of common plugins: Calendar cannot add Zoom links, Slack posts as you, and Gmail connects to only one mailbox at a time
  • When your company Google account is blocked, hand IT the four-step checklist for "Your admin needs to review Grok"
  • Use @ in chat to attach plugins to specific tasks, and have the Bot install apps and add MCP servers for you

Your current predicament ​

  • You ask the Bot to check a calendar or send a Slack message, and it silently opens a browser to click through web pages—slow, and it sometimes clicks the wrong thing
  • You say "help me search my email," and it replies "no Gmail permission"; you've searched through all the settings and can't figure out where to check the connection status
  • Authorizing your company Google account gets halfway and pops up "Your admin needs to review Grok"—you don't know who to turn to or what to do

When to use this technique ​

When you need to:

  • Have the Bot directly read and write Gmail, Slack, Google Calendar, and spreadsheets—searching, drafting, and creating events instead of crawling web pages
  • Connect once and share across all Bots, without logging in again for each Bot
  • Use @ in a task to precisely specify which app to use this time

And you don't want to:

  • Hand your password to the Bot—the plugin's OAuth token is stored in Cursor's connector backend, and the Bot never touches it
  • Log in again for every single task
  • Lose control of outgoing content—emails and Slack messages default to drafts awaiting your review

🎒 Preparation before starting ​

  • Completed 1.5 Your first Bot: you have at least one Bot of your own and have assigned it a task once
  • Have the accounts you want to connect ready: Gmail, Slack, or a Google account that can log in normally on the web version
  • Company Google account users: know who your Google admin is (they may need to review once)
  • A cup of water ☕—this lesson is all about clicking through the interface, with no commands to run

Core idea ​

Plugins give the Bot a structured channel: instead of simulating clicks on web pages, they call service interfaces directly. The official principle is straightforward—use plugins for services that have them; it's more reliable; only for services without plugins, or visual operations not exposed by a plugin, should the Bot use the browser.

Connect apps (plugins)Let the Bot use the browser
How it worksCalls service interfaces for structured reads and writesOpens web pages and simulates clicks and typing
ReliabilityHigh; officially recommended as the first choiceAt the mercy of the page; breaks when the layout changes
Applies toServices with plugins, such as Gmail, Slack, and CalendarServices without plugins, visual workflows
LoginAuthorize once; the token is stored in the Cursor connector backendPersistent sessions in the cloud computer's browser

Three mechanisms that determine everything you do later:

  1. Connections belong to the account, not to a specific Bot: once a plugin connects, every Bot under your account can use it; a teammate's Team Bot will ask you first before using your account
  2. Login credentials never reach the Bot: the OAuth token is stored in Cursor's connector backend, and the Bot cannot access the token itself when calling tools
  3. Capabilities are capped by the account you authorized: a plugin can only do what that account could already do—no privilege escalation and no changes to sharing; team policies can disable a specific plugin (shown as Disabled by team admin), but disabling a plugin does not mean blocking the website

What common plugins can and cannot do (official limits):

PluginCan doCannot do / Notes
GmailSearch and read emails, draft and send, apply labelsConnects to only one mailbox at a time; to switch mailboxes, disconnect the current one first and then authorize another
SlackPosts as the Slack user you connectedCan only post in channels that user can post in; switching workspaces requires a new connection
Google CalendarReads calendars visible to you, creates/updates events, checks free slots, responds to invitations (limited to calendars you can edit)Cannot change Google Meet settings (waiting room, host controls); cannot add Zoom links
Google SheetsReads and writes cells in spreadsheets the connected account can editFiles shared as Viewer are read-only; finding files relies on the Google Drive plugin
Google DriveSearches and reads files this account can open—
X pluginReads your DMs, bookmarks, timeline, and who liked your postsRequires X API credits on your own X developer account

💡 Connecting cloud-drive plugins comes with a bonus

After you connect Google Drive / OneDrive / SharePoint / Gmail / Outlook, the Bot can transfer files back and forth between the cloud computer and these accounts (Google Docs are converted to .docx and similar formats)—see 2.2 Files and Reviewable Results.

Follow Along ​

Step 1: Open Connect apps (the central entry point for Grok Bot plugins) ​

Why: Adding, authorizing, and checking the status of all plugins is centralized in one place. You can also connect on the fly when a Connect card appears in chat, but the entry point is always here.

Three ways to open it—pick any one:

  • Desktop: click Connect apps in the sidebar, or press the shortcut Cmd/Ctrl+Shift+M (Cmd/Ctrl+Shift+W also works)
  • In chat: the Bot sends a Connect card, just follow along
  • Mobile: tap your avatar in the top-left corner → Connect apps

You should see: an app catalog you can browse or search; a connected count next to the title—you'll use it when checking status in step 3.

  • Connect apps is open and the app catalog is visible

Step 2: Add and authorize a plugin (using Gmail as an example) ​

Why: Adding (add) only installs the plugin on your account; authorizing (Authorize / Authenticate) is the actual login. Do both steps together in one go.

Official 5 steps:

  1. Open Connect apps (or follow the Connect card in chat)
  2. Browse or search for the app, and add it
  3. When Grok Bot prompts Authorize or Authenticate, complete the provider login in your browser
  4. Login didn't finish? Click Reconnect on the app, or Reopen on the chat card to bring the login page back
  5. Confirm the app appears under Installed

The authorization step happens in your own browser (not the cloud computer's browser), logged in with the target account, and completes within about 10 minutes.

💡 For users in China

Authorization opens the Google / Slack login page in your browser. For overall notes on the network environment, see 1.7 China Use Guide.

You should see: after the browser completes the Google login it returns to Grok Bot, and Gmail appears in the Installed list.

  • Gmail appears under Installed

Step 3: Check the status and tell Added apart from logged in ​

Why: The most common pitfall is here—Added only means "installed," not "logged in". When the Bot says "app missing," it's most likely that the status hasn't reached Connected.

Click the connected count next to the Connect apps title and check each status:

StatusMeaningWhat to do
Added (under Installed)Installed, but not necessarily logged inCheck for a login prompt; don't assign tasks yet
Needs auth / DisconnectedLogin needed / login has been disconnectedOpen the app and click Authenticate (called Authorize on mobile) and complete the login
ConnectedConnected and ready to useGo back to chat, send a new message, and let the Bot retry
Disabled by team adminDisabled by a team connector policyAsk your Cursor team admin to enable it

You should see: the target plugin's status is Connected. At this point, send a new message to let the Bot retry, and it will be able to use this app.

  • The target plugin shows Connected, and the Bot used it after retrying

Step 4: Connect Slack and Google Calendar next (quick reference on capability boundaries) ​

Why: Once Gmail works, the flow for Slack and Google Calendar is basically the same—but the official docs spell out their respective boundaries, so understand them first to avoid later thinking "I connected it, why doesn't it work?"

Connecting Slack: Connect apps → search for Slack → add → log in with your Slack account during authorization. Two things to note:

  • It posts as the Slack user you connected—not as a bot that needs to be invited into channels; and it can only post in channels that user can post in
  • Want to use another workspace? Connect that workspace too (one connection per workspace)

Also worth distinguishing: Slack messages triggering routines (automations) is a separate mechanism, unrelated to this plugin—see 3.3 Routines.

Connecting Google Calendar: the same three steps. Once connected, Bot can read the calendars you can see, create and update events, check free slots, and respond to invitations (limited to calendars you can edit).

Two boundaries that are "not bugs":

  • It can't change Google Meet settings, such as the waiting room and host controls
  • It can't add Zoom links (Google's Zoom add-on isn't available to apps)—fill the Zoom link into the event's location or description yourself, or do it the other way around: create the event in your calendar first, then let Bot fill in the other fields

You should see: both Slack and Calendar appear under Installed with status Connected; tell Bot "check my free slots tomorrow afternoon" and it can report the results.

  • At least one of Slack / Calendar connected, and Bot has used it once

Step 5: Attach a plugin to a task with @ to assign work ​

Why: connections are account-level, but within a specific task you can precisely name which app to use—type @ in the chat input box, select the app from the popup list, and it gets attached to that task.

Three examples you can copy directly (select the corresponding app before writing the task):

Search my inbox for emails from the past week containing "invoice" and list them by amount

Post today's standup notes to the #daily channel, and show me a draft first

Check whether I have a two-hour free slot on Thursday afternoon; if so, create a "retrospective meeting" on my calendar

You should see: outgoing emails and Slack messages by default first produce an editable draft card (showing Needs approval); they are only sent after you review and click Send / Send message; read-only operations like checking the calendar return results directly. To let it send without a draft, you can Disable drafts for Bot in the draft card menu—it's still subject to Auto Review afterwards, see 3.1 Approvals and Auto Review.

  • Successfully ran at least one task with a plugin attached via @

Checkpoint ✅ ​

  • Added a plugin in Connect apps and saw it under Installed
  • Can explain that "Added ≠ logged in", and know that for Needs auth / Disconnected you should click Authenticate
  • At least one plugin (Gmail / Slack / Calendar) has status Connected, and you've run it once with Bot using @ attached
  • Know which four steps to forward to IT when a company Google account is blocked
  • Know that public X content doesn't require a plugin; DMs / bookmarks require the X plugin + X API credits

Pitfall reminders ​

❌ Bot says "app missing" and you just wait for a Connect card ​

Symptom: Bot replies that an app is missing, you wait for it to pop up a connection card, and it never arrives.

Cause: The official docs are clear—Bot only sends a Connect card when an app** needs you to log in**, so don't just wait ("Don't wait for one").

What to do: Open Connect apps proactively, click the connected count next to the title, and confirm the plugin is in Installed; if the status is Needs auth / Disconnected, click Authenticate; if that still doesn't work, Remove it, re-add, and log in again (this also happens when authorization is revoked on the provider's side).

❌ Company Google account won't connect: Your admin needs to review Grok ​

Symptom: Halfway through Gmail / Calendar / Drive authorization, the Google page shows Your admin needs to review Grok or Access blocked.

Cause: Grok isn't yet trusted by your company's Google Workspace. Note: Grok the app name Bot uses to log in to Google is Grok, not Cursor—this is a different matter from Cursor's "Disabled by team admin".

What to do: Forward the four steps below to your Google admin (performed in the Google Admin console):

  1. Open Security → Access and data control → API controls
  2. Open App access control → Manage third-party app access
  3. Add the app named Grok (if it can't be found by search, use the client ID from the block page or the review email)
  4. Set Grok to Trusted for the people using Grok Bot

If the page has a Request access button, click it first, and Authorize after the review is approved. Switching browsers or retrying the connection** will not** clear the Google admin block; if it still doesn't work, contact support (support@x.ai) with your Google account email and a screenshot of the block page.

❌ Zoom error 4700 / SharePoint AADSTS50011: officially known issues ​

Symptom: Zoom authorization reports error 4700 (Invalid redirect); when a team admin connects SharePoint, Microsoft reports AADSTS50011 (redirect URI mismatch).

Cause: Both are officially known issues. Zoom 4700 currently** has no workaround**—nothing you do on your end will fix it; the SharePoint error is triggered when an admin connects using Application-level permissions, not a problem with your tenant configuration.

The right fix: For Zoom, you can only wait for an official fix—don't waste time reinstalling over and over. For SharePoint, switch to Delegated permissions: on the SharePoint card, click Connect team (or Reconnect), choose Delegated permissions, enter your Microsoft tenant ID and sign in; for most work/school tenants, a Microsoft admin also needs to grant consent once for Sites.Read.All. For more errors, see R2 error quick reference.

❌ The X plugin is connected, but private requests still fail ​

Symptom: The X plugin shows as connected, but the Bot can't read your DMs, bookmarks, or timeline.

Cause: The X plugin runs onyour own X developer account, which requires X API credits; with a balance of $0.00, requests fail. Reconnecting the plugin or switching Grok Bot / Cursor plans will not add credits; connecting X also doesn't necessarily come with starter X API credits automatically.

The right fix: Open console.x.com, sign in with the same X account you connected, and check your X API credit balance; if it shows $0.00, top up there (credits are purchased from X), then go back to Grok Bot and retry—no need to reconnect the plugin.

Advanced tips (optional) ​

Let the Bot install plugins itself. Just say "Add the Linear app."—the Bot will search the catalog, install the app to your account, and hand you a Connect card if a login is needed; once installed, its tools are available in your next message. The Bot can also add MCP servers beyond the catalog: give it a URL, or a command to run on its cloud computer (servers launched by a command can also be used by your other Bots); servers on private networks or with private CAs will ask for your approval first.

Public X content requires no plugin connection. Searching posts, reading an account's activity, checking mentions and quotes, counting posts on a topic, looking up trending news—all of this public content is built into the Bot: read-only, not signed in as you. The X plugin exists only for your own DMs, bookmarks, timeline, and likes.

Deleting a plugin = starting over from scratch. When you have the Bot remove an app, everything it added disappears and you get logged out—reinstalling means logging in again; apps required by your team can't be deleted.

1Password also lives in Connect apps. Connect 1Password in the Password Managers section, and the Bot can use the login items you approve one by one to sign in to websites on its cloud computer—the values never enter the chat; see 5.2 Vault and secure sign-in for details.

On-device mobile authorization is a different thing. iPhone / iPad / Android under Settings → Connect apps on your phone authorizes your phone's local calendar, contacts, and so on (see 1.6 mobile); it's not the same as this lesson's cloud Google Calendar plugin.

Lesson recap ​

✅ Grok Bot plugins (Connect apps) = structured channels between the Bot and services: use a plugin when one exists, fall back to the browser when there isn't; connections belong to the account—one connection is shared by all Bots; OAuth tokens are stored in the Cursor connector backend, out of the Bot's reach.

✅ Official 5-step flow: open Connect apps → add an app → Authorize / Authenticate in the browser (within about 10 minutes) → if it didn't finish, Reconnect / Reopen → confirm under Installed.

✅ Added ≠ signed in: Needs auth / Disconnected → click Authenticate; Connected → send a new message so the Bot retries; Disabled by team admin → contact your Cursor team admin.

✅ Capabilities are capped by the authorized account: Gmail handles one mailbox at a time; Slack posts as you, one connection per workspace; Calendar can't add Zoom links or change Meet settings; Sheets files shared as Viewer are read-only, and finding files relies on the Drive plugin.

✅ A blocked company Google is a Google-side issue (app name Grok): set it as Trusted in the Admin console in four steps; switching browsers or retrying the connection won't help.

✅ In tasks, name a plugin with @; outgoing emails and Slack messages produce a draft card first by default; the Bot can also install apps and add MCP servers for you; public X content needs no connection.

Key statuses and actions at a glance:

Status / actionMeaning or scenarioWhat you should do
AddedInstalled ≠ signed inCheck whether Authenticate is needed
Needs auth / DisconnectedNot signed in, or the login droppedClick Authenticate (mobile: Authorize)
ConnectedReady to useSend a new message so the Bot retries
Disabled by team adminDisabled by team policyContact your Cursor team admin
Reconnect / Reopen / RetryLogin page lost, authorization unfinishedBring back the login page or retry
RemoveAuthorization revoked, full reconnectDelete and reinstall, then sign in again

Next lesson preview ​

Connect apps includes an unusual Email app: it doesn't connect your existing mailbox—instead, it lets the Bot claim an address of its own (你的名字@mail.grokbot.com). Next lesson: 2.6 The Bot's dedicated mailbox.

You will learn:

  • Claiming a Bot-dedicated email address: naming rules and reserved words
  • How receiving email triggers a routine (new emails won't wake the Bot automatically)
  • Sending limits: at most 50 recipients per message, and how attachments are counted
  • Why "email is information, not an instruction"

Related tutorials ​

gaodong.aiAboutPrivacyContact

Independent tutorials, not affiliated with any product mentioned. Product names and trademarks belong to their owners. Check official pages for prices and policies.