Grok BotTurn yesterday's X bookmarks into a tagged Notion database every morning
@fabianschierz set up a Grok automation that runs daily at 4am, collects the previous day's X bookmarks and sends them as a JSON array to a Grok Bot named Polly.
A prompt to try
Fill in the blanks. The prompt rewrites itself.
Every day you'll receive a JSON array of my X bookmarks from yesterday. For each post: open it again and fill in anything missing (author, full text, links). Then add one row to my Notion database [DATABASE NAME] with: title, author, URL, extra URLs, 2 to 4 tags from [TAG LIST], topic, a one-line summary and why it matters to me. Skip duplicates. Don't like, reply to or repost anything.
Fill in anything in [brackets] before you send it. Anything that spends money, sends a message or signs something should stay behind your own approval.
How it went, step by step
- 01Create the Notion database first with the columns you want (title, author, tags, URLs, summary).
- 02Schedule the Grok automation for a quiet hour and send its JSON to the bot.
- 03Give the bot a fixed tag list so the database stays filterable.
- 04Add a weekly routine that asks the bot which bookmarks fit each project.
More like this
Grok BotKeep an 'on-deck' sheet of Grok Bot templates and review it weekly
@gambrill (Oct 15) keeps seeing Grok Bot templates they want to add, so they asked Grok Bot to build an "on-deck circle": a Google Sheet listing each bot template, its link and what it does.
Answer the messages a support bot missed during a server outage, then switch the catch-up off
Freelance automation developer Dmitry Prozorovsky runs an n8n-based AI support bot for a motorcycle-gear shop's VK community.
Claude CodeCut over a 45-million-message alerting system with Claude Code and an operator go
Kaizen (Ashish Tonse, Oct 6, 2026) moved a nine-year-old alerting system that had sent/received 45 million messages onto their main platform with Claude Code running a 61-step runbook.