A platform for code hosting, collaboration and development workflows.
Check official pricing and availability. Model versions must be checked in each case.
Software & DevOpsWalks your product every weekday in its own test account and reports what shipped, unshipped, and broke—with repro steps and screenshots.
Read the case’s method and prerequisites
Import / Add to Grok from the official marketplace page, then chat. Author feature claims are from the page, not a site verification. Software integrations listed on the page are mapped into tools[] per t652u (AgentMail, GitHub, Linear); you still authorize connectors inside Grok Bot. Full rules are not public; we have not tested this ourselves.
Grok Bot; page public_integrations.names mapped into tools[]: AgentMail, GitHub, Linear
Associated by case tags. Verify costs, permissions and actual results in the case.
Life Admin & HomeConnect Muse (Meta AI agent) to Google Calendar, GitHub, and other services; set up scheduled tasks and permission boundaries to automate daily summaries, information monitoring, content co-creation, and code review.
Read the case’s method and prerequisites
Requires a Muse account (Meta-provided; available in Japan since 2026-10-23). Use via Web or mobile app. External services (Google Calendar, GitHub, Google Drive, etc.) must be connected with appropriate permissions. Author reports current free usage; exact limits unknown. Privacy setup recommended at start: turn off AI learning toggle in Data Controls, and set sensitive actions to ask-each-time instead of always-allow.
Muse · Google Calendar · GitHub · Google Sheets
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsInput: existing Next.js password-protected prototype + Grok Bot (AI agent with its own computer); Process: phased audit, multi-round PR iteration, infrastructure migration; Output: public time-zone conversion site, Chrome extension, launch assets
Read the case’s method and prerequisites
Requires Cursor account with Grok Bot access; existing code repo (GitHub) and deployment account (Vercel). Optional: Claude Code token, Cloudflare, Pabbly, Google Analytics/GTM. Cost reference (author-reported, not tested by us): Grok Bot Super $100/mo, Claude Max $100/mo, Vercel Pro $20/mo, Chrome Web Store developer fee $5 one-time, ElevenLabs Starter ~$6/mo, Higgsfield ~$23/mo.
Vercel · GitHub · Cloudflare · Google Analytics · Pabbly
Associated by case tags. Verify costs, permissions and actual results in the case.
Work & OperationsInput: scattered Grok Bot tasks and external service permissions → Process: reorganize bots into dedicated roles, unify records in Notion, let bots hand off directly → Output: a bot team that runs on ~2 hours/day of human approval
Read the case’s method and prerequisites
Prerequisites: Grok Bot accounts, a Notion workspace, and per-bot access to required services (e.g., Gmail, GitHub, Buffer). Cost conditions are unknown. Core method: one job per bot with its own chat, written job description, and memory; Notion as the single source of work record; bots can message each other for handoffs; all outbound actions require human approval.
Notion · Gmail · GitHub · Buffer
Associated by case tags. Verify costs, permissions and actual results in the case.
Work & OperationsClaim a dedicated bot email, enable native X search and monitoring, receive tasks via @bot, hand off coding to Cursor cloud agents, and run a specialist bot team led by a primary bot
Read the case’s method and prerequisites
Requires the Grok Bot desktop app (updated to the inbox-enabled version), an active Grok Bot or Cursor subscription (which includes Grok Bot access), a GitHub account (for code agents), and an X account (for search and @bot tagging). Team plans require an admin to enable inboxes first. Some features are restricted for EU/UK/Australia users and Cursor-subscription channels.
Cursor · GitHub · X · Slack · Notion
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsNatural language description → Claude Sonnet calls SubmitRax MCP to generate form HTML → auto-publish to GitHub Pages and return a live link
Read the case’s method and prerequisites
Import this template into n8n, configure SubmitRax Bearer Token, Anthropic API Key, GitHub PAT, and repository details, then enable the Chat Trigger to generate and host forms through natural language conversation.
n8n · GitHub
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsAfter CI deploy → Webhook trigger → wait for render stability → Snapshot Site screenshot compare → Slack alert and GitHub Issue on mismatch
Read the case’s method and prerequisites
Prerequisites: accessible n8n instance; Snapshot Site API credential; Slack workspace credential; GitHub personal access token with repo scope. Input: CI pipeline POSTs url, baselineUrl, optional commit and environment. Boundaries: url and baselineUrl must be full https URLs; Snapshot Site returns soft errors for bare domains (HTTP 200 + {error: true}); Wait defaults to 45s, typical range 30–60s; mismatch threshold defaults to 10%, adjustable per site rendering variability. Cost: Snapshot Site API billed per call; see official pricing.
n8n · slack · github · snapshot-site
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsScheduled trigger → parallel Jira and GitHub fetch → OpenAI summary → Slack Block Kit post → optional Google Sheets log
Read the case’s method and prerequisites
Prerequisites: n8n instance; credentials for Jira Cloud, GitHub, OpenAI, and Slack; Google Sheets credential only if logging is enabled. Requires access to the Jira project, GitHub repo read scope (fine-grained token needs repo + pull-request read), and Slack channel post permission. Uses gpt-4o-mini with temperature 0.2 and maxTokens 2000.
n8n · google-sheets · github · slack
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsGitHub Webhook → GPT-4o severity & category analysis → Jira ticket creation → parallel Slack/Discord/GitHub notifications
Read the case’s method and prerequisites
Prerequisites: n8n instance; GitHub repo admin access; Jira Software Cloud with API token; OpenAI API key with GPT-4o access; Slack workspace or Discord server (optional). Customization required: developer email mappings, JIRA_PROJECT_KEY, Slack channel name, Discord webhook URL, Jira domain.
n8n · webhook · code · openai · github · slack
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsNew GitHub Issue → AI analysis → parallel outputs to spreadsheet, tasks, notifications, and labels
Read the case’s method and prerequisites
Import the template workflow into n8n, configure credentials for GitHub, OpenAI, Slack, Gmail, ClickUp, and Google Sheets, specify the target repository and notification channels, then activate. Requires an n8n instance and API or OAuth credentials for the listed services.
n8n · github · google-sheets · clickup · slack · gmail
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsGitHub Webhook trigger → fetch changed files and diffs → extract and structure code changes → score and categorize → route by severity → post review to GitHub PR → store in PostgreSQL → Slack notification
Read the case’s method and prerequisites
Import the n8n template. Prerequisites: n8n instance (self-hosted preferred for webhooks), GitHub repo admin access (webhook + PAT), PostgreSQL database, Slack webhook URL. Credentials required: githubApi, postgres. The AI review node in workflow.json is a Code-node placeholder (scoring logic); actual LLM call must be wired per template instructions.
n8n · GitHub · PostgreSQL · Slack
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsListen for new GitHub issues → AI classification (type/priority/labels) → Create Linear task and post GitHub comment
Read the case’s method and prerequisites
Requires an n8n instance; configure GitHub credentials (webhook trigger and comment permissions), OpenAI credentials (gpt-4.1-mini, etc.), and Linear credentials (replace teamId with actual value). GitHub owner/repository fields are empty in the template and must be filled with the target repository.
n8n · github · linear
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsGitHub PR trigger → AI Agent calls tools (plan / security scan / cost estimate / standards search) → structured review → Postgres archive + PR comment → auto-approve or Slack human review
Read the case’s method and prerequisites
Prerequisites: n8n instance (self-hosted or enterprise recommended), GitHub repository admin access (repo scope + PR read/write), OpenAI API key, Postgres database, Slack workspace admin access, optional vector store (for RAG retrieval of internal IaC standards) and CI endpoints (terraform plan / security scan / cost estimate). Costs depend on OpenAI model usage and n8n execution volume.
n8n · github · openai · memory · ai-agent · slack
Associated by case tags. Verify costs, permissions and actual results in the case.
Work & OperationsInput: shared /workspace with ops boundaries → Process: weekday cadence inventory, archive, backup, collision flagging → Output: live registry + weekly org review
Read the case’s method and prerequisites
Prerequisites: xAI Grok Bot account (one persistent cloud computer per account), GitHub private repo access. Input form: paste BOT.md role protocol as system prompt. Required materials: read/write access to /workspace, operator-named registry file, allowlisted backup directories, custom retention days (default 14). Cost: unknown. Boundaries: never delete another bot's working tree without operator-approved named archive step; never commit secrets including .env, *.pem, cookies, private keys; screens are not a security boundary.
github
Associated by case tags. Verify costs, permissions and actual results in the case.
Software & DevOpsInput vague bug report with screenshot → separate stated facts from assumptions, record precise environment, reproduce step-by-step on staging with synthetic data → output reproducible pack with evidence or non-reproducible finding
Read the case’s method and prerequisites
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
Associated by case tags. Verify costs, permissions and actual results in the case.
