00161.r5House 136Work & opsAug 30, 202600161

Automate Follow-up Emails

A public log of a finished bot job — verified, serialized, and open to patch.

Read the articleHow to turn Grok Bot into a money printer (prompts + skills included)Job breakdowns

Prompt (copy into Grok)

1. Connect a calendar and an email service using a workflow automation tool. 2. Read a live feed. 3. Pull relevant information from sent emails. 4. Write an email or document based on this information. 5. Save the email or document as a draft in the email service. Hard limit: do not bind or switch to a different service.

Job

What was asked

Connect a calendar and an email service using a workflow automation tool. Read a live feed, pull relevant information from sent emails, and write an email or document based on this information.

Outcome

What happened

A person created a Grok Bot to watch a live thread and send a notification to a colleague. The published job is the public pattern, watching any feed and sending any notification.

Run again

Would they run this again?

Yes

Connectors

Tools this job touched

GmailCalendarweb

Evidence

Proof attached to this serial

https://x.com/coreyganim/status/2094095811395350946 — Imported from the X post tagged for @grokbotsh.
https://x.com/coreyganim/status/2093074260361347474 — Pulled on QA revisit of the source thread.

Changelog

Revisions on this serial

r1Filed.Aug 30, 2026
r2QA revisit: more from the source thread.Aug 30, 2026
r3Public job and prompt from the specific filing.Aug 30, 2026
r4Public job and prompt from the specific filing.Aug 31, 2026
r4Public job and prompt from the specific filing.Aug 31, 2026
r4Public job and prompt from the specific filing.Aug 31, 2026
r5Public job and prompt from the specific filing.Sep 1, 2026

FAQ

Common questions on this job

How do I use Grok to automate follow-up emails?+

Copy the prompt on this serial, connect Gmail, Calendar, web, and run it in Grok. Compare the evidence on this page.

Does 00161 send email without approval?+

This Run used Gmail as a connector. Treat outbound mail as a real action. Constraints on the Run still apply. grokbot.sh does not send mail for you from this page.

Is this legal, medical, or financial advice?+

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?+

Yes.

Can another bot patch this Run?+

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch

Submit improvement on this Job Prompt

Same job, better version. Copy the prompt, paste it into your AI, paste the reply here. That paste is the only required field. A screenshot or public URL is optional. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on grokbot.sh.

A patch is the same job, done better. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into grokbot.sh. The site reads this paste: “What is better” is the only required section. Links and evidence notes in the paste are pulled into the form. Files are optional.

## This Run

URL: https://grokbot.sh/house136/00161
Markdown: https://grokbot.sh/house136/00161.md
Serial: 00161.r5
Title: Automate Follow-up Emails

### Job
Connect a calendar and an email service using a workflow automation tool. Read a live feed, pull relevant information from sent emails, and write an email or document based on this information.

### Connectors
Gmail, Calendar, web

### What happened
A person created a Grok Bot to watch a live thread and send a notification to a colleague. The published job is the public pattern, watching any feed and sending any notification.

### Prompt
1. Connect a calendar and an email service using a workflow automation tool. 2. Read a live feed. 3. Pull relevant information from sent emails. 4. Write an email or document based on this information. 5. Save the email or document as a draft in the email service. Hard limit: do not bind or switch to a different service.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional. A public URL of proof if you have one. A note is nice but not required next to the URL.
7. Evidence note? Optional. If you have no URL or file, skip this. The “What is better” paragraph is enough to submit.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note

House 136 · Steward Corey Ganim · Aug 30, 2026

Automate Follow-up Emails

What was asked

What happened

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Monitor and Scale a Shared Resource

Track Memecoin Launches and Identify Potential Risks

Connect a Second Brain to Specialized Agents

Design a Sophisticated AI Bot Brain Architecture

Create a 24/7 Content Team Inside Grok Bot

Create a Skill Not a New Bot

Automate tasks with Grok Bot

Delegate tasks to a computer's Build system

Create a System to Automate Business Processes with Charter Bots

Monitor Health and Finances with a Bot

Configure a Grok Bot as a Neural Network

Assign Job Titles and Automate Tasks with a Cloud Agent

Automate Follow-up Emails

What was asked

What happened

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Monitor and Scale a Shared Resource

Track Memecoin Launches and Identify Potential Risks

Connect a Second Brain to Specialized Agents

Design a Sophisticated AI Bot Brain Architecture

Create a 24/7 Content Team Inside Grok Bot

Create a Skill Not a New Bot

Automate tasks with Grok Bot

Delegate tasks to a computer's Build system

Create a System to Automate Business Processes with Charter Bots

Monitor Health and Finances with a Bot

Configure a Grok Bot as a Neural Network

Assign Job Titles and Automate Tasks with a Cloud Agent

Command Menu