Calendar, scheduling and sharing.
Check official pricing and availability. Model versions must be checked in each 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.
Work & OperationsInput: Gmail inbox + Google Calendar; Processing: 3-hour sweep, research, draft replies; Output: recommendations and drafts awaiting your one-tap approval
Read the case’s method and prerequisites
Requires a Grok Bot account and access to Gmail and Google Calendar. After connecting your Google account in Grok Bot, paste the main prompt as the first system instruction. The author recommends starting with one bot and splitting into additional bots only when duties clearly diverge.
Gmail · Google Calendar
Associated by case tags. Verify costs, permissions and actual results in the case.
Work & OperationsBuild a Telegram AI assistant in n8n that handles Gmail, Google Calendar, Google Sheets, and optional MCP tools via natural language
Read the case’s method and prerequisites
Based on an official n8n template: Telegram Trigger receives messages, an AI Agent (Gemini 2.0) interprets intent, and routes via MCP tools to Gmail, Google Calendar, or Google Sheets. Requires an n8n instance, Telegram Bot, Google account authorization, and a Google Sheet with Name/Email/Company/Role columns.
n8n · Gmail · Google Calendar · Google Sheets · Telegram
Associated by case tags. Verify costs, permissions and actual results in the case.
Life Admin & HomeManage calendar and email via natural-language WhatsApp messages, powered by Gemini
Read the case’s method and prerequisites
Prerequisites: n8n instance (self-hosted or cloud), Meta for Developers account (WhatsApp Business API), Google account (Workspace or Gmail), Google AI Studio API key. All credentials are stored securely in n8n. The Google Calendar nodes use a placeholder email [email protected] that must be replaced with a real calendar address.
n8n · WhatsApp · Gmail · Google Calendar · Gemini
Associated by case tags. Verify costs, permissions and actual results in the case.
Content & CreativeChat trigger → AI Agent collects patient info → checks Google Calendar availability → books appointment and logs to Google Sheets
Read the case’s method and prerequisites
Import the template into n8n, configure OpenAI API key and Google OAuth credentials, select the target Calendar and Sheets, fill in the AI Agent systemMessage, then test the chat flow. Requires an n8n instance and three credential types: openAiApi, googleCalendarOAuth2Api, googleSheetsOAuth2Api.
n8n · google-calendar · google-sheets
Associated by case tags. Verify costs, permissions and actual results in the case.
Sales, Marketing & SupportInput your customer needs → Sales Lead breaks down and assigns tasks to 4 specialists → Outputs customer research, meeting briefs, follow-up drafts, and pipeline reviews, all saved to shared folder for your approval
Read the case’s method and prerequisites
Prerequisites: a platform account supporting multi-Bot collaboration (e.g., Grok) where you can create 5 separate Bots; access or ability to connect Gmail, Calendar, Slack, Notion, and X; ability to create a shared folder at /workspace/shared/sales/ with sub-directory permissions. Cost: not specified by source; follow the actual billing of your platform and tools. Boundaries: all outbound sending, quoting, discounting, and contract terms require user confirmation; Bots do not accept or modify meeting invites; Bots do not set price floors.
Gmail · Slack · Notion · X · Google Calendar
Associated by case tags. Verify costs, permissions and actual results in the case.
Work & OperationsEmployee sends WhatsApp message → LLM classifies intent → routes to 5 specialized AI agents → auto-processes leave, attendance, FAQ, complaints, candidate shortlisting → replies via WhatsApp
Read the case’s method and prerequisites
Prerequisites: n8n instance; WhatsApp Business API credentials (Twilio or Meta); OpenAI API key; Google Sheets/Calendar/Gmail OAuth2; Supabase vector store. Costs: OpenAI per-token; WhatsApp Business API per-message; Google Workspace per subscription. Note: Google Sheets document IDs, Supabase table names, office geo-fence coordinates, and WhatsApp phone numbers in workflow.json are placeholders and must be replaced.
n8n · whatsapp · google-sheets · google-calendar · supabase
Associated by case tags. Verify costs, permissions and actual results in the case.
Content & CreativeInput your content request → lead breaks it down and assigns to research/script/distribution specialists → outputs schedule, drafts, multi-platform versions, and weekly analytics
Read the case’s method and prerequisites
Prerequisites: access to grok-bot; accounts for Gmail, Calendar, Notion, Slack, and/or X if you choose to connect them (recommended by source, not mandatory). Boundaries: this template provides role prompts and collaboration flow only; tool account setup is your responsibility. Any external send, payment, transaction, or delete action requires your confirmation. Routine task times are examples—adjust to your timezone.
Gmail · Google Calendar · Notion · Slack · X
Associated by case tags. Verify costs, permissions and actual results in the case.
Shopping & ErrandsInput: seller requests and store backend exports → Process: lead bot assigns tasks, four specialist bots execute, shared folder collaboration → Output: business briefings, product copy, competitor analysis, support tickets, and daily data reports
Read the case’s method and prerequisites
Prerequisites: a platform account supporting grok-bot with ability to create 5 bots; currently using or willing to connect Gmail, Calendar, Slack, Notion, and/or X. Input format: paste prompt text into each bot's description field; store backend data exported as CSV/spreadsheets into a designated shared folder. Required materials: 5 bot prompt files (lead.md / sourcing.md / copy.md / support.md / data.md). Cost conditions: unknown (depends on platform grok-bot pricing and tool API usage). Boundaries: bots must not modify store prices/inventory/listing status, must not make payments/ads/purchases, and must not reply to customers on the seller's behalf; any outbound send, payment, transaction, or delete action requires draft approval by the seller.
Gmail · Slack · Notion · X · Google Calendar
Associated by case tags. Verify costs, permissions and actual results in the 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 & 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: 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.
Life Admin & HomeInput staples list, 4-week order history, and next-week calendar → predict restock needs with price checks → output a priced basket (stops before checkout, hands to you)
Read the case’s method and prerequisites
Prerequisites: access to grok-bot; prepare four weeks of order history (item name, size, quantity, unit price, date), standing staples list, and next 7 days of Google Calendar. Frequency: run once per week on your agreed shopping day, in a fresh chat. Boundary: the assistant never places orders, never pays, never enters checkout. If the retailer supports cart-filling without a payment step, it will populate the cart; otherwise it outputs a paste-ready list. Use a dedicated shopping account for each retailer instead of your household primary account.
amazon · costco · google-calendar
Associated by case tags. Verify costs, permissions and actual results in the case.
Money, Bills & BenefitsInput read-only balances, transactions, holdings & calendar outflows → run protocol for cash runway, anomaly scan, portfolio drift & fee tally → output one-screen daily report with source attribution
Read the case’s method and prerequisites
Prerequisites: environment supporting grok-bot. Read-only access to Plaid (accounts), Yahoo Finance (holdings), and Google Calendar (scheduled outflows) is suggested but not configured in the source. Prepare account last-four digits, transaction IDs, tickers for source attribution. Cost: unspecified by source.
plaid · yahoo-finance · google-calendar
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.
