Hey @Dushant_Bhola, thanks for the suggestion!
Deep links only accept the parameters each link type defines, which is why a custom key like schedule_id gets rejected. A new prompt link is coming in an upcoming Grok Bot update that covers your use case. It opens a Bot with a message already typed into its composer, so you can put the ID in the message text:
grokbot://app/v1/prompt?id=&text=Look%20up%20schedule%2012345
There is also a web version that hands off to the app, which works well from a browser or email: Open in Grok Bot&text=…
A few details:
- The message is filled in but never sent automatically. The user reviews it and presses send.
- It only fills an empty composer, and the text must be a single line of up to 1,000 characters (URL-encoded).
- To get the Bot’s id, use “Copy link” from the Bot’s menu in the sidebar. The id is the last part of that link.
The link will work once your Grok Bot app is on the update that includes it, so keep an eye on upcoming releases.