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 guide sets up a Codex automation that reads project files on a schedule and emails a weekly summary via the Gmail plugin.
A guide sets up a Codex automation that reads project files on a schedule and emails a weekly summary via the Gmail plugin.
The guide has you install the Gmail plugin through OAuth and send a test email. You then create an automation attached to a local project folder. Its prompt tells Codex to summarize the files and send the result with @Gmail. The demo used a folder of two transcript files, medium reasoning, a Sunday 9 a.m. schedule and full-access permissions so it runs unattended.
The source says setup takes under ten minutes and then runs with no further input. It gives no measured results from real runs, only troubleshooting for failures such as expired OAuth, approval pauses and a missing @Gmail mention.
Automations use tokens on every run, so check your usage first. Large folders or high reasoning drain credits quickly, and full access is needed for unattended runs.
Create a scheduled automation that runs every [day and time], reads the files in [project folder], and writes a short weekly summary of progress, open issues, and next steps. Email it to [recipient address] using my Gmail plugin. Before the first send, show me the draft and the schedule so I can approve them.
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.