I created a webhook-triggered routine via the Bot. Opening the routine details on Windows desktop only shows: Enabled toggle, Instructions, “When a webhook fires”, empty run history. There is no gray box with the three click-to-copy fields (POST to URL, Secret crsr_…, Authorization header). Deep links for webhook-url/key/header also do not surface credentials. I am not on iOS—this is desktop 0.47.0. Recreating the routine does not help. The Bot cannot see or emit the URL/key, so external callers cannot use the webhook.
Related: Webhook url missing on ios says credentials are desktop-only, but desktop still lacks the fields here.
Also filed in-app feedback requesting a reply.
Steps to Reproduce
Ask a Grok Bot to create a routine with webhook trigger type webhook.
On Windows desktop Grok Bot, open agent → Routines → that routine.
Observe trigger text only; no POST URL / crsr_ / Authorization fields.
Expected Behavior
Desktop trigger card shows POST URL, sender key, and Authorization header for copy.
Operating System
Windows 10/11
Version Information
0.47.0 x64
Additional Information
Suspected Bot-created webhook routines may not provision credentials to the client so the UI block never mounts.
Hey, thanks for the detailed report and the link to the iOS thread.
You’re right, those fields are actually missing, and it’s not something on your end. New bots store their routines on the server (that’s the note saying “This Bot keeps its routines on the server” in the routine panel), and for these routines the desktop app currently doesn’t fetch or show the webhook URL, key, or Authorization header. Recreating the routine doesn’t change this, and the bot itself can’t provide those values either, so deep links open an empty panel.
This is a known issue we’re already tracking, and I’ve added your report to it. Unfortunately, there’s no way to get the URL or key for this kind of routine right now.
As a temporary workaround, if you need to wake the bot from something external, Slack message triggers work right now (ask the bot to create a routine that runs when a message is posted in a channel you control) or you can use a schedule.
Run into this exact same issue trying to have a bot action emails from Agent Mail as soon as they’re received (push to webhook). But don’t have access to the key to auth the push.
Thank you for update thought I was doing something wrong. Desktop bug is on Mac as well. An update on the situation would be great. Webhook URL and key are nowhere to be found on both desktop versions or mobile app. I just want to know if I can wait for fix or do I have to transfer my accounts to slack paid plan on top of grok bot subscription. Is it an easy bug fix or could it take weeks?
Hey, thanks to both of you for the confirmations. @phonebooth, @Fern, yep, it’s the same issue, and it’s not on your side.
@Fern, confirmed: it’s not Windows-only. Mac and mobile behave the same way. Same root cause: for newer bots, routines are stored on the server (the “This Bot keeps its routines on the server” note in the panel). For these routines, the client currently doesn’t fetch or show the Webhook URL, key, or Authorization header on any desktop app or in the mobile app. Recreating the routine doesn’t change anything, and the bot can’t return those values either.
We’re tracking this issue, and I’ve added your reports to it. I can’t share an exact timeline right now. I won’t promise “soon” or “weeks” since that wouldn’t be fair. When there’s an update, I’ll reply right here.
For now, there’s no way to get the URL or key for this kind of webhook routine. If you need to wake the bot from something external, the working options right now are a Slack message trigger (ask the bot to create a routine that fires on a message in a channel you control) or a schedule. Nothing extra required on your side, just alternative triggers that are available today.
Hey @Robby_Grossman, thanks for confirming. I’ve added your report to the tracked issue as well. @phonebooth, the Agent Mail case belongs here too. The root cause is the same, and it’s not on your side.
Status is unchanged. I can’t share an exact timeline yet, and I won’t promise soon or a couple of weeks since that wouldn’t be fair. As soon as I have an update, I’ll post it right here.
Workarounds to wake the Bot from the outside right now are a Slack message trigger. Ask the Bot to create a routine that triggers on a message in a channel you control. Or use a schedule.
@thomas2018 thanks for sharing your setup. Just a note for anyone trying it. Keep that local endpoint inside a trusted network only via SSH or VPN, and don’t expose it to the public internet, as you warned.
Same issue here, can’t use a webhook and none of the details are displayed on Mobile or MacOS. Currently having Grok do periodic polling via HTTP as a workaround. Would be nice to have the webhooks for sure.
Hey @Kimball_Leavitt, thanks for confirming. Yep, it’s the same issue. For new Bots, routines are stored on the server, and the client (Mac, mobile) doesn’t yet fetch or show the Webhook URL, key, and Authorization header. This isn’t anything on your side.
Your HTTP polling approach is a totally workable workaround for now. For external triggers that are available right now, you can also use the Slack message trigger (ask the Bot to create a routine that fires on a message in a channel you control) or a schedule.
Status hasn’t changed. I can’t share an exact timeline yet, and I won’t promise dates because I don’t want to mislead you. Once I have an update, I’ll reply in this thread.
Found a work around for my issue, total kludge, but I used clipboard paste through Accessibility to kick off the bot. MacOS. Getting a return value is still somewhat problematic, but having the bot write to disk somewhat acceptable at the moment
Grok Bot creates a webhook routine successfully, but the routine detail panel never shows the Webhook URL or Webhook key (sender key) fields, so the URL/key cannot be copied into an external service (Readwise custom webhook).
Steps to Reproduce
In Grok Bot chat, ask the agent to create a routine with trigger { “type”: “webhook” } (e.g. name readwise-reader-brief, enabled).
Confirm the routine appears under the agent’s Routines list as “When a webhook fires.”
Open the routine detail panel (agent name in chat header → Routines → readwise-reader-brief).
Also try the deep links from the agent’s Current routines line: Webhook URL / Webhook key / Authorization header (grokbot://app/v1/sidebar?target=webhook-url|webhook-key|webhook-header&automation=readwise-reader-brief).
Retry after pause/resume, delete+recreate, and create-as-paused then enable.
Expected Behavior
The routine panel exposes copyable Webhook URL and Webhook key (and Authorization header if applicable) so an external system can POST to the routine.
Actual: Panel shows Name, Instruction, “When a webhook fires,” and empty run history — but no URL/key fields under the webhook trigger. Deep links do not surface usable values. The agent cannot read or print the URL/key (by design: credentials stay in the panel only).
Also: empty Routines list has no “+” to add a routine manually (expected for server-managed bot routines; creation via chat works). That is separate from the missing webhook credential fields.
Impact: cannot connect Readwise (or any) custom webhook to the routine. Forced workaround: paste Reader doc links / IDs in chat for one-off briefs.
In-app Send Feedback was attempted from the agent but failed (“unavailable in privacy mode”); user may also file via Help → Send Feedback.
@Grzesiek_Zawlodzki, your screenshot shows it clearly. The routine panel for readwise-reader-brief only shows When a webhook fires, and it doesn’t show the Webhook URL, key, or Authorization fields. The reason is the same as earlier in the thread. For new Bots, routines are stored on the server, and the client apps on Windows, Mac, and mobile currently don’t load or display these credentials. Recreating the routine doesn’t change anything, and the Bot can’t reveal these values either.
I also see that some of you aren’t using Slack. Besides the Slack message trigger, there are two other options that work without external credentials:
Schedule: ask the Bot to run the routine on a schedule.
HTTP polling: like @Kimball_Leavitt described above, the Bot periodically polls the endpoint itself. This works if you need to react to external events without a webhook.
Status is unchanged for now. I can’t share an exact timeline, and I won’t promise soon because I don’t want to mislead anyone. As soon as there’s an update, I’ll reply here.
Ok, I think I’ve solved the webhook problem, Set up a webhook (OUTBOUND) for the bot to access (mine is local). Turns out it can take in requests as well as send responses!!!
