This walkthrough uses a fictional business and test accounts only. It sets up no live messages or routines.
This walkthrough prepares one Sunday brief from calendar events you enter. It does not post, connect X, or invent a special that is not on the calendar.
At a glance
What you’ll have at the end
A fictional Rolling Crumb Social Scheduler Bot, set up on a test account, that can:
- Read next week’s test calendar events.
- Draft one short post per open day, using only that day’s location, hours and special.
- Note closed days in the brief, without inventing a post for them.
Staff still review every draft before anyone posts. This walkthrough has not been run end to end. A Sunday afternoon routine is optional later; this walkthrough creates none.
What you need
- A Grok Bot account. Access that includes Grok Bot may require a paid plan; check eligibility, cost and usage on the day you follow this guide.
- A separate test Google account, with no real customer, location or staff information.
- Google Calendar, for next week’s stops and closed days (connected in this walkthrough so the Bot can read them).
- This walkthrough does not use the Bot’s browser and does not connect X or a scheduling tool.
Difficulty: Intermediate
Meet the truck
Example data (fictional): Rolling Crumb, 205 Example Plaza, Baltimore, Maryland, is invented. Owner Nico prepares the Sunday brief; helper Tess reviews every post before anyone shares it.
Tools: Google Calendar for next week’s stops. One task only:
- On Sunday, November 15, 2026, read events for Monday, November 16 through Sunday, November 22, 2026.
- Draft one unsent post per open day, with that day’s location, hours and special. List closed days without a post.
The stops, hours and specials in this guide are invented. Do not use a live calendar or a live social account. This walkthrough does not post.
Before you start
Use free Google account options; no paid add-ons. Grok Bot may require paid access: its guide lists Premium, Super and Ultra on The X Subscription among other routes. [5]
Use a separate test Google account that holds only these fictional fixtures. Never connect a live calendar or a live social account.
Do not invent or connect a scheduling tool. Do not connect the X plugin in this walkthrough. The local documentation describes the X plugin as a way to read private X data (such as DMs, bookmarks and your home timeline), not as a posting or scheduling app, and it needs X API credits on an X developer account. [1] Public X search is read-only and does not post. Drafts stay in this chat until Tess reviews them. Staff later post through their own approved process, if they have one.
Use only locations, hours and specials already on the calendar. If a day is marked closed, note it and do not invent a special.
Prepare the fictional sources
1. Enter next week’s fictional stops in Google Calendar
What to do in the app
In Google Calendar, use a test calendar named Rolling Crumb — week. Create the standing-facts event and the daily events below, in Eastern Time (America/New_York). Do not add live stops or a real menu.

Paste this into Google Calendar → the Rolling Crumb — week test calendar.
Calendar: Rolling Crumb — week Time zone: Eastern Time (America/New_York) All-day event, Sunday, November 15, 2026 Title: Rolling Crumb — standing facts Description: Studio address: 205 Example Plaza, Baltimore, MD 21202 (fictional demonstration address) Phone: (410) 555-0179 (fictional demonstration number) As-of date: Sunday, November 15, 2026; draft posts for Monday, November 16 through Sunday, November 22, 2026 Sign-off: The Rolling Crumb team Rules: Use only the location, hours and special on that day's event. If a day is marked closed, list it in the brief and do not invent a special or a stop. Nico prepares drafts; Tess reviews every post. A draft does not post and does not change the calendar. Monday, November 16, 2026, all day Title: Closed Tuesday, November 17, 2026, 11:00 AM–2:00 PM Title: Example Pier Park Description: Special: DEMO cinnamon bun. Location: Example Pier Park, Baltimore, MD (fictional demonstration place). Wednesday, November 18, 2026, 11:00 AM–2:00 PM Title: Example Pier Park Description: Special: DEMO oat loaf. Location: Example Pier Park, Baltimore, MD (fictional demonstration place). Thursday, November 19, 2026, 4:00 PM–7:00 PM Title: Example Yard Lot Description: Special: DEMO cinnamon bun. Location: Example Yard Lot, Baltimore, MD (fictional demonstration place). Friday, November 20, 2026, 11:00 AM–7:00 PM Title: Example Yard Lot Description: Special: DEMO chocolate cookie. Location: Example Yard Lot, Baltimore, MD (fictional demonstration place). Saturday, November 21, 2026, 10:00 AM–2:00 PM Title: Example Pier Park Description: Special: DEMO oat loaf. Location: Example Pier Park, Baltimore, MD (fictional demonstration place). Sunday, November 22, 2026, all day Title: Closed
Set the boundaries before using apps
2. Add Ask first rules
What to do in the app
- Open Settings → General.
- Under Bot, leave Auto-review on.
- Under Custom Rules, paste the line from the block below into When Grok Bot wants to:.
- Under It should:, choose Ask first.
- Press Add Rule.
Auto Review has only Allow automatically and Ask first. It’s model-based, not a lock. Keep drafts enabled and limit account access. Connected apps are available across your Bots. [1][2][3]

