Grok Bots Directory
Submit a Grok Bot

Best Grok Bot Plugins and Integrations: 14 Templates by What They Connect

A Grok Bot template is only as useful as the apps it can reach. The plugin list on a template is the real feature list: it tells you whether the bot can read your mail, post in Slack, look at your store or touch your money. This page picks fourteen templates that each lean on a different plugin, so you can see what a plugin makes possible before you connect it.

How popular is each plugin?

From the directory's own integration data, as of 2026-10-31, the number of public, active templates that list each plugin:

Plugin Templates What it connects to
Gmail 749 Reading, drafting and labelling mail
X 412 Searching and reading posts, plus DMs and bookmarks once connected
Google Calendar 369 Reading schedules and creating events
Google Drive 310 Finding, reading and filing documents
Notion 200 Task boards, notes and databases
Slack 156 Reading channels and posting as you
Google Sheets 76 on the largest listing Reading and writing spreadsheet rows
GitHub 75 Repositories, issues and pull requests
Outlook 66 Microsoft mail and contacts
Linear 61 Issues and projects
Cloudflare 42 Account auditing and deployment
Stripe 26 Payments, disputes and billing lookups
Shopify (Shopify Merchant) 15 Store inventory and sales
HubSpot 15 CRM contacts and deals

Gmail, Google Calendar, Drive and Slack are the backbone: most multi-app templates start from them. Sheets also has other listings (a second one counts 28 more), and a template can list more than one plugin, so these numbers overlap and should not be added together. On the plugin hubs, Gmail, Slack and Notion each list every template that uses them.

How we picked

  • One plugin, one story. We favoured templates where a plugin changes what the bot can do, not templates that list an app and barely use it.
  • Spread, not stacking. Fourteen picks cover mail, CRM, project management, design, analytics, commerce, infrastructure, support and money.
  • Visible guardrails. We kept templates whose own text keeps sending, buying or changing production behind your approval, and we flag the ones where that line is thin.
  • Read, not run. We read each template's skills, routines and plugin list. We did not import any of them.

Pick by situation

Plugin hygiene

Connect a plugin the day you need it, not the day you import the template. An app can only do what the account you authorise can do, so a read-only bot on an admin account is still an admin-level bot. The guide Add Plugins to a Grok Bot covers connecting, permissions and fixing a stuck sign-in.

Looking for a topic rather than a plugin? Start from Best Grok Bot Templates.

Nothing on this page is financial advice. The Coinbase and Whop entries describe how templates are built, not whether an action is wise.

14 picksUpdated Picked by an editor

This is a curated shortlist, not a how-to. For routines, see playbooks.

