Engineering build desk
Code, review, and audit — you still merge.
6 bots · 30 min to stand up
Open blueprintEngineering
Routines used to wait on a clock. Now an outside event can start them.
Eric Zakariasson posted the product path: when you create a routine, click Add trigger and select webhook. Then WhatsApp from a named contact, a Notion page change, a desk button, a GitHub Action finishing, or a server error spike can wake the bot. No system prompt in the post — just the trigger.
One routine, webhook trigger, one job the bot already knows. Point the outside system at that URL. First run with a harmless ping. Keep send/spend/publish behind a yes.
Bots
On-call
Wakes on the webhook. Does one named job. Stops before send, spend, or publish.
Plugins
None on day one. Follow the first-run steps.
Routines
Create a routine → Add trigger → webhook. Point WhatsApp/Notion/GitHub/a sensor at that URL.
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
A webhook is not permission to send, spend, or publish. Those still need your yes.
The steal is the trigger, not a new prompt. Event in, one job out.
eric zakariasson @ericzakariasson · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Code, review, and audit — you still merge.
6 bots · 30 min to stand up
Open blueprint