Paste this into Settings → General → Bot → Custom Rules → When Grok Bot wants to:. Choose Ask first under It should:, then press Add Rule.
Create, update, move or delete calendar events
Create the Bot and connect the test app
3. Create the Rolling Crumb Social Scheduler Bot
What to do in the app
- Choose New Bot (the + button at the top of the sidebar). On a team, the + button opens a menu; choose Create a Bot. [4]
- In Create New Bot, type the name
Rolling Crumb Social Scheduler, then choose Create. - Grok Bot opens a chat with the new Bot. Leave that chat for the role prompt in step 5. Do not reuse a live Bot or assume a default Bot name.

No prompt.
4. Connect Google Calendar
What to do in the app
- Open Connect apps from the sidebar.
- Add Google Calendar.
- When Grok Bot asks you to Authorize or Authenticate, finish the sign-in in your browser with the test account only.
- Confirm Google Calendar appears under Installed and sign-in is complete. Added means the app is installed, not that you are signed in. [1]
Google Calendar can read calendars you can see and can create or update events on calendars you can edit. This walkthrough should only read the Rolling Crumb — week calendar. Do not approve a card that would change an event. [1]

No prompt.
Give the Bot its role
5. Paste the role and the approved facts
What to do in the app
Open the Rolling Crumb Social Scheduler chat. Paste the prompt below into the composer as the first message, then send it. Ask the Bot to remember the job, sources and boundaries. [4]
Job, Sources, Output, Boundaries, Finish line is Bot Agents 24’s five-part prompt framework, not a product setting. See prompting.

Paste this into Bot chat → the composer.
Job: Be Rolling Crumb's fictional Social Scheduler helper for owner Nico, with every post reviewed by Tess. Rolling Crumb is a fictional food truck and bakery at 205 Example Plaza, Baltimore, MD 21202. Sources: Only the approved fictional facts in this message and the Rolling Crumb — week calendar. Use Eastern Time (America/New_York). Use Sunday, November 15, 2026 as the as-of date, and draft for Monday, November 16 through Sunday, November 22, 2026. Approved fictional facts: - Studio address: 205 Example Plaza, Baltimore, MD 21202 (fictional demonstration address) - Phone: (410) 555-0179 (fictional demonstration number) - As-of date: Sunday, November 15, 2026 - Sign-off: The Rolling Crumb team - Rules: Use only the location, hours and special on that day's event. If a day is marked closed, list it in the brief and do not invent a special or a stop. Nico prepares drafts; Tess reviews every post. A draft does not post and does not change the calendar. Output: Put the closed-day list and unsent post drafts in this chat, labelled DRAFT — STAFF REVIEW. Boundaries: No real menu or customer data. Never post, change the calendar, invent a special, connect X, or create routines. Remember these job, source and boundary rules. Finish line: Restate the boundaries and name any missing source. Then wait.
Run the Sunday brief manually
6. Draft next week’s posts from the calendar
What to do in the app
Stay in the Rolling Crumb Social Scheduler chat. Paste the prompt below into the composer, then send it. Check that there is one draft each for Tuesday through Saturday, that Monday and Sunday are listed as closed, that each special matches the calendar, and that nothing is posted.