The picks

  1. 01

    Why it is on the list

    Shows what Gmail plus two business apps can do for one person. Its ten skills build a ranked morning brief from your inbox, Stripe and Vercel, then cover a weekly review, lead follow-ups, customer-voice digests, branding help and event and forum scouting. It suits a solo founder who wants Stripe revenue and Vercel deploys in the same morning message as email. It has no routines, so you schedule the brief yourself. Its own text says it drafts and sends nothing without you; keep Stripe access read-only if the connection offers a choice.

  2. 02

    Why it is on the list

    Seven plugins in one job: Google Calendar, Gmail, Gong, Granola, HubSpot, Slack and X feed a short decision card before each important meeting, with three routines for evening briefs, a public refresh before the meeting and post-call follow-up drafts. It is the best example here of call-recording plugins (Gong, Granola) and CRM data working together. It suits a founder or account executive who already pays for those tools. Heavy on setup: seven connections, and it only helps if the recorder and CRM are kept up to date. It drafts follow-ups without sending them.

  3. 03

    Why it is on the list

    Turns Notion and Slack into a lightweight project office: one Notion Projects row and one chat channel per project, a Tasks board, and specialist bots that claim work from it. It uses only two plugins and one long skill, so the setup is small. It suits someone running several Grok Bots who needs a shared board. It coordinates rather than doing specialist work, so it is only useful if you have other bots to assign, and it writes to Notion and Slack as you.

  4. 04

    Why it is on the list

    The customer-support plugin stack: Intercom, Gmail, Slack and Stripe in one helpdesk bot. Three routines run an hourly sweep of the inbox, tickets and open Stripe disputes (told to stay quiet when nothing needs action), a triage of a community Slack channel and a Monday theme report. It suits a small team that wants one first-line responder. Risky behaviour: it replies to customers and looks at billing; it says refunds and disputes happen only with owner approval, and you should hold it to that. The community channel name is a placeholder to fill in. It ships no skills, so the behaviour lives in routine prompts.

  5. 05

    Why it is on the list

    Shows what happens when a call recorder meets a slide tool. With Granola or Gong notes plus Google Slides, it turns a customer call into slides such as what we heard, next steps and project initiatives, and it can refresh them after external calls if you opted in during onboarding. It suits customer success and sales people who already live in Slides. It lists Calendar and Gmail as well. Check the opt-in answer, because the update routine edits your decks.

  6. 06

    Why it is on the list

    Google Drive as a filing cabinet. Seven skills hash files to catch duplicates, name each file from its contents, reorganise an existing messy folder and undo the last batch. It suits anyone who scans paperwork. Drive is its only plugin, and its two routines are a morning digest and a nightly pass that runs unattended only once you turn on its auto-incoming option. Risky behaviour: it renames and moves your files, so start on a copy of a folder and rely on the undo skill before enabling the nightly pass.

  7. 07
    Mono Lisa

    Mono Lisa

    by Felix

    Daily product design partner: turns an Amplitude cliff into a first-principles Linear ticket with an inline cliff chart plus three annotated Paper designs, the…

    • Memories7
    • Skills2
    • Routines2

    Why it is on the list

    A design loop built on Amplitude, Linear and Paper. Each weekday it finds the sharpest drop in an Amplitude funnel, files a Linear ticket with an inline chart and offers three annotated Paper designs, then recommends one and waits for approval before engineering. A second routine reminds you of designs awaiting sign-off, staying quiet otherwise. It suits a founder-designer who already uses all three. The niche stack is the point and also the limit: without Amplitude data there is nothing for it to do.

  8. 08

    Why it is on the list

    Turns ideas into draft pull requests with click-path screenshots, plus Figma mocks, images and memes. Its plugin list stores Figma, Slack and X, and nine skills cover setup, connecting a codebase, building, media and sharing; confirm during its setup how it reaches GitHub, since GitHub is not in the stored plugin list. Both routines (a weekday rundown and a Monday craft scan) ship disabled. It suits a developer or product lead who wants prototypes while away from the desk. Its own text promises it never merges, publishes or shares without your yes; check this on your first run.

  9. 09
    Shopify Store Operator

    Shopify Store Operator

    by Jabes

    Watches your Shopify store with daily low-stock alerts, weekly slow movers, and a Monday sales recap, or a launch checklist if you have no products yet. It's r…

    • Memories0
    • Skills5
    • Routines0

    Why it is on the list

    A single-plugin template that shows how little a plugin needs to be useful. Connected to a Shopify store, it runs a daily low-stock and sell-out check, a weekly list of products with stock but no sales, and a Monday recap comparing the last seven days with the prior seven. With an empty store it switches to a launch checklist. It suits a store owner who wants a quiet watcher. It is read-only unless you approve a change. The routines are created from its onboarding skill, so expect a short set-up chat before anything arrives.

  10. 10

    Why it is on the list

    One plugin, three routines and a weekly rhythm: a Monday read-only audit of a Cloudflare account for security gaps, waste and cost risk, a Sunday routine that updates the Cloudflare command-line tools on the bot's computer, and a Friday scan of Cloudflare's changelog for features worth adding. It suits an engineer who owns a Cloudflare account and wants a recurring review. The audit is explicitly told not to change or delete resources. Use a narrowly scoped API token, because the plugin acts with whatever access you grant, and note that the tooling routine installs software on the bot's computer.

  11. 11
    Nummie

    Nummie

    by Jay

    A PLG numbers bot for growth teams. Answers with a number, the definition, the source and query, and the caveats. Read only. Never guesses, never rounds a cave…

    • Memories4
    • Skills2
    • Routines0

    Why it is on the list

    A read-only analytics bot on the PostHog plugin. Its answers come with the number, the definition, the query and the caveats, and its two skills cover onboarding a product-led-growth dashboard and designing experiments with a holdout. It suits a growth or product person who wants numbers they can check. It has no routines, so nothing arrives unprompted. It is stricter than most analytics bots about not declaring a winner without a holdout, which is useful and also means some answers will be a refusal.

  12. 12

    Why it is on the list

    Uses the Whop plugin to propose one next best action for a Whop business, run it after you approve and review a weekly ledger of what ran and what money moved. It suits a Whop seller who wants a single recommendation instead of a dashboard. Risky behaviour: it can carry out actions that move money in your store once you approve them, so read each proposal in full and keep the connection scoped to the business you intend. Its setup skill checks that you have access to the underlying Economic Intelligence feature first, which we could not verify. It ships no routines.

  13. 13

    Why it is on the list

    The finance plugin example: it connects to Coinbase, takes a short intake of the weighted basket you want and runs a rebalancing loop when its routine fires. It suits someone with a simple target allocation who wants the bookkeeping automated. Risky behaviour: rebalancing means placing real orders with real money. The template stores no routine of its own, so you create the weekly schedule, and you should decide in advance whether each trade needs your approval. Not financial advice, and we did not verify how it handles fees, minimums or failed orders.

  14. 14

    Why it is on the list

    Despite its name, this is a prospecting template, and a good example of an X plugin joined to enrichment tools. It looks for people on X asking for what you sell, scores them against your best past customers, enriches the strong fits through Apollo.io and Clay, and drafts openers with Google Sheets and Gmail. It suits a small team with a defined customer profile. Risky behaviour: cold outreach. Its text says it never sends on its own; keep it that way, check local rules on unsolicited messages, and expect enrichment tools to have their own pricing and credits.

