Google’s email service.
Check official pricing and availability. Model versions must be checked in each case.
Work & OperationsInput: business needs and client materials → Process: 1 lead bot dispatches to 3 specialists (BD, delivery, billing) → Output: deliverables, lead lists, invoice tracking, and decision summaries
Read the case’s method and prerequisites
Prerequisites: account permissions to create multiple bots; already using or planning to use some of Gmail, Calendar, Notion, Slack, X; access to a shared filesystem at /workspace/shared/. Cost conditions: unknown (depends on platform and tool subscriptions). Not tested by this site; verify yourself.
Gmail · Google Calendar · Notion · Slack · X
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportInput: teammate-specified topic + audience; Process: search Google Drive, Zoom recordings, Gmail threads and rank by recency; Output: structured internal enablement draft document with link
Read the case’s method and prerequisites
Prerequisites: access to grok-bot, plus read permissions for Google Drive, Gmail, and Zoom (listed as suggested integrations in source; actual connectors require manual configuration). Input format: send the bot a topic name and audience description. Cost: unknown. Boundary: internal use only; never send to customers or set to public link. If fewer than 3 usable sources are found, report gaps explicitly instead of padding.
gmail · zoom · google-drive
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportScan email and CRM for meeting commitments → cross-check calendar for unbooked, no-show, and stalled reschedules → output a priority follow-up list sorted by deal amount
Read the case’s method and prerequisites
Prerequisites: readable Gmail/email threads, Google Calendar access, HubSpot CRM read permissions, and a grok-bot runtime. Input is 21 days of external communication threads and calendar events; processing includes commitment detection, calendar cross-check, event classification, and stall detection; output is a structured text report. Source does not provide specific API configuration, OAuth flows, HubSpot field mappings, or scheduling setup details. The bot is read-only: no emails sent, no calendar events created/modified/cancelled—all booking actions require human execution.
hubspot · google-calendar · gmail
Associated by case tags. Verify costs, permissions and actual results in the case.
Life Admin & HomeInput: specify mailbox and time range → Process: search by sender groups and flag sensitive mail → Output: line-by-line approval cleanup proposal with samples
Read the case’s method and prerequisites
Start a new dedicated chat with grok-bot and paste the BOT.md role protocol as system prompt or first message. Requires web access to the target Gmail account; without an API connector, manually type search strings into the Gmail web client and feed result counts back to the model. Default scope is everything older than 12 months; one account per run. The model never auto-deletes, empties trash, unsubscribes, or asks for passwords/2FA codes.
gmail
Associated by case tags. Verify costs, permissions and actual results in the case.
Money, Bills & BenefitsInput written expense policy and week's transactions → pull receipts from Gmail and Drive → output match report, policy exceptions, and human-reviewed chase drafts
Read the case’s method and prerequisites
Prerequisites: grok-bot access; read permissions for Gmail, Google Drive, and Google Sheets; written expense policy with limits and categories (not a summary). This template is a role protocol—configure the BOT.md content as a system prompt or conversation starter. Tool integrations are labeled suggestions; actual connector setup (OAuth/API) is not provided and must be done separately. Output goes to a document draft requiring human review before sending.
gmail · google-drive · google-sheets
Associated by case tags. Verify costs, permissions and actual results in the case.
Life Admin & HomeInput: Flight confirmation emails in Gmail → Process: Extract bookings, de-duplicate, compute check-in open time, build prep checklist → Output: Per-flight structured prep pack with three-stage reminders
Read the case’s method and prerequisites
Prerequisites: a grok-bot runtime environment with authorized access to Gmail (to read flight confirmation emails) and Google Calendar (to write reminders). Input is flight confirmation, itinerary, e-ticket, or schedule-change emails in your inbox, which must contain a six-character record locator (PNR). The bot runs twice daily, morning and evening. Cost conditions are unknown and depend on grok-bot runtime and mail/calendar API billing. Known limitations: the bot only organizes information and sends reminders; it does not perform any booking changes. If it cannot confirm check-in open time from airline rules, it states so rather than assuming 24 hours. It does not guess passport, visa, seat, or baggage details.
gmail · google-calendar
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportRead open deals for this quarter and next → match against calls, emails, and internal messages → flag slipping/silent/blind patterns and draft owner-reviewed notes
Read the case’s method and prerequisites
Prerequisites: Salesforce read access (opportunity fields, close-date history), Gong/Granola call and meeting-note access, Gmail read access (filtered by account domain), and Slack internal channel read permissions. Runtime is grok-bot. Recommended schedule: weekday evenings and two hours before weekly pipeline review. Source does not specify API versions or connector configuration; verify OAuth scopes for each system before production use.
salesforce · granola · gong · slack · gmail
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportInput Gmail inbox → filter by budget tier and brand fit → output ranked shortlist and log to Google Sheets
Read the case’s method and prerequisites
Prerequisites: accessible Gmail inbox and Google Sheets edit permissions; grok-bot runtime environment configured by the operator (specific version not stated in source). Source integrations tag [gmail, sheets] is a suggested tool list, not a pre-configured connector. Cost conditions unknown. Schedule: every weekday at 08:00, scanning the previous 24 hours.
gmail · google-sheets
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportInput Gmail negotiation thread + Google Sheets historical deals → agent rebuilds deal state, extracts sponsor intelligence, prices from your own records, builds concession ladder → outputs one-page strategy brief for human send-off
Read the case’s method and prerequisites
Prerequisites: access to grok-bot runtime; a complete Gmail email thread with one sponsor; a Google Sheets deal history (including charged amount, deliverables, and post-campaign reports). This template is a role protocol—paste it into the agent's system/role field. Boundary constraint: the agent never replies directly to sponsors and never commits to any rate; all output is for operator review before human send-off.
gmail · google-sheets
Associated by case tags. Verify costs, permissions and actual results in the case.
Content & CreativeInput pending topics from Google Sheets → AI generates SEO blog posts → email human approval → revise based on feedback or archive
Read the case’s method and prerequisites
Prerequisites: n8n instance; OpenAI API key; Google Sheets OAuth2 credentials; Gmail OAuth2 credentials. Copy the author's Google Sheet template (requires Topic List and Generated Content sheets). Adjust the Schedule Trigger interval as needed. Replace the default recipient email in the approval node with your own. Costs depend on OpenAI token usage and n8n hosting.
n8n · Google Sheets · Gmail
Associated by case tags. Verify costs, permissions and actual results in the case.
Work & OperationsConfigure any mail-reading bot as a safety sentinel → scan for injection attack patterns → block high-risk actions and await human confirmation
Read the case’s method and prerequisites
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
Associated by case tags. Verify costs, permissions and actual results in the case.
Money, Bills & BenefitsScheduled Google Sheets wallet loader → Moralis on-chain data via API → GPT-4o-generated readable summary → simultaneous Telegram and Gmail delivery
Read the case’s method and prerequisites
Prerequisites: self-hosted or cloud n8n instance; Moralis account and API Key; OpenAI API Key; Telegram Bot and Chat ID; Gmail OAuth2 authorization; Google Sheets OAuth2 authorization. Costs: Moralis and OpenAI API are usage-based; self-hosted n8n has no platform fee. Input: Google Sheets with a `wallet_address` column. Output: Telegram text message + Gmail HTML email.
n8n · telegram · gmail · google-sheets
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportInput a search query → AI Agents analyze websites and LinkedIn → output structured lead sheet
Read the case’s method and prerequisites
Requires an n8n instance; configure credentials for Serper.dev, ScraperAPI, Google Gemini, plus Google Sheets OAuth2 and Gmail OAuth2. Set search_query in the Edit Fields node. Create a Google Sheet with the specified headers. Costs depend on third-party usage.
n8n · Serper · ScraperAPI · Google Sheets · Gmail
Associated by case tags. Verify costs, permissions and actual results in the case.
Life Admin & HomeStrava activity trigger → data flattening → Gemini AI analysis → structured output → HTML email / WhatsApp delivery
Read the case’s method and prerequisites
Prerequisites: accessible n8n instance; Strava developer account with OAuth2 credentials; Google Gemini (PaLM) API credentials; Gmail OAuth2 or SMTP credentials; optional WhatsApp Business Cloud credentials. The flow is triggered by a Strava activity update webhook, preprocesses and flattens data, sends it to a Gemini AI Agent for analysis, then delivers results via email or WhatsApp. This site has not tested the flow; verify credentials and webhook reachability in a test environment before relying on it.
n8n · strava · gmail · whatsapp
Associated by case tags. Verify costs, permissions and actual results in the case.
Content & CreativeInput Google Calendar events → parse attendees, retrieve email context, AI-generate summary → output HTML email brief
Read the case’s method and prerequisites
Prerequisites: n8n instance (self-hosted or cloud), Google Calendar and Gmail OAuth2 credentials, OpenRouter API key. This template uses 14 nodes and relies on OpenRouter for GPT-4o (or Claude 3.7). All node parameters in workflow.json are empty objects; the workflow cannot run immediately after import and must be configured node-by-node in the n8n UI. Not tested by this site.
n8n · gmail · google-calendar
Associated by case tags. Verify costs, permissions and actual results in the case.
