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 Make.com scenario sends a daily email digest from ClickUp to stakeholders without ClickUp accounts, and adds contacts to a selected action item.
A Make.com scenario sends a daily email digest from ClickUp to stakeholders without ClickUp accounts, and adds contacts to a selected action item.
They set up ClickUp with a master action-item list plus related project and contact lists, rolling stakeholder emails into each task and auto-adding the right contacts when a project is chosen. In Make, the intended flow was a 6 AM scheduled run that lists incomplete tasks, iterates them, groups them by project in a Text Aggregator, and sends one email digest to that project’s stakeholder email field; the person manually tested the outputs and email format.
The first version failed because the Text Aggregator was pulling whole ClickUp objects, so the email came out as JSON instead of task fields. Commenters said the fix was mapping individual fields and grouping by project name; no finished result or performance numbers were reported.
A practical catch from the thread: test by writing the generated subject, recipients, and body to Google Sheets or a Make data store before turning on live email sends.
Build a scenario that runs every day at [time] and pulls tasks from my ClickUp [space or list] that are [due soon, changed, or blocked]. Format them into a clean email digest and send it to [stakeholder emails] who don't have ClickUp accounts. Send a test digest to me first and don't send it to stakeholders until I approve.
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.