Triage telehealth appointments with GPT-4o-mini, Telegram, Google Calendar

Quick overview This workflow collects telehealth appointment details via an n8n Form, uses OpenAI (GPT-4o-mini) to score no-show risk, then sends Telegram reminders and confirmations and updates Google Calendar based on the patient’s response, with Slack alerts on workflow errors.

How it works Receives a new appointment submission from an n8n Form with patient, appointment, and Telegram chat details. Sends the appointment data to OpenAI (GPT-4o-mini) to generate a 0–100 no-show risk score and explanation. Routes the flow based on the risk score, sending a single friendly Telegram reminder for low-risk patients. For high-risk patients, sends escalating Telegram reminders and a final message that waits for a confirmation or cancellation reply. If the patient cancels, creates a new “rescheduled” time slot in Google Calendar and sends the patient a Telegram reschedule acknowledgement. If the patient confirms, updates the existing Google Calendar event to note the confirmation and sends a Telegram confirmation message. If any step fails, posts an error notification to a Slack channel.

Setup Add credentials for OpenAI (Chat), Telegram Bot, Google Calendar OAuth2, and Slack OAuth2 used for error notifications. Update the n8n Form path/fields as needed and ensure patients provide a valid Telegram Chat ID for messaging. Replace the placeholder Google Calendar ID (for example, "your-calendar@example.com") and ensure your events have the correct Event ID available to update when confirming. Review and adjust the high-risk threshold (default score ≥ 70) and the wait duration for patient replies to match your operational process. Set the Slack channel target for error alerts and verify your workspace allows the app to post messages.

0
Downloads
1
Views
8.63
Quality Score
intermediate
Complexity
Author:Rahul Joshi(View Original →)
Created:7/2/2026
Updated:7/4/2026

🔒 Please log in to import templates to n8n and favorite templates

Workflow Visualization

Loading...

Preparing workflow renderer

Comments (0)

Login to post comments