How To Use Claude, Grok Bot, Notion, GitHub And Cursor Together (Plus How I'm Rebuilding My Bot Team)

13 min read

Short answer: to use Claude, Grok Bot, Notion, GitHub and Cursor together, give each tool exactly one job and make all of them read from and write to one shared place, a Notion handbook. Claude does the hands-on work in your apps, Grok Bot keeps the social and real-time jobs, GitHub holds every version of your website code, and Cursor is where you edit that code by hand. The tools never need to talk to each other directly. They talk through the handbook.

I built a team of 20 Grok Bots to run my repair shop. It worked, and it also sprawled: six research bots, two test bots, a manager bot auditing the others, and the same rules copied into twenty sets of instructions. Last week my two website themes drifted apart because three tools edited them separately. This guide is the setup I'm moving to, and the second half is my real plan for rebuilding the team.

What Should Each AI Tool Do?

Tool Its one job Why it fits
Notion The handbook: rules, procedures, task board, change log Every tool can read it; you change a rule once
Claude The hands: store data, website changes, long writing, research, checking work Works inside your apps through connectors, asks before risky actions (Part 4)
Grok Bot The voice: social posts, X and trend watching, routines already running My bots already do these well; no reason to rebuild them
GitHub The memory for code: every version of the website theme Any change can be seen, compared and undone
Cursor The workbench: hands-on code editing with AI beside you For the times you want to see and steer the code yourself
The rule that makes it work: never let two tools own the same job. When Grok and Claude both wrote product descriptions, I got two voices and twice the cleanup. Pick one owner per job and write it in the handbook.

How Do You Set Up A Notion Handbook For AI Bots?

Make one Notion page called Handbook with five sub-pages. Keep each one short enough that a bot can read it in one go.

  1. Rules: the things every tool must follow. Mine: warranty wording, words we never use in listings, walk-ins by call or text first, no supplier names or costs in customer copy, ask before anything goes live.
  2. Who Owns What: the table above, filled in with your tools and bots.
  3. Procedures: step-by-step how-tos, like "how we change the website" (my A/B/C theme process) or "how we write a device page."
  4. Task Board: a simple board with columns: Ideas, Needs Steve, Doing, Done.
  5. Change Log: one line per change: date, tool, what changed, where the backup is.

Then connect it. In Claude, add Notion under Settings → Connectors and tell your Projects "read the Handbook Rules page before starting." For Grok bots, link or paste the Rules page into their instructions and point them to the Task Board for handoffs. Turn the Procedures into Claude Skills over time (Part 3 shows how), so Claude loads each one only when it's needed.

Why Should You Put Your Shopify Theme On GitHub?

Because a theme edited from three places drifts. Shopify can connect a theme to a GitHub repository: in Shopify admin go to Online Store → Themes → Add theme → Connect from GitHub. After that, every change, whether from the theme editor, Claude, Cursor or a designer, becomes a saved version you can compare and undo.

  • Branches replace copies. My "Theme A, Theme B, backup C" routine becomes a main branch for the live site, a working branch for changes, and saved versions for backups.
  • Designers stop overwriting each other. If my designer works on an older copy, GitHub shows exactly what would be lost before it goes live.
  • Claude Code and Cursor both work on the same repo, so nothing gets copied by hand between tools.

Where Does Cursor Fit If You Already Have Claude?

Cursor is a code editor with AI built in, and it can use Claude models. Use it when you want to be hands-on: open the theme repo, look at the actual file, ask the AI to change one section and watch it happen. For everything else (bulk store changes, writing, research) stay in Claude. If you're not a coder, you can skip Cursor entirely; Claude and Claude Code cover the same ground with less to learn.

How Do The Tools Hand Work To Each Other?

Through the Task Board, never through you copying text between chats.

  1. A Grok bot spots something (a competitor's new price, a bad review, a trending question).
  2. It adds a card to Needs Steve or Ideas with the facts and a link.
  3. You approve it by moving the card to Doing and adding "Claude."
  4. Claude reads the card, does the work in the store or site, backs up first, and writes one line in the Change Log.
  5. The card moves to Done, and the Grok bot that raised it can post about it if it's customer news.

A Handoff, Start To Finish

G
Scout (Grok Bot)Card added to Needs Steve: three customers this week asked if we fix Pixel 9 back glass. We don't list it. Link to the messages attached.
S
SteveMoved to Doing. Claude, add it as a quote-only repair.
C
ClaudeAdded Pixel 9 back glass as quote-only on the Google page, following the Rules page. Change Log updated. Card moved to Done.

How Am I Rebuilding My 20-Bot Grok Team?

Here's the honest picture. My team grew one bot at a time, every time I hit a new problem. By November it was 20 bots, and most of my usage went to bots checking on other bots. I even had to pause routines for a week to stay inside my usage. The rebuild has three moves: merge overlapping bots, move hands-on work to Claude, and replace bot-checking-bot with one handbook.

Before and after

Old bots New setup Runs on
Cortana (Co-CEO and assistant) Cortana, coordinator: daily brief, Task Board triage Grok Bot
Social, Writer, Scout & Analyst Social, one bot for ideas, drafts and posting plans Grok Bot
Local Reputation Reputation, review checks and reply drafts Grok Bot
Front Desk (RepairDesk Clerk) Front Desk, bookings to tickets, customer replies Grok Bot for now; moves to Claude if a RepairDesk connection is available
The Designer, The Localizer, AI Search Visibility Website Project: theme, listings, SEO, page copy Claude, with Shopify and GitHub
R&D, Research & Site Reader, Supplier Reader, Projects Manager Research Project: parts facts, supplier pages, device specs Claude, with Research and Claude in Chrome
R&D Photo Sourcer, R&D Render Visuals, one bot for photos and renders Grok Bot
The Accountant Books Project: money checks, tax dates Claude, read-only on financial accounts
Bot Manager Retired. Replaced by the Handbook plus a weekly Claude check of the Change Log Claude scheduled task
Test, Test Owner Kept off by default; switched on only to test bot kits before release Grok Bot

That takes 20 bots down to 5 Grok bots plus 3 Claude Projects, with the same jobs covered. Fewer bots means fewer copies of the rules, fewer routines checking each other, and much less usage spent on overhead.

Why some jobs move to Claude and some stay on Grok

  • Move to Claude: jobs that change things in my store, my website or my files, and jobs that need long careful reading. Claude works directly in those apps and checks its own changes.
  • Stay on Grok: jobs built around X, trends and social voice, and routines that already run well. If it isn't broken, I don't move it.

What's The 4-Week Rollout Plan?

Week Do this Done when
1 Build the Notion Handbook. Merge every bot's copied rules into one Rules page. Connect Claude to Notion. Every rule lives in one place
2 Connect the website theme to GitHub. Set up the Website and Research Projects in Claude. Pause the bots they replace (don't delete yet). Claude handles a week of website and research work
3 Merge Social, Writer and Scout; merge Photo Sourcer and Render. Move every handoff to the Task Board. No more copying text between chats
4 Set up the Books Project and the weekly Change Log check. Compare usage and results with week 0. Archive the paused bots. Same work done, lower usage, nothing lost

Safety net: paused bots stay paused, not deleted, until week 4. If a merged bot drops a job, I switch the old one back on.

Your Turn

  • ☐ List every AI tool and bot you use and the one job each does. Circle the overlaps.
  • ☐ Make a Notion page called Handbook with Rules, Who Owns What and a Task Board.
  • ☐ Move your rules out of individual bot instructions into the Rules page.
  • ☐ If you have a Shopify theme, connect it to GitHub before your next design change.

Frequently Asked Questions

Can Claude and Grok Bot work together?

Yes, through a shared place like a Notion page or a Google Doc. One writes a task or finding there, the other reads it. They don't need to connect to each other directly.

Do I need Cursor if I have Claude?

No. Cursor is for hands-on code editing. If you don't edit code yourself, Claude and Claude Code cover the same work.

How do I connect my Shopify theme to GitHub?

In Shopify admin, go to Online Store, Themes, Add theme, Connect from GitHub, and pick or create a repository.

How many AI bots does a small business need?

Fewer than you think. One per real job, with no overlaps. My shop is going from 20 bots to 5 bots plus 3 Claude Projects for the same work.

Why use Notion as the hub?

Because every tool can read it and you only change a rule once. Google Docs or Drive work too; what matters is one shared place.

More Claude Guides

  1. How To Set Up Claude As Your AI Assistant
  2. Claude Plans, Models And Usage Limits Explained
  3. How Claude Remembers: Projects, Memory, Skills And Instructions
  4. Let Claude Work In Your Apps
  5. How To Prompt Claude Like A Pro
  6. Claude, Grok Bot, Notion, GitHub And Cursor Together (you're here)

Running Grok Bots? See How My Repair Shop Runs On A Team Of Grok Bots.

Unofficial guide written by a customer of these tools. Not affiliated with Anthropic, xAI, Notion, GitHub, Cursor or Shopify.

Back to blog