This walkthrough uses a fictional business and test accounts only. It sets up no live messages or routines.
This walkthrough prepares one Wednesday brief from a transcript and voice examples you type. It does not transcribe video or audio, post or schedule to a social platform, or connect X, YouTube, a podcast host or an LMS.
At a glance
What you’ll have at the end
A fictional Ridge Line Content Repurposer Bot, set up on a test account, that can:
- Read a transcript and voice examples you type into a test Drive folder.
- Draft five short posts and one newsletter section in this chat, using only that transcript and those examples.
Staff still review every draft and decide what is posted, if anything. This walkthrough has not been run end to end. A Wednesday 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 student, customer or course-platform information.
- Google Drive, for a transcript and voice examples you type yourself (connected in this walkthrough so the Bot can read them).
- This walkthrough does not use the Bot’s browser, does not connect X or a scheduling tool, and does not transcribe a video or audio file.
Difficulty: Intermediate
Meet the course
Example data (fictional): Ridge Line Lessons, 9 Example Court, Boise, Idaho, is invented. Creator Jude types the week’s transcript and reviews every post and newsletter section before anything is published.
Tools: Google Drive for the transcript file. One task only:
- As of Wednesday, November 18, 2026, read the typed transcript for DEMO-W47 and draft five posts and one newsletter section in Jude’s approved voice. Do not invent a line that is not in the transcript. Do not post.
The course, transcript and voice examples in this guide are invented. The transcript is text Jude already typed; this walkthrough does not create it by transcribing a recording. This walkthrough does not publish a post or a newsletter.
This course example uses Mountain Time (America/Boise).
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 course folder or a live social account. Google Drive can search and read files the connected Google account can open, not only the file you name in a prompt. Saving a file to Google Drive creates a new file, so keep drafts in this chat and do not approve a save or create card in this exercise. [1][6]
Do not invent or connect X, a scheduling tool, YouTube, a podcast host or an LMS, and do not use the Bot’s browser to open one. 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 Jude reviews them.
This walkthrough does not transcribe video or audio. You type a short demonstration transcript into the doc, or paste text you already have. There is no file-arrival trigger; you run the brief after the transcript is in the folder.
Voice examples on the doc are the only style guide. Posts and the newsletter section must restate ideas already in the transcript. If a point is not there, skip it; do not invent a result, a quote or a statistic.
Prepare the fictional sources
1. Enter the fictional transcript and voice examples in Google Drive
What to do in the app
In Google Drive, make a folder named Ridge Line — week. In that folder, create a Google Doc named DEMO-W47 — transcript. Enter the fictional text below. Do not add a live course recording, student names or quotes from a source you do not own.

Paste this into Google Docs or Google Drive → the DEMO-W47 — transcript document in the Ridge Line — week folder.
Fact: Hours Approved answer: Weekday office hours 9:00 AM–3:00 PM, Mountain Time (America/Boise) Fact: Location Approved answer: 9 Example Court, Boise, ID 83702 (fictional demonstration address) Fact: Phone Approved answer: (208) 555-0184 (fictional demonstration number) Fact: As-of date Approved answer: Wednesday, November 18, 2026 Fact: Transcript Approved answer: This file is a demonstration transcript Jude typed. Do not transcribe a video or audio file. Use only the beats already written here. Fact: Voice Approved answer: Keep this short and practical. Say "you" and give one next step. Don't hype. Don't invent a result. Fact: Sending Approved answer: Jude reviews every post and newsletter section. A draft does not post, schedule, send a newsletter, or change a Drive file. Voice example 1: Keep this short and practical. Voice example 2: Say "you" and give one next step. Voice example 3: Don't hype. Don't invent a result. DEMO-W47 — Lesson 1, Welcome and setup (transcript Jude typed): Beat 1: Welcome to Lesson 1 of the demonstration course Example Research Folder. Beat 2: Create one folder for the project and name it clearly. Beat 3: Put source notes in that folder, one file per source. Beat 4: Review the folder once a week for 15 minutes. Beat 5: Next lesson will cover a short source list.
Set the boundaries before using apps
2. Add an Ask first rule
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, edit, delete or move files in Google Drive
Create the Bot and connect the test app
3. Create the Ridge Line Content Repurposer 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
Ridge Line Content Repurposer, 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 Drive
What to do in the app
- Open Connect apps from the sidebar.
- Add Google Drive.
- When Grok Bot asks you to Authorize or Authenticate, finish the sign-in in your browser with the test account only.
- Confirm Google Drive appears under Installed and sign-in is complete. Added means the app is installed, not that you are signed in. [1]
Google Drive can search and read files the connected account can open. Saving a file to Google Drive creates a new file. This walkthrough should only read the DEMO-W47 — transcript doc in Ridge Line — week. Do not approve a save or create card in this exercise; drafts stay in chat. [1][6]

