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.
The poster built an agent that reads emails, checks calendar availability, replies with a meeting time and adds it to the calendar.
The poster built an agent that reads emails, checks calendar availability, replies with a meeting time and adds it to the calendar.
The poster built a background agent that scans their inbox for meeting requests, pulls the proposed date and time from the email, checks their calendar for conflicts, and either confirms the slot or suggests alternatives before blocking the time on the calendar. In comments, they said it uses limited permissions, no free-form actions, encrypted handling, and explicit authorization; for their use case it also accounts for in-person appointments, travel time, and distance between meetings.
They said they had used it for about a month and estimated it saved 3–4 hours a week of scheduling. The main shortcoming raised in the thread was trust: people were uneasy about giving inbox access, and the poster did not share a detailed technical implementation.
The clearest practical catch is that this only made sense for them because existing scheduling tools did not handle travel time between in-person appointments.
Build an agent that watches [email account] for meeting requests, checks my [calendar] for open slots in [working hours and time zone], and drafts a reply proposing a time. When the other person confirms, add the event to the calendar. Have it save replies as drafts for my approval before sending anything, and tell me when the setup is ready to test.
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.