A news-to-website pipeline with two approval gates

How this helps you

The research and building run overnight while every public step still waits for your word.

Every day at [time], read the Notion page for today, check for anything missed, rank the top [N] stories and write an Edition Draft in Notion. Then stop and wait. Do nothing more until I reply "approve".

What they did

@ai_for_success runs his AI Compass newsletter site with four Bots. Compass_Scout runs at 11 PM, 3 AM and 8 AM IST, watching 55 accounts through 10 grouped X queries plus discovery searches. It checks primary sources, separates confirmed news from trending but unverified stories, removes duplicates and saves to that day's Notion page. Compass_Editor auto-runs at 8:30 AM, checks for anything missed, ranks the stories, writes an Edition Draft in Notion, then stops until he replies "approve". When he says "publish yesterday's edition", AIFS_Ops confirms the page is marked Approved and hands the brief to AIFS_Dev, which launches a Cursor Cloud Agent on his GitHub repo. The agent researches official sources, writes the articles, opens a PR and a Vercel preview. It merges only when he says "publish". If he hits cloud agent limits, he switches the build to Google Antigravity on his Mac.

Who it's for: People publishing a regular newsletter or site from X and web news.

Before you start

• Notion, GitHub and Cursor Cloud Agents connected.
• A site that deploys previews from pull requests (his uses Vercel).

How to try it

1. Build the scout first: a routine with your watchlist that writes verified items to a dated Notion page.
2. Add the editor: a later routine that ranks and drafts, then waits for "approve".
3. Add an ops Bot that only checks the Approved status and hands off.
4. Add a dev Bot that launches a cloud agent to write, open a PR and a preview.
5. Review the PR and preview; reply "publish" to merge.

What to expect

A ranked draft waiting in Notion each morning, and a PR with a preview link after you approve.

Common mistakes

• Letting one Bot do everything. Each gate sits between two Bots.
• Skipping the source check. His scout separates verified from unverified before anything is drafted.

Related tips

• A daily X digest in Slack: Watch what people do with Grok Bot on X and Slack you a 9am digest.
• Fact-check before you publish: It checked 11 claims against 9 sources and quoted the line behind each.
• Watch coding work live and get recordings back: With Cursor connected, your Bot links you to the cloud agent live and sends screenshots and screen recordings.

Worth knowingA full build shared by its author, with the steps in his own words.

Learn more: Grok Bot Use Cases: Real Workflows From Real Users · All Grok Bot workflows tips