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 developer fixed OpenClaw cron jobs that ran without delivering by turning thinking mode off, after which six articles reached Telegram in 30 seconds.
A developer fixed OpenClaw cron jobs that ran without delivering by turning thinking mode off, after which six articles reached Telegram in 30 seconds.
The cron job scanned RSS feeds, filtered articles and wrote a digest. A separate announce agent then forwarded the digest to Telegram. With thinking on, the model did all its work inside the thinking block, so the summary was empty and nothing was sent. The developer set thinking to off in the heartbeat config, using DeepSeek Chat as the heartbeat/cron model, and added isolated sessions.
With thinking enabled, jobs averaged 88 seconds and delivered nothing across five test runs. With thinking off, the same job took 30 seconds and delivered six articles to Telegram on the first attempt.
The delivered:true status only means the announce agent ran without error, so confirm in Telegram. A daily digest cost about $0.03/day on OpenRouter.
My scheduled job that sends [N] article digests to [Telegram] at [time] runs but nothing arrives. Check the cron job settings and logs, find why delivery fails (try turning thinking mode off), and fix it. Finish by running it once so the digest actually shows up in Telegram, and ask before changing other jobs.
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.