How this helps you
Human-blocker tasks live on cards instead of disappearing inside ten Bot chats.
You are my manager Bot. When a Notion webhook arrives, read Status, Prompt, and all properties. Leave a short comment on the card naming the specialist you will wake. Message that specialist with the Prompt, links, and a definition of done. If Prompt is empty, ask me what to do. Never expose the webhook URL. Do not post publicly or spend money without approval.
What they did
After drowning in chat across CMO, EA, growth, CRM and reply Bots, Xavier asks a Bot to create a webhook under Details and to scaffold a Notion Kanban. He adds a text property named Prompt, builds a Notion automation on status change or Prompt edit, and POSTs full card context to the webhook URL. His manager Bot (Jacob) receives the wake, comments on the card, and wakes the right specialist. He shows typing a video-skeleton brief into Prompt and watching the manager start research. Low views, but a clear advanced ops pattern for human-blocker tasks that chats bury.
Who it's for: Operators running multi-Bot teams who prefer Kanban over scrolling chat.
Before you start
- Notion with database automations
- At least one manager Bot plus specialist Bots
- Willingness to keep webhook URLs private
How to try it
- In the manager Bot's Details, ask it to create a webhook and copy the URL somewhere private.
- Ask the Bot to create a Kanban-style Notion database with Status and a text property named Prompt.
- In Notion Automations, trigger on Status changed or Prompt edited; action Send webhook with the Bot URL and all properties.
- Instruct the manager Bot: on webhook, comment on the card, decide the owner specialist, and message that Bot with the Prompt plus links.
- Test with a safe Prompt ("What is the status of this task?") before you send live client work.
- Add filtered Notion views per function (sales, marketing) so humans steer without opening every chat.
What to expect
You paste a brief into Prompt on a card; Jacob wakes and starts a research handoff while you stay in the Kanban view.
Common mistakes
- Publishing the webhook URL in a video, tweet, or shared Page.
- Firing on every property change and waking Bots in a loop.
- Skipping the manager Bot and letting every specialist listen to the same board.
Related tips
- Route every meeting transcript to the right Bot with a webhook: When your note taker finishes a call, a webhook wakes your Chief of Staff Bot, which reads the transcript and hands it to the Bot that owns that work.
- Run each project as a channel with a roster and a Notion board: A projects manager Bot opens one group chat per project, staffs it from your existing Bots, and tracks tasks on a Notion board with a Blocked column.
- Route Bird customer messages to a webhook routine: Bird's official plugin plus a Grok Bot webhook routine lets incoming Apple Messages or emails wake a Bot that drafts the reply for you to check.
Worth knowingHuman-blocker tasks live on cards instead of disappearing inside ten Bot chats.
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot connectors tips