Automate Help Center Updates with APIs

JSON· Markdown· House 055 · Steward Damon Chen · AI researcher and developer

Job

Use APIs to watch for merged PRs, check for UI changes, update help articles, and draft new ones if needed, and take screenshots if necessary

Connectors

web

What happened

A user configured a bot to watch for merged PRs, check for UI changes, update help articles, and draft new ones if needed. The bot takes screenshots if necessary and accesses various APIs, including those of Intercom, GitHub, and Notion. This automation allows the user to focus on building the product without having to manually update the help center. This job is a public pattern, and it can be repeated by others.

Would run again

Yes

Evidence

https://x.com/damonchen/status/2090319001813676471 — Imported from the X thread tagged for @tryreallybot.

Changelog

r1: Filed. (Aug 20, 2026)
r2: QA revisit: more from the source thread. (Aug 20, 2026)
r3: Public job and prompt from the specific filing. (Aug 20, 2026)

FAQ

How do I use Grok to automate help center updates with apis?

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

Does 00207 send email without approval?

This Run does not list a mail connector. Nothing on this page sends email.

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/house055/00207
Markdown: https://really.bot/house055/00207.md
Serial: 00207.r3
Title: Automate Help Center Updates with APIs

### Job
Use APIs to watch for merged PRs, check for UI changes, update help articles, and draft new ones if needed, and take screenshots if necessary

### Connectors
web

### What happened
A user configured a bot to watch for merged PRs, check for UI changes, update help articles, and draft new ones if needed. The bot takes screenshots if necessary and accesses various APIs, including those of Intercom, GitHub, and Notion. This automation allows the user to focus on building the product without having to manually update the help center. This job is a public pattern, and it can be repeated by others.

### Prompt
Set up a bot to watch for merged PRs, check if they changed the UI or user workflow, and update help articles accordingly. If necessary, take screenshots and upload them to a help center platform. Access various APIs to automate the process.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: 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