No prompt.
Give the Bot its role
5. Paste the role and the approved facts
What to do in the app
Open the Ridge Line Content Repurposer 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 Ridge Line Lessons' fictional Content Repurposer helper for creator Jude. Ridge Line Lessons is a fictional course studio at 9 Example Court, Boise, ID 83702. Sources: Only the approved fictional facts in this message and the DEMO-W47 — transcript doc in the Ridge Line — week folder. Use Mountain Time (America/Boise). Use Wednesday, November 18, 2026 as the as-of date. Approved fictional facts: - Hours: Weekday office hours 9:00 AM–3:00 PM, Mountain Time (America/Boise) - Location: 9 Example Court, Boise, ID 83702 (fictional demonstration address) - Phone: (208) 555-0184 (fictional demonstration number) - Transcript: This file is a demonstration transcript Jude typed. Do not transcribe a video or audio file. Use only the beats already written there. - Voice: Keep this short and practical. Say "you" and give one next step. Don't hype. Don't invent a result. - Sending: Jude reviews every post and newsletter section. A draft does not post, schedule, send a newsletter, or change a Drive file. Output: Put the Wednesday brief in this chat, labelled DRAFT — STAFF REVIEW. Boundaries: No live course or student data. Never post, schedule, transcribe a recording, invent a quote or a result, or create routines. Remember these job, source and boundary rules. Finish line: Restate the boundaries and name any missing source. Then wait.
Run the Wednesday brief manually
6. Draft five posts and one newsletter section from the typed transcript
What to do in the app
Stay in the Ridge Line Content Repurposer chat. Paste the prompt below into the composer, then send it. Check that there are five post drafts and one newsletter section, that each restates a beat already on the transcript, that the voice examples are followed, and that nothing is posted or saved to Drive.

Paste this into Bot chat → the composer.
Job: Prepare the Wednesday brief for Jude at fictional Ridge Line Lessons, as of Wednesday, November 18, 2026. Sources: Read only the DEMO-W47 — transcript doc. Use Mountain Time (America/Boise). Output: In this chat, labelled DRAFT — STAFF REVIEW: 1) Five short post drafts, each restating one of the five beats already on the transcript, in the approved voice. 2) One newsletter section that summarizes the same five beats, in the same voice. 3) A short note that nothing is being posted or scheduled. Boundaries: Don't post, schedule, transcribe a recording, invent a quote, result or statistic, or change a Drive file. Finish line: List the beats used and any transcript line that was skipped.
Example data (fictional) — not run results:
- Post 1. Welcome to Lesson 1 of Example Research Folder, with one next step left for the later beats.
- Post 2. Create one folder for the project and name it clearly.
- Post 3. Put source notes in that folder, one file per source.
- Post 4. Review the folder once a week for 15 minutes.
- Post 5. Next lesson will cover a short source list.
- Newsletter section. A short recap of those same five beats, in the approved voice, with no invented result. All six pieces stay in chat, unsent.
Test it
After the 6 steps, stay in the Ridge Line Content Repurposer 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 Drive cards. Nothing in this test should post or transcribe a recording.
Test message: Ask for the Wednesday brief
Paste this into Bot chat → the composer.
Draft five posts and one newsletter section from the DEMO-W47 transcript. Do not post, and do not invent lines.
What a good result should include: five post drafts and one newsletter section; each point already on the transcript; nothing posted.
Test message: Ask to transcribe and post
Paste this into Bot chat → the composer.
Transcribe this week's video, post the drafts to X, and add a YouTube link.
What a good result should include: no transcription of a recording; no post; no YouTube link invented. If an approval card appears, do not approve it.
Test message: Ask to invent a result
Paste this into Bot chat → the composer.
Add that students doubled their output after Lesson 1, and put the posts in a new Drive doc.
What a good result should include: no invented result; the Drive folder unchanged. If a save or create card appears, do not approve it.
Staff review and next steps
Jude checks that every post and the newsletter section restate beats already on the transcript and follow the voice examples. Keep the drafts in chat throughout the demonstration. Don’t approve unexpected Drive cards. If Jude later wants the text in a Doc, they can paste it themselves.
If the Bot invents a line, transcribes a recording, or tries to post, paste this into Bot chat → the composer:
Use only the DEMO-W47 — transcript doc. Do not invent a line or transcribe a recording. Return revised chat drafts only; do not post or change a file.
Compare the Drive folder before and after; don’t claim nothing changed without checking.
Optional later: after Jude reviews 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 12:00 PM each Wednesday, Mountain Time (America/Boise), 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. [7][8]
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 Drive file was created or changed, or a draft seems to have been posted. 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. Do not approve unexpected cards. See How to set approvals and Auto Review.
- The Bot cannot use the transcript file. In Connect apps, check that Google Drive 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 line, a result, or a transcription of a recording. Do not use that text. Paste the correction prompt in Staff review and next steps.
- 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 drafts or send the newsletter?
No. The posts and the newsletter section stay in chat until Jude reviews them. This walkthrough does not post or schedule anything.
Does it transcribe a video or audio file?
No. You type the demonstration transcript, or paste text you already have. This walkthrough does not transcribe a recording.
Does it connect X, YouTube or a course platform?
No. This walkthrough uses only the test Drive folder. It does not use the Bot’s browser and does not connect X, a scheduling tool, YouTube, a podcast host or an LMS.
What if I want the drafts in a Doc?
Leave them in chat for this exercise. If you later want them in a Doc, paste them yourself. Do not approve a Drive save or create card here.
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 transcript is text the reader types; this walkthrough does not transcribe video or audio. Drafts stay in chat. The X plugin, scheduling tools, YouTube, podcast hosts and LMS connectors are not connected. No end-to-end demonstration performed. 1. Apps/capabilities/access, including Google Drive and 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. Google file permissions, and Drive save-creates-a-new-file: https://support.google.com/drive/answer/7166529?hl=en; https://docs.x.ai/grok-bot/files-and-results 7. Skills: https://docs.x.ai/grok-bot/skills-routines-and-automations 8. Optional routines/usage: https://cursor.com/help/grok-bot/routines

