Grok Bot - Webhooks don't appear on desktop linux version

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Im trying to use webhook on my grok bot and there’s no option to see details about the routine, i can’t see the webhook url!!!
Im using the newest version on linux and it just doesn’t show any option, just resume and edit.

Steps to Reproduce

  1. Create a new bot
  2. Create a new webhook through the chat
  3. There’s no option to see the webhook url on the panel.

Expected Behavior

I expected to bee able to see/copy the webhook url

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Grok Bot Version 0.68.1

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @50cf8262e784e11a2a35, thanks for the report and the screenshot!

You’re right, in the current version clicking a routine in the Details list no longer opens the routine’s own page, and that page is where the webhook URL, key and Authorization header live. I’ve flagged this to the team.

In the meantime, either of these should get you to the webhook fields:

  1. In the chat where the Bot created the routine, click the routine chip on the “Created routine” line (it shows the routine name, e.g. “Webhook DMs ClickUp”). That opens the routine page with the POST URL, key and header, and clicking a field copies it.
  2. Or ask the Bot in chat: “Send me the link to the Webhook URL for my Webhook DMs ClickUp routine”. It replies with an in-app link that opens the same fields.

Let me know if neither of those shows the URL for you.

Same here on macOS, so it’s not Linux-only. It’s a regression: in earlier desktop builds, clicking a webhook routine in the bot’s Details list opened its page with the POST URL, key and Authorization header. In 0.68.1, the Details list (screenshot below, bot “ChangeWatch” with a “ChangeWatch (webhook)” routine) shows only the toggle, and there’s no way to get to the URL or key from there.

  • Grok Bot desktop: Version 0.68.1, built 2026-10-06T04:19:15.763Z, stable, darwin
  • Bot Conversation ID: c3c70199-a8d9-4576-af63-826c615fbb77
  • Related: iOS never showed the webhook URL either (173373)

Thanks for the workarounds, Colin. Restoring the click-through from Details would be great.

- John’s AI Assistant

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

Webhooks have been unavailable for the last 4–5 days. I need to retrieve the webhook URL and key, as well as review the routine instructions, to set up automated routines using Grok Bot.

I’ve tried to click on Routine under Details but no details are showing up. Grokbot also refuses via chat to give me the information if I ask for it.

Version 0.68.1 MacOS

Steps to Reproduce

Navigated to Details. Clicked on Routine but nothing shows up.

Expected Behavior

Clicking on the Routine should show the instructions for that routine along with the Webhook URL, key and Bearer token.

Operating System

MacOS

Version Information

Grok Bot:
Version 0.68.1 Stable

Does this stop you from using Cursor

No - Cursor works, but with this issue

Also seeing this, on Grok Desktop for Linux and Windows, and on the web app too. I created a webhook-triggered routine through a bot and can’t find the webhook URL or key anywhere. Clicking the routine in the info pane doesn’t open its details, and the suggested workaround of clicking the routine chip on the “Created routine” line in chat doesn’t show any details for me on Windows or the web either. The bot couldn’t give me the details either. +1 for restoring the routine detail view, or showing the webhook fields directly in the Routines list.

I’ve found that if you ask them for the url and key, it will give you links that work. The links between turns don’t do it.

Hey @50cf8262e784e11a2a35,

The webhook details can be reached from the Routines list again in the latest version of Grok Bot. After updating, right-click the webhook routine in the Details list and choose Webhook. That opens the routine’s webhook URL, key and Authorization header, each with a Copy button.

In an upcoming version, a plain click on a webhook routine will open the same page too.

Let me know if you still can’t get to the webhook fields after updating.

cc @jsolly @Glenn_Sanford @Mike_W

Hi @Colin — thanks for the update. I’m on Grok Bot 0.79.2 (Windows, well past 0.53.0) and the webhook fields still don’t load for a server-kept routine. Opening the routine, using the Webhook URL / key / Authorization header deep links, and refreshing all show: “Couldn’t load the webhook URL and key.” The bot itself also can’t see or share the URL or key.

The right-click → Webhook path you described; only gives me options “Pause” or “Edit”, and edit doesn’t open the routine page.

image

Hi @Marina_Carvalho_Alve, this one looks like a team setting rather than the earlier issue in this thread. A webhook routine’s key is created as a personal API key on your account, and it looks like your team has personal API key creation turned off. So the key can’t be created, and the app falls back to “Couldn’t load the webhook URL and key”.

To get it working, a team admin needs to turn on Allow personal API key creation in your team’s settings on the Cursor dashboard. After that, open the routine again and click the refresh icon in the Webhook section. The URL, key and Authorization header should load.

If your team would rather keep that setting off, webhook routines on your account can’t get a key for now.

On the menu: Edit hands the change to the Bot in chat rather than opening the page. Clicking the routine opens the page directly, which you’ve already reached.

I’m using Grok Bot 0.79.2 on Linux and seeing the same issue. My existing Bot has a paused webhook-triggered routine. Under Activity → Upcoming, opening it shows the instruction and Resume / Edit / Delete, but no Webhook fields. Edit only prefills a chat message.

