Grok Bot

Prerequisites: a grok-bot runtime with access to Amazon order history; a dedicated shopping login is suggested (source notes shared-session isolation risk). Input: user names a shopping day in chat. Boundary: the protocol explicitly prohibits placing orders, paying, entering card numbers, OTPs, or any second factor; if Amazon requests any of these, stop and hand off to the operator's own device. Cost conditions unknown.

amazon

Prerequisites: access to grok-bot (specific version and pricing not stated in source). Paste the full BOT.md text as a role/system prompt. For each monitoring task, provide: product specs, acceptable condition, max price (with currency), and allowlisted sites. The [amazon] integration tag is a suggested tool name only, not a pre-configured API connector or auto-polling mechanism; actual availability depends on grok-bot's live browsing capabilities.

amazon

Prerequisites: access to a staging environment with ability to create synthetic test data; grok-bot runtime available. Constraints: strictly prohibited from using production customer data, querying production databases, signing into real customer accounts, or copying real records into staging. Tool integrations (jira/github/sentry) are source-suggested labels only; actual connector configuration required separately. Cost conditions unknown.

jira · github · sentry

Prerequisites: read access to the target GitHub repository; know the branch name or use the default branch. Feed the full BOT.md text as a system/role prompt to grok-bot, then provide the repository and branch as a user message to trigger the audit. The source does not specify the invocation method (chat / API / built-in platform), so users must adapt accordingly. The audit is read-only: no PR creation, no push, no branch edits. Output is a Markdown report requiring human review before action.

github

Prerequisites: operator must provide the advertiser list to monitor; requires access to platform public ad libraries (Meta Ad Library, Google Ads Transparency, LinkedIn Ad Library, TikTok Ad Library); requires a maintained baseline sheet from the previous week for comparison. Tool status: slack and sheets are suggested integrations per source, not confirmed connectors; model version unspecified in source, listed only as grok-bot. Cost conditions: public ad libraries are free to access; costs for grok-bot API or third-party connectors unknown. Compliance boundary: read public library content only, no login, no ad clicks, no terms-violating scraping.

slack · google-sheets

Prerequisites: source deck URL, target country/language, local currency and date format, and approver name. If a Google Slides connector is available, operate directly; otherwise open in browser and note this in output. The source does not provide connector configuration details; verify access and permissions before use.

google-slides · sheets

Prerequisites: access to a grok-bot runtime; Zoom recordings stored in an accessible location (e.g., Google Drive); recordings must include a transcript, otherwise the recording is logged as missing transcript with zero moments extracted. Input is single-recording metadata (date, URL, duration, rep, account, transcript); output is a per-moment index row (date, account, rep, type, tag, start/end timestamp, deep link, quoted setup question, reuse score). Known limits: integrations are labeled suggestions, not configured connectors; grok-bot version unspecified; moments below score 3 or showing confidential content are marked "internal only, do not reuse"; prohibited from sending clips to prospects, publishing recording links outside the team, or deleting/trimming source recordings.

zoom · google-drive

Prerequisites: configure niche, page template schema (schema), entity queue, and allowlisted research sources. Runtime uses grok-bot; output saved to google-drive or designated folder. Cost conditions unknown. Hard boundary: auto-publish, deploy, domain purchase, sales emails, and public hosting links are prohibited.

google-drive

Prerequisites: access to a grok-bot runtime environment (such as xAI platform or compatible interface) and a Gmail account or equivalent email integration. Use this template as the system prompt for a security layer node placed before the mail-reading bot. The source does not provide specific connector configuration steps; you will need to configure mail intake and downstream action nodes according to your platform. Known limitation: this sentinel does not replace human final judgment; mail-triggered automations inherently carry financial and data exfiltration risks, and this solution only adds a second-look mechanism.

gmail

Prerequisites: Access to FeedHive (or equivalent content library), Notion (or equivalent draft storage), and a Slack workspace; grok-bot runtime configured. One-time initialization confirms accounts, library, success criteria, minimum age threshold (90 days), and banned topics. Then runs automatically every Friday. Known limits: tool names are source suggestions, not confirmed connectors; underlying model version unspecified; not tested by this site.

feedhive · notion · slack

Prerequisites: podcast transcript (self-sourced or via transcription service); need to build or configure internal bots (Shortform Scaler, Trial Reels, SEO/AEO bot) as source does not provide implementations; channel owners must be designated. Boundaries: specific model version, API costs, and platform permissions not stated; human approval is mandatory, not fully automated.

Platform: Grok Bot (X platform built-in automation bot). Prerequisites: you have created and run at least one routine that currently contains multi-line detailed instructions. Operations are performed in Grok Bot's skill and routine management UI; exact UI paths depend on the platform version. Cost: Grok Bot features are currently platform-built-in with no extra API fees (X subscription policies apply). Limitations: source did not disclose skill internal syntax or version control mechanics; back up the original routine text before migrating.

Prerequisites: grok-bot access; Gmail and Google Calendar accounts; a CRM account (to be logged in once inside the bot's browser). Cost: unknown, depends on grok-bot subscription tier and whether the Outbound Prospecting marketplace plugin incurs extra fees. Input format: text description of ideal customer profile (ICP) and historical best customers with purchase reasons. Boundaries: all external emails require human review by default; bots run in the cloud without your laptop being on.

Prerequisites: a registered domain you can manage, with DNS on Cloudflare. You need your Grok Bot email address (usually provided by the platform). Cloudflare Email Routing may be free on certain plans; verify current terms with Cloudflare. This site has not tested the workflow; steps below are reconstructed from the author's experience report.

cloudflare

Prerequisites: Grok Bot account with quota system (billed by actual work done, not message count); existing multi-bot team environment. Boundaries: Specific quota numbers and model version not stated in source; 'shared memory' implementation unspecified; results are author estimates, unverified.