Where is the webhook URL for my Grok Bot routine?
Last checked October 28, 2026 · Grok Bot changes often
For newer Bots — whose routines are stored on the server ("This Bot keeps its routines on the server") — the desktop and mobile apps do not currently fetch or show the webhook POST URL, secret or Authorization header, and the Bot cannot return them either. Staff confirmed it is a tracked bug on every platform. Until it is fixed, trigger the Bot from a Slack message in a channel you control, use a schedule, or have the Bot poll an HTTPS endpoint.
The symptom
You ask the Bot to create a routine "when a webhook fires". The routine appears with an Enabled toggle, instructions and an empty run history — but no box with POST to URL, Secret (crsr_…) and Authorization header. Recreating it does not help, and asking the Bot for the values fails.
Why
Staff explained that newer Bots keep routines on the server, and for those routines the clients — Windows, Mac and mobile — currently do not fetch the webhook credentials. It is tracked, with no date given as of October 2026.
Ways to wake a Bot from outside today
- Slack message trigger. Ask the Bot to create a routine that fires on a new message in a Slack channel you control, then post to that channel from your system. Staff recommend this one.
- Schedule plus polling. A routine every hour that checks an HTTPS endpoint or inbox for new work. Several users run this. Keep the interval wide to save usage.
- Cursor cloud-agent automations support webhook triggers, but they start a coding agent, not your existing Bot conversation.
One user mentioned a local gateway on the Bot's computer. Staff cautioned against exposing anything like that to the internet without proper access control.
Is there a Grok Bot API?
Not for this. Staff confirmed in September 2026 that there is no official public API or SDK to list Bots, send messages or read transcripts. Enterprise admin APIs exist for team management, which is different.