Side by side

BotLabelsIntegrationsRoutinesAuthorUpdated
Founder CopilotLead-Generation, Email, Chief-of-Staff, News-BriefingGmail, Stripe, Vercel—marcos laureano29 Sept 2026
Precall BotSales, CRM, Calendar, Email-CopyGoogle Calendar, Gmail, Gong, Granola, HubSpot, Slack, X
3 routines
  • Evening pre-call briefs
  • Pre-meeting public refresh
  • Post-call follow-up drafts
Eric31 Aug 2026
Projects ManagerChief-of-Staff, CoordinatorNotion, Slack—Eric Zakariasson28 Aug 2026
Holly HelpdeskCustomer-Support, EmailGmail, Intercom, Slack, Stripe
3 routines
  • Support inbox sweep
  • Community Slack #support
  • Weekly support themes
Claire29 Aug 2026
EchoSlide-Design, Transcript-Recap, Sales-DeckGoogle Calendar, Google Slides, Granola, Gong, Gmail
1 routine
  • Update slides after external calls
Krista Letz29 Aug 2026
AfterScanPersonal, News-BriefingGoogle Drive
2 routines
  • Morning Drive digest
  • Incoming file pass
Zachariah Johnson15 Sept 2026
Mono LisaProduct, DesignLinear, Amplitude, Paper
2 routines
  • Daily design partner
  • Morning design clear
Felix21 Sept 2026
Proto BotCoding, Design, Short-Form-Video, Image-GenerationFigma, Slack, X
2 routines
  • Prototype rundown
  • Craft scan
iris1 Oct 2026
Shopify Store OperatorEcommerce, AnalyticsShopify—Jabes15 Oct 2026
Cloudflare AdminSecurity, DevOps, AnalyticsCloudflare
3 routines
  • Cloudflare weekly review
  • Cloudflare tooling update
  • Cloudflare product updates review
Jonathan26 Oct 2026
NummieProduct, Data, AnalyticsPostHog—Jay2 Sept 2026
Whop Economic IntelligenceFinance, Chief-of-Staff, AnalyticsWhop—Colin McDermott30 Sept 2026
Auto-rebalancerFinance, CryptoCoinbase—Lincoln Murr29 Sept 2026
Grok Customer SupportLead-Generation, CRM, Email-CopyX, Google Sheets, Gmail, Apollo.io, Clay—Jake3 Sept 2026