Grok Bot × Shortcuts: send shared links to a traceable knowledge inbox

Submit shared links with a request identity and distinguish accepted, read, organized and stored states.

The source describes webhook routines, the iOS Get Contents of URL action and a text-input alternative. This guide adds identity and receipt checks; the two phone recordings are reviewed in the supplement below.

Verification status

Source reading and media coverage are listed below. This site has not executed the live workflow. Fixtures, fields and prompts here are independent exercises, not the author’s results.

EXECUTION & TAKEOVER

Execution and takeover boundaries

The actions below require the agreed inputs, accounts and scope. Configuring a Routine does not expand that authorization.

Can run automatically

Validate links, request ids and output fields on synthetic inputs; prepare source records and short summaries, separating acceptance from completion.

Requires confirmation

Confirm Webhook Routine creation, Shortcut or credential configuration, real requests and test or production knowledge-base writes.

Take over after a failure

When HTTP 200 has no artifact, inspect Bot state and files by the same request id. Mark unread sources as failed for user handling without duplicate entries or key exposure.

Scenario and input

Synthetic input: request_id=KB-001, source_url=https://example.com, kind=link.

1. Define the stored artifact

Choose a test destination and required metadata: short summary, original link, author and actual reading scope.

2. Draft the trigger

Have the responsible routine accept JSON and verify its POST URL and Bearer header without publishing credentials.

3. Configure the phone sender

Use Get Contents of URL with POST, a JSON body and authorization header. Accept a shared URL or a separate text-input menu.

4. Separate acceptance and completion

Treat HTTP 200 as acceptance, then inspect source reading, output path and failures in the Bot’s result. State video and image coverage explicitly.

5. Retest edge cases

Test a normal URL, a duplicate identity and an inaccessible URL before using the real knowledge destination.

A synthetic acceptance fixture

inbox.csv: request_id, source_url, read_status, stored_path, error. Replaying KB-001 creates no duplicate; inaccessible sources retain their failure reason.

Copyable task brief

Copy template

Use the synthetic fixture to prepare the deliverable for Grok Bot × Shortcuts: send shared links to a traceable knowledge inbox. Do not connect real services yet.
Input: Synthetic input: request_id=KB-001, source_url=https://example.com, kind=link.
Requirements:
1. Choose a test destination and required metadata: short summary, original link, author and actual reading scope.
2. Have the responsible routine accept JSON and verify its POST URL and Bearer header without publishing credentials.
3. Use Get Contents of URL with POST, a JSON body and authorization header. Accept a shared URL or a separate text-input menu.
4. Treat HTTP 200 as acceptance, then inspect source reading, output path and failures in the Bot's result. State video and image coverage explicitly.
5. Test a normal URL, a duplicate identity and an inaccessible URL before using the real knowledge destination.
Return itemized records, evidence locations, unknowns and next steps, marking unperformed actions explicitly.
Do not install tools, change access, purchase, publish, create Bots or schedule work in this pass.

Acceptance and review

Duplicates do not multiply entries, failures remain traceable, unread sources have no invented summary, and completion includes a path.

Copy template

Review the artifacts without taking external actions.
Acceptance: Duplicates do not multiply entries, failures remain traceable, unread sources have no invented summary, and completion includes a path.
Separate pass, fail, untested and evidence; distinguish synthetic fixtures from live results.
Stop on missing sources, permissions or uncertain outcomes and list the required evidence.
Propose one next step with a recovery plan and wait for confirmation.

Video supplement: two phone entry points and completion states

The two recordings clarify where the existing Shortcuts are used on a phone. They do not add a knowledge-base architecture. Both show submission from the phone, with no final storage receipt.

Video one: Douyin share sheet (12.23 seconds)

1. Tap Share on the content page (00:00–00:03).
2. Choose More to open the system share sheet (00:03–00:06).
3. Select the Shortcut named “Send to knowledge Bot” in the recording (00:06–00:07).
4. Return to playback (00:07–00:12), then check the request and artifact in the Bot chat separately. Returning to the app does not establish successful storage.

This adds entry-point detail to a11-m02. The audio belongs to the third-party video being shared, not to a Grok Bot tutorial. Automatic recognition covered the full track; that work is not transcribed here.

Video two: copy a WeChat link and enter it (16.97 seconds)

1. Copy the article link from its top-right menu and check the copied confirmation (00:00–00:04).
2. Invoke Shortcuts and choose the knowledge-inbox action (00:04–00:06).
3. Paste the URL into the link prompt (00:06–00:12).
4. Submit and return to reading (00:12–00:17); check source-reading status, summary and output path in the Bot separately.

This expands a11-m03. The recording does not establish whether an Action button or another entry point invoked the Shortcut. Action-button configuration is therefore not a verified prerequisite. Full-track analysis found digital silence.

Add these to the acceptance run

Submit the same synthetic test link through both paths, recording entry=share_sheet or entry=manual_link, a request identifier and response time. Retain the existing request_id deduplication rule. Record server-side acceptance, source reading and storage separately: an HTTP 200 means accepted and started under the official routine guidance. A phone demonstration does not prove server-side processing, deduplication or writing completed.

Video verification scope

Both recordings were sampled at approximately one frame per second, including their ends. The largest viewed-frame gaps were 1.23 seconds and one second; this was not continuous viewing. The first recording’s share-menu scroll at 00:03.4–00:06.5 was not inspected frame by frame. The second recording’s invocation mechanism remains unknown. Full audio tracks underwent automatic recognition and loudness analysis, without human listening. The Shortcuts were not rerun and the shared third-party works were not read.

Author follow-up: multiple Webhook purposes for one Bot

The author reply read by the collector says one Bot can receive multiple Webhooks with different instructions. This supplements input organization, without supplying all Shortcut actions or a completed storage receipt. It does not identify the exact phone invocation mechanism.

Use that statement to refine the site’s acceptance table:

1. List input types and processing instructions, such as link summaries or text notes, then map each to an entry point rather than treating all requests as one content type.
2. Check each entry’s Routine, request fields and destination. Whether using the source image’s info field or the site’s practice fields request_id and source_url, update the receiving parser as well as the phone request body.
3. Use one synthetic item to check routing, deduplication and completion receipts through each entry. An additional entry does not establish successful reading, processing or storage.

These are site-written configuration and acceptance suggestions based on an author statement, without a live Webhook run. A separately mentioned SDK or browser extension does not replace the phone Shortcut. Complete, attributable installation and storage materials were not obtained in this round.

Sources and applicability

Original article: @cgnot996; published 2026-09-09.

Index-to-source mapping: strong content match.

The collector reports viewing 12 images and reviewing 2 video(s) through sampled frames, without continuous playback. The screenshot uses info for Shortcut Input. If adopting the request_id/source_url fixture, update the routine parser to match. The images also show stored paths and receipts.

Prices, interfaces and menus change. Check unresolved conditions against the actual account and current official documentation.

See the rewrite and verification map for all 24 sources

Verification record

Content updated: 2026-10-18 · Editing a page does not reverify its sources or live workflow.

Documentation review: Historical review record · 2026-10-18
Preserves this page’s existing source-review record. Its source notes state actual text, image, video or code coverage and unavailable material. This integration did not recheck external sources or establish a live workflow pass.

Live workflow verification: Unverified
This site has not executed the live accounts, bridges, external writes or scheduled workflow. Author demonstrations, synthetic fixtures and page checkboxes do not establish this site’s live verification.