Grokbot TemplatesGrokbot Templates
All use cases

Engineering

Wake a bot from anywhere with a webhook trigger

Routines used to wait on a clock. Now an outside event can start them.

Share

What hurt

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.

What to install or create

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.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read the cited post. The path is Add trigger → webhook.
  2. 2Pick one job the bot already does well by hand.
  3. 3Create a routine, add trigger, select webhook. Copy the URL.
  4. 4Fire a harmless test event (a Notion dummy edit, a GitHub ping, a desk button).
  5. 5Watch the first wake. Send, spend, and publish still wait for you.

Approval fence

A webhook is not permission to send, spend, or publish. Those still need your yes.

What to tweak

The steal is the trigger, not a new prompt. Event in, one job out.

Source

eric zakariasson @ericzakariasson · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Related team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro