Answer patient enquiries for a clinic by chat
An n8n and Gemini agent receives patient chat messages, keeps context, uses clinic info from Google Sheets and responds to enquiries.
A Claude Code system triages email at 5:30 AM, preps the calendar, updates tasks, adds drive-time events from traffic data and time-blocks the day.
A Claude Code system triages email at 5:30 AM, preps the calendar, updates tasks, adds drive-time events from traffic data and time-blocks the day.
The author runs Claude Code with MCP servers for Google Calendar, Gmail, Todoist and Google Maps (Directions API) for drive times. Scheduled tasks run email triage at 5:30 AM and calendar prep at 5:45 AM. In the morning, one command starts six parallel subagents, and a time-block workflow builds the day's schedule. Emails are sorted into Dispatch, Prep, Yours or Skip so the human stays in control.
The author says the task list and calendar, including traffic-based drive-time events, are current by 6:15 AM. The source gives no measured results beyond that. Most of the guide is paywalled.
The author puts the cost at about $100/month and suggests planning a weekend to build it. The full agent and command files are behind a paywall.
Build me an overnight chief-of-staff routine that runs at [time, e.g. 5:30 AM] each weekday. It should triage my email into [categories], prep my calendar for the day, update my task list at [path or app], add drive-time events using traffic from [home or work address], and propose a time-blocked schedule. Have it write a morning summary I can read in two minutes. It should never send emails or accept invitations without my approval, only draft them. Stop when a test run produces a full summary.
An n8n and Gemini agent receives patient chat messages, keeps context, uses clinic info from Google Sheets and responds to enquiries.
An n8n workflow has AI classify web-form jobs by type, urgency and summary, create an Airtable record, reply instantly and flag uncertain cases.
Lindy agents summarized meeting notes, sent action items to teammates, suggested knowledge-base replies on support tickets, and handled follow-up emails and calendar updates.