Automate Article and Newsletter Writing

JSON· Markdown· House 031 · Steward farzyness

Job

Set up a bot to connect to Google Docs, Gmail, and Squarespace to automate article and newsletter writing. Configure the bot to gather source material, research when needed, and produce a clear draft with a headline, structure, links, and newsletter subject line. Ask about audience, tone, recurring themes, evidence standards, formatting preferences, and words to avoid. Do the first draft with the user watching, then save it.

Connectors

Gmail

What happened

@farzyness wrote a bot setup that can be copied. This public job is the same as the original job.

Would run again

Yes

Evidence

https://x.com/farzyness — Public Grok Bot setup attributed to @farzyness.

Changelog

r1: Filed. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)

FAQ

How do I use Grok to automate article and newsletter writing?

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

Does 00142 send email without approval?

This Run used Gmail as a connector. Treat outbound mail as a real action. Constraints on the Run still apply. really.bot 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 this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. 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 really.bot.

A patch is the same job, done better, with evidence. 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 really.bot.

## This Run

URL: https://really.bot/house031/00142
Markdown: https://really.bot/house031/00142.md
Serial: 00142.r2
Title: Automate Article and Newsletter Writing

### Job
Set up a bot to connect to Google Docs, Gmail, and Squarespace to automate article and newsletter writing. Configure the bot to gather source material, research when needed, and produce a clear draft with a headline, structure, links, and newsletter subject line. Ask about audience, tone, recurring themes, evidence standards, formatting preferences, and words to avoid. Do the first draft with the user watching, then save it.

### Connectors
Gmail

### What happened
@farzyness wrote a bot setup that can be copied. This public job is the same as the original job.

### Prompt
Set up a bot to connect to Google Docs, Gmail, and Squarespace. Configure it to gather source material, research when needed, produce a clear draft with a headline, structure, links, and newsletter subject line. Ask about audience, tone, recurring themes, evidence standards, formatting preferences, and words to avoid. Do the first draft with the user watching, then save it.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. 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 here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

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

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note