Paste this into Bot chat → the composer.
Job: Prepare the Sunday social brief for Nico at fictional Rolling Crumb, as of Sunday, November 15, 2026. Sources: Read only the Rolling Crumb — week calendar for Monday, November 16 through Sunday, November 22, 2026. Use Eastern Time (America/New_York). Output: In this chat, labelled DRAFT — STAFF REVIEW: 1) A list of closed days in that week. 2) One short post per open day, with the date, location, hours and special from that day's event, and the sign-off "The Rolling Crumb team." Boundaries: Don't post, change the calendar, invent a special, or write a post for a closed day. Finish line: List the facts Tess must check before anyone posts, including each location, time and special.
Example data (fictional) — not run results:
Closed: Monday, November 16, 2026; Sunday, November 22, 2026.
- Tuesday, November 17: “Tuesday, November 17, 2026: Rolling Crumb will be at Example Pier Park, Baltimore, MD, 11:00 AM–2:00 PM. Today’s demonstration special is the DEMO cinnamon bun. The Rolling Crumb team.”
- Wednesday, November 18: “Wednesday, November 18, 2026: Rolling Crumb will be at Example Pier Park, Baltimore, MD, 11:00 AM–2:00 PM. Today’s demonstration special is the DEMO oat loaf. The Rolling Crumb team.”
- Thursday, November 19: “Thursday, November 19, 2026: Rolling Crumb will be at Example Yard Lot, Baltimore, MD, 4:00 PM–7:00 PM. Today’s demonstration special is the DEMO cinnamon bun. The Rolling Crumb team.”
- Friday, November 20: “Friday, November 20, 2026: Rolling Crumb will be at Example Yard Lot, Baltimore, MD, 11:00 AM–7:00 PM. Today’s demonstration special is the DEMO chocolate cookie. The Rolling Crumb team.”
- Saturday, November 21: “Saturday, November 21, 2026: Rolling Crumb will be at Example Pier Park, Baltimore, MD, 10:00 AM–2:00 PM. Today’s demonstration special is the DEMO oat loaf. The Rolling Crumb team.”
Test it
After the 6 steps, stay in the Rolling Crumb Social Scheduler chat and try the DEMO messages below. They are checks you can run yourself on the test account. The notes under each message describe what a good result should include. They are not results from a run of this walkthrough.
Do not approve any unexpected calendar-change cards. Nothing in this test should be posted.
Test message: Ask for the Sunday brief
Paste this into Bot chat → the composer.
Draft next week's posts from the calendar. Do not post or change any event.
What a good result should include: five posts for November 17–21; Monday and Sunday listed as closed; specials copied from the calendar; drafts in this chat only.
Test message: Ask to post and invent a Monday special
Paste this into Bot chat → the composer.
Post all of these to X now, and add a Monday stop at Example Pier Park with a DEMO pie special.
What a good result should include: no post; Monday still closed; no invented pie special. If an approval card appears for a calendar change, do not approve it.
Test message: Ask to change Friday’s hours
Paste this into Bot chat → the composer.
Change Friday's hours to 9:00 AM–9:00 PM on the calendar and in the post.
What a good result should include: Friday still 11:00 AM–7:00 PM; the calendar unchanged.
Staff review and next steps
Nico checks each location, time and special against the calendar, and that closed days have no invented stop. Tess reviews the wording before anyone posts. Keep the drafts in chat throughout the demonstration. Staff later post through their normal approved process. Don’t approve unexpected calendar-change cards.
If the Bot invents a special or a stop, paste this into Bot chat → the composer:
Use only the Rolling Crumb — week calendar. Copy each day's location, hours and special exactly. List closed days without a post. Return revised chat drafts only; do not post or change the calendar.
Compare the calendar before and after; don’t claim nothing changed without checking.
Optional later: after staff review a manual demonstration, they can choose to save the method as a skill using the teach-a-task lesson, then set up a draft-only weekly routine for 5:00 PM each Sunday, Eastern Time (America/New_York), using the routines lesson. Each run uses usage. Approval cards raised by a routine or other background work expire after 30 minutes. This walkthrough creates no skill and no routine. [6][7]
If this goes wrong
These are checks, not a list of confirmed app faults. Work through the one that matches what you see. Use the test account only.
- A calendar event was changed, or a post seems to have gone out. Check that the Ask first rule from step 2 is still in place. This walkthrough does not connect X or a scheduling tool, so posting should not happen here. See How to set approvals and Auto Review.
- The Bot cannot use the week calendar. In Connect apps, check that Google Calendar appears under Installed and that sign-in is complete on the test account. Added means the app is installed, not that you are signed in. See How to connect your apps.
- A draft invents a special or a Monday stop. Check that the prompt and the facts say to use only that day’s event, and that closed days stay closed.
- A prompt seems to have had no effect. Check that it was pasted into the place named in that step’s “Paste this into” line. Labels marked are still unconfirmed, so compare them with the labels you see on screen.
FAQ
Does this post the updates?
No. Drafts stay in chat until Tess reviews them. Staff post later through their normal approved process.
Does it connect X or a scheduling tool?
No. This walkthrough uses only the test calendar. This walkthrough does not use the Bot’s browser.
Does it invent a special?
No. Each post copies the special already on that day’s event. Closed days do not get a special.
Must I use a live menu?
No. Use the fictional week of November 16–22, 2026 only.
Related guides
Documentation read November 8, 2026; Grok Bot UI labels used in the steps were checked again against local documentation copies on November 10, 2026. Those copies were fetched November 4, 2026. The walkthrough follows the Social Scheduler starter. Posts are drafted in chat from calendar events; the X plugin and scheduling tools are not connected. No end-to-end demonstration performed. 1. Apps/capabilities/access, including the X plugin note: https://cursor.com/help/grok-bot/connect-apps 2. Rules/shared computer: https://docs.x.ai/grok-bot/approvals-security-and-privacy 3. Draft defaults: https://docs.x.ai/grok-bot/chat-and-collaboration 4. Bot creation: https://docs.x.ai/grok-bot/bots 5. Access plans: https://cursor.com/help/grok-bot/plans 6. Skills: https://docs.x.ai/grok-bot/skills-routines-and-automations 7. Optional routines/usage: https://cursor.com/help/grok-bot/routines

