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 user runs Claude Cowork on a headless machine, staging cloned documents so it can run the scripts and programs needed for work.
A user runs Claude Cowork on a headless machine, staging cloned documents so it can run the scripts and programs needed for work.
A commenter says they use Cowork with a headless machine dedicated to Claude, then let it run the work scripts and programs they need by cloning the documents into Cowork’s cloud session and staging them there. They describe steering that setup remotely from their phone, rather than keeping Claude running directly on the machine.
They say the setup has been seamless for extensive use and that they do not notice a meaningful difference from local mode. The thread gives no metrics or concrete failures for this specific workflow.
The main catch is that this depends on a separate headless Claude-only machine, with the actual documents cloned into the cloud session context.
In the folder [path to staged copies of my documents], run the script [script name or command] on each file and save the outputs in a new folder called [output folder]. Work only on these copies, and never touch the originals. When you finish, give me a list of the files processed, anything that failed, and why. Ask me before deleting or overwriting any file.
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.