Start a Grok Bot routine by webhook
Start a Grok Bot routine the moment a form entry, store order or CRM event arrives, using the routine's webhook URL and key, with sends kept behind approval.
For small-business owners whose form tool, store or CRM can send webhooks · Grok Bot · Intermediate
Researched, not run yetWhat that means
Copy the prompt
Fill in the [brackets] after you paste it.
PART 1:
Save the process we just used as a skill called "[SKILL NAME, e.g. New quote request]". Include: when to use it; the inputs it needs (the fields a [form entry / store order / CRM record] sends, such as [FIELD NAMES]); the order of work; how to check the result; what to return in this chat; and the rule that anything that sends, posts, books or spends waits for my approval. Show me the skill before you save it.
PART 2:
Add a routine with a webhook trigger that runs the "[SKILL NAME]" skill on the JSON body each call sends. Only act when the body is a [new form entry / new order / new deal] with [REQUIRED FIELD]; otherwise, report what arrived and stop. If a required field is missing, say which one and do not guess. Post the result in this chat. Do not send, post, book or spend anything without my approval. Never repeat the webhook key in chat. Then tell me where to find the routine's Webhook section.Copied. Paste it into Grok Bot next.
Free PDF
Get this setup as a PDF
Enter your email and a print-ready copy of this setup opens here, to save as a PDF. The free starter pack opens too. Tap confirm in the email that follows to get occasional new setups. Unsubscribe anytime.
Already a subscriber? Unlock it on this device
Free PDF
A confirmation email is on its way too: tap confirm in it to get new setups by email.
Three ways to run this setup
Free
Copy and paste it yourself
Copy the prompt above into ChatGPT, Claude or Grok. It drafts. You approve.
Go to the prompt$9 once
Complete Pack
One payment, no membership. Opens the pack pages: Bot Safety Checklist, Second Brain Starter Vault, Voice File Starter, Tested Grok Bot prompt pack, Write it as code prompts.
See the Complete PackFree to start, VIP $19 a month
Save it as a bot in the guided setup app
The app turns this setup into a bot with the draft-only rules. 3 setups build free; the rest are part of VIP. A human reviews a prompt or setup for you within 24 hours, up to 2 a month.
Build it in the app
Want this one tested next? Vote for it.
What you get back
Illustrative: what one routine run could post in the Bot's chat, not from a real run.
- New quote form entry: a homeowner, gutter repair, wants a call Thursday after 3
- Logged to the lead sheet as row 14 (status: new)
- Reply drafted and waiting for your OK. Nothing sent.
3 steps
- Copy the prompt.
- Paste it into Grok Bot.
- Fill in the [brackets], then read the answer before you send or use it.
Quick answer
Make the job work once in chat on a sample, save it as a skill, then ask the Bot to add a webhook trigger to a routine that runs it. Open the routine on desktop and copy the three fields in its Webhook section: POST to (the URL), key, and header (Authorization: Bearer plus the key). Paste them into the webhook settings of your form tool, store or CRM, send one test, and check the Bot's chat and Run history. A 200 reply means a run started, not that it finished. Keep the key secret and keep anything that sends or spends behind approval.
How do you set it up?
Skip this if
- The sending app has no place to add a custom header. It then cannot send the key, and a call without the current key starts no run.
- A morning or hourly schedule is fast enough for the job. A schedule is simpler and has no key to protect.
Done after day one
One test entry from the sending app started a routine run, and the result showed up in the Bot's chat.
Tools
- Grok Bot on desktop (the Webhook fields are on the desktop routine view) and, for Run history, the phone app
- A form tool, store or CRM with webhook settings that let you set the URL, the POST method and a custom header
- One sample entry, order or record to test with, with no real customer details
Steps
- Pick one event and one job, for example: a new quote form entry, logged and drafted as a reply. Then do the job once in a chat with the Bot, using a pasted sample entry, until the result is right. xAI's advice is to start with a one-time task, make it reliable, save it as a skill, and only then automate it.
- Save the method as a skill. Run the first part of the prompt below. A useful skill says when to use it, what inputs it needs, the order of work, how to check the result, what to return, and what needs approval.
- Ask the Bot to add a webhook trigger. Run the second part of the prompt below in the same chat. It asks for a routine that runs the skill on the JSON body the app sends, with a narrow rule for what to act on and what to do when fields are missing.
- On desktop, click the Bot's name at the top of the chat, open the Details tab and open the new routine. Its Webhook section shows three fields: POST to (the URL), key (the secret), and header (Authorization: Bearer followed by the key, ready to copy). Click a field to copy it.
- In the sending app, open its webhook settings (in a forms tool, a store or a CRM, it is usually under settings, integrations or notifications). Paste the POST to URL as the destination, choose POST, and add the header: the name Authorization with the value Bearer and the key, or the full header field if the app takes one line. Send a JSON body if the app offers it; the Bot receives the body with the routine instruction.
- Send one test: submit a test form entry, place a test order, or create a test record with no real customer details. If the app shows the reply, a 200 means Grok Bot accepted the call and started a run, not that the Bot has finished. Any other reply means no run started: check that the routine is not paused and that the call uses the current key.
- Check the result. Read the Bot's chat for the run's output. On the phone, open the Bot's profile, then Routines, tap the routine and read Run history: each recent run shows as Running, Succeeded or Failed, with the reason for a failed run. No runs yet means nothing has started it.
- Keep the approval. In Settings, General, under Bot, keep Auto-review on and add an Ask first rule for each action that sends or spends, such as "Ask first before sending any external email." xAI says email from a routine waits as a draft until you press Send.
Where to paste this prompt
Grok Bot → paste the prompt into a chat, or save it as a routine or scheduled task if the job repeats
More ways to run it
Which chat tools work with this prompt?
This prompt needs routines and connectors, so it's written for:
- Grok Bot
How sure is this?
Last updated: · Last reviewed:
Before you use this
Who it is for: Small-business owners whose form tool, store or CRM can send webhooks, and who want new leads or orders picked up right away instead of on the next scheduled run.
What it is allowed to do: Drafts for you. Writes drafts (emails, posts, plans, replies). You review and send. Nothing goes out without you.
At a glance: time, cost and difficulty
At a glance
All outcome figures are estimates from cited sources, not independent verification by us.
- What it is allowed to do
- Drafts for you
Writes drafts (emails, posts, plans, replies). You review and send. Nothing goes out without you.
- Time saved (estimate)
- Not measured yet
- Difficulty
- Intermediate
- Tools needed
- Grok Bot
- Typical cost
- Grok Bot: every routine run spends usage, and a Test run spends usage too, because it does the work (xAI). Plan prices: Not stated in sources. Webhooks in your form, store or CRM: depends on that app and its plan; Not stated in sources.
Reviewed Nov 6, 2026
Basis (estimate): No timing claim: nothing in the sources measures time spent or saved for this job.
What usually goes wrong?
Where agents tend to stall on this job. More patterns in Where AI gets stuck.
- The app replies with something other than 200. Check that the routine is not paused and that the header uses the current key.
- The app got a 200 but nothing shows up yet. A 200 means the run started, not that it finished; check the Bot's chat after a minute.
- Testing with an entry made before the trigger existed. Only new events start a run.
- A busy form or store hits the hourly limit. Narrow what the routine acts on, or move it to a schedule.
What tips make it smoother?
- Keep the trigger narrow. One form or one order type per routine is easier to check than a routine that reacts to everything.
- Name the routine after the event, like New quote form, so its row in Details says what starts it.
- Use Test on the routine after each edit, with a safe sample, before you rely on real events.
- Write down which app holds the key, so you know where to change it later.
Where do the claims come from?
Summaries use public sources linked below, not independent verification. How setups are picked.
- Read xAI’s write-up (docs.x.ai)
xAI: Skills and routines (read 2026-11-06): start with a one-time task, make it reliable, save it as a skill, then automate; what a useful skill states; routines can start from a webhook call; Webhooks section: ask the Bot to add a webhook trigger, open the routine on desktop, POST to is the URL, key is the secret sent as Authorization: Bearer <key>, header is the full header to copy; optional JSON body is passed with the routine instruction; 200 means a run started, not finished; any other reply means no run started; only new activity counts; Run history on the phone; Test spends usage; rate limits of 300 runs an hour for all routines and 200 an hour per routine; Automation run rate limit exceeded is not retried automatically; require approval for sending, purchasing, deleting or publishing.
- Read xAI’s write-up (docs.x.ai)
xAI: Approvals, security, and privacy (read 2026-11-06): Auto-review and Ask first rules in Settings, General, under Bot; email from a routine waits as a draft until you press Send; approval cards raised by a routine expire after 30 minutes; do not send an API key in ordinary chat.
- Read Cursor (Grok Bot help)’s write-up (cursor.com)
Cursor (Grok Bot help): Routines help article (read 2026-11-06): the Webhook section shows the URL and key for a routine that a webhook call starts; for a webhook, the call must return 200 and use the current key; for a rate limit failure, send the webhook call again.
Common questions
- Where is the webhook URL for a Grok Bot routine?
- Ask the Bot to add a webhook trigger, then open the routine on desktop. The Webhook section shows POST to (the URL), key and header, and a click copies each one.
- What does a 200 response from a Grok Bot webhook mean?
- Grok Bot accepted the call and started a run. It does not mean the Bot has finished, so check the Bot's chat for the result.
- How many times an hour can a webhook start a routine?
- xAI says all of your routines together can run up to 300 times an hour, and each routine up to 200 times an hour.
Free kit by email
Get the free kit by email
The starter pack and the Portable AI Office, sent to your inbox. New setups by email after that. Unsubscribe any time.
What to do next
- Morning inbox briefing and multi-inbox triage
Start the day with a short “what needs you” note, and periodically sort multiple inboxes into reply vs FYI vs junk, with drafts for your approval, not auto-send.
- Connect your bot to a CRM the safe way
Connect your bot to a CRM or field-service app through the safest available route, starting read-only and widening access only after a test.
- Turn a good bot run into a saved routine
Save a bot run that worked as a written routine, test it on a second input, then schedule it with outward actions kept behind your approval.
Have a setup that works? Submit it. We credit sources and write it up in plain language.