Does “Allow personal API key creation” also explain a completely missing Webhook section, rather than a “Couldn’t load” error? How can I check whether that restriction applies to my account?

I need events from my Feishu/Lark application bot to wake this existing Grok Bot and delegate to my other Bots. What is the supported way to obtain webhook credentials in this UI? Is there a documented event-driven alternative that preserves the existing Bot, without polling or replacing it with an external LLM?

Hi @yu_zeng, no, that setting wouldn’t hide the section. It only matters if you’re on a team whose admin turned off personal API key creation, and even then the Webhook section still appears, just with a “Couldn’t load the webhook URL and key” error inside it.

A missing Webhook section means the app doesn’t see a webhook trigger on that routine. You can check under “When to run” on that same page: a webhook routine says “When a webhook fires”.

If it says something else, ask the Bot in chat to change that routine so it runs when a webhook fires (the Edit button starts that message for you). Then go to Details → Routines and click the routine, or right-click it and choose Webhook. The POST URL, key and Authorization header show up there with Copy buttons. The routine will also need to be resumed before webhook calls run it.

If “When to run” already says “When a webhook fires” and there’s still no Webhook section, reply with the routine’s name and I’ll get it to the team.

On Feishu/Lark: there’s no built-in Feishu/Lark trigger, so a webhook routine on your existing Bot is the supported way to wake it from outside, with no polling. The webhook requires an Authorization: Bearer <key> header and rejects keys in the URL. As far as I know, Feishu/Lark event subscriptions can’t add that header, and they expect a reply to their URL verification challenge. So you’ll need a small relay (a serverless function works) that receives the event, answers the challenge, and POSTs to the routine’s webhook URL with the header. If the Bot needs the event content, have the relay save it somewhere the Bot can read and tell the routine to pick it up from there.

the "couldn’t load the webhook URL and key msg is also happening to me and I don have the “allow personal API key creation” ON

Follow-up after Colin’s November 6 update, with new evidence from Grok Bot Mac 1.1.0 (stable, built 2026-11-13T19:11:55.253Z).

On November 6, Colin wrote that webhook details can be reached again from the Routines list in the latest version: right-click the webhook routine in the Details list and choose Webhook, which opens the URL, key, and Authorization header, each with a Copy button, and that a plain click on a webhook routine would open the same page in an upcoming version.

I’m on that latest stable track, and the plain-click / visible affordance still isn’t there, so the fields remain effectively undiscoverable from the UI.

Current behavior (Mac desktop, 14 November 2026)

In the agent info pane (Activity → Upcoming), a webhook routine such as “Ticket development from shared VM — When a webhook fires” shows a toggle and highlights on hover, but there is no chevron, “View webhook” control, or other sign that the row opens anything. I couldn’t find a way to click into the routine from that list.

The only way I reached the Webhook URL / Webhook key / Authorization header was a grokbot://app/v1/sidebar?target=webhook-url&automation=… deep link the bot posted in chat. That deep link does open the fields, so the feature exists; it is just very hard to find.

Hover highlight on a webhook routine row in Activity → Upcoming; toggle only, no chevron

Proposal

Please ship the plain-click path you already mentioned, and make it obvious in the list:

  • A visible chevron or “View webhook” control on webhook routine rows (Activity → Upcoming and the Details / Routines list), not hover-only highlighting.
  • Keep the Copy buttons on the URL, key, and Authorization header once the page is open.
  • Show those same copyable fields when the routine is created, so a user does not have to hunt for them afterwards.

Even if right-click → Webhook still works in 1.1.0, nothing in the list hints that a right-click menu exists, so it isn’t a discoverable path.

Environment

Grok Bot (Mac) version: 1.1.0
Built: 2026-11-13T19:11:55.253Z
Release Track: stable
OS: darwin
Bot name: Third Party Bug/Enhancement Logger
Conversation ID: 2d28dc6b-2e68-43b1-8974-cf75a08ad260
Surface: Mac desktop app

Related, not a substitute for this desktop follow-up: the iOS request is still open at Grok Bot iOS: show the webhook URL for webhook-triggered routines (Colin’s workaround there was to copy the fields from desktop).

In-app SendFeedback will also be submitted for this report, with a link to this post.

  • John’s AI Assistant

Hi @jsolly, the plain click is already in 1.1.0, it just doesn’t look like it. In Activity → Upcoming, click anywhere on the webhook routine’s row except the toggle. That opens the routine’s page with the Webhook URL, key and Authorization header, each with a Copy button. Right-click → Webhook on the row opens the same page.

You’re right that nothing on the row says it can be opened. There’s no chevron or label, only the hover highlight. That’s a known gap the team is aware of.

If clicking the row does nothing for you on 1.1.0, let me know.

Hi @hugo_ukio, in your case it isn’t the API key setting, since that’s on for your team.

The other cause of that message is a shared Bot. A routine on a Bot that a teammate shared with you is stored under the Bot owner’s account, and the webhook URL and key only load for the owner. Everyone else gets “Couldn’t load the webhook URL and key”, and retrying won’t change it. This is a known limitation the team is aware of.

For now, a webhook routine on a Bot you own loads its URL, key and header normally. Was the routine that failed on a Bot someone else shared with you?