Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Quick Overview This workflow uses Google Sheets, OpenAI, Telegram, and Slack to send post therapy check in messages, analyze patient replies for sentiment and risk, alert therapists to at risk resp...

Best for

Ticket Management automation workflows
AI Chatbot automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.googlesheets, @n8n/n8n-nodes-langchain.openai, n8n-nodes-base.telegram, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.slack

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Rahul Joshi.

Original n8n.io source

1.1 Workflow description

Title: Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets
Workflow name: Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets

Quick Overview

This workflow uses Google Sheets, OpenAI, Telegram, and Slack to send post-therapy check-in messages, analyze patient replies for sentiment and risk, alert therapists to at-risk responses, and log non-urgent replies for ongoing wellness tracking.

How it works

Runs every hour on a schedule trigger.
Reads session records from Google Sheets and keeps only sessions that have a session date and have not been marked as check-in sent.
Uses OpenAI (gpt-4o-mini) to generate a personalized, non-clinical Telegram check-in message from the patient’s session details.
Sends the check-in to the patient via Telegram and updates the Google Sheets session row to store the message and mark the check-in as sent.
Triggers on incoming Telegram messages, looks up the patient in a Google Sheets master list by Telegram ID, and selects the most relevant recent session to provide context.
Sends the patient reply and session context to OpenAI for JSON-formatted sentiment classification and parses the result into structured fields.
If the sentiment is classified as at-risk, posts an urgent alert to a Slack channel; otherwise, appends the reply and sentiment details to a Google Sheets wellness log.

Setup

Connect Google Sheets OAuth credentials and update the spreadsheet document ID and sheet names for Sessions, Patients_Master, and Wellness_Log.
Create and connect a Telegram bot credential, set up the Telegram trigger webhook, and ensure patient Telegram chat IDs are stored in Google Sheets.
Add an OpenAI API key credential and confirm the selected model (gpt-4o-mini) meets your requirements.
Connect Slack OAuth credentials and replace the placeholder Slack channel ID used for therapist alerts, and confirm the error-alert channel is set correctly.
Verify your Google Sheets columns match the workflow’s expected fields (for example session_id, checkin_sent, checkin_message_sent, therapist_slack_id) before activating.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Overview

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 2 - Section: AI Check-In Generation

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 3 - Section: Patient Reply Capture

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 4 - Section: Sentiment Analysis

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 5 - Section: Escalation & Logging

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 6 - Credentials & Security

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 7 - Schedule Trigger (Every Hour)

Type / Role: n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices: Version 1.1

Block 8 - Read Completed Sessions

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.2

Block 9 - AI: Generate Personalised Check-In Message

Type / Role: @n8n/n8n-nodes-langchain.openAi - openAi
Config choices: Version 1.4

Block 10 - Telegram: Send Check-In to Patient

Type / Role: n8n-nodes-base.telegram - telegram
Config choices: Version 1.2

Block 11 - Sheets: Mark Check-In Sent

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.2

Block 12 - Code: Parse Sentiment JSON

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 13 - IF: At-Risk Detected?

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2

Block 14 - Slack: Alert Therapist (Human-in-Loop)

Type / Role: n8n-nodes-base.slack - slack
Config choices: Version 2.2

Block 15 - Sheets: Append to Wellness Log

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.2

Block 16 - Filter: Due for Check-In (24h passed)1

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2

Block 17 - Merge

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 18 - Read Completed Sessions (Reply Branch)

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.2

Block 19 - AI: Sentiment Analysis on Reply

Type / Role: @n8n/n8n-nodes-langchain.openAi - openAi
Config choices: Version 1.4

Block 20 - Sheets: Lookup Patient by Telegram ID

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.2

Block 21 - Telegram Trigger: Capture Patient Reply

Type / Role: n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices: Version 1.1

Block 22 - Code: Parse Merge Output

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 23 - Section: Trigger & Filter

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - On Workflow Error

Type / Role: n8n-nodes-base.errorTrigger - errorTrigger
Config choices: Version 1

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets
Complexity	advanced
Nodes	26
Categories	Ticket Management, AI Chatbot
Author	Rahul Joshi
Published	16 Jun 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/16428/16428.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Ticket Management workflows AI Chatbot workflows

Frequently asked questions

What does Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management, AI Chatbot use case.

Rahul Joshi

269 workflows

Nodes

n8n-nodes-base.stickynote n8n-nodes-base.scheduletrigger n8n-nodes-base.googlesheets @n8n/n8n-nodes-langchain.openai n8n-nodes-base.telegram n8n-nodes-base.code n8n-nodes-base.if n8n-nodes-base.slack

Complexity

advanced

Published 16 Jun 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/16428/16428.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Detect and route customer escalations with Claude, Slack and Linear

## Quick Overview This workflow receives support messages via a webhook, normalizes payloads from Gmail, Zendesk, Intercom, and HelpScout, and uses Anthropic Claude to detect escalation signals and severity, then posts alerts to Slack and creates Linear tickets for actionable cases. ## How it works 1. Receives an inbound support message via a POST webhook. 2. Normalizes the incoming payload (Gmail, Zendesk, Intercom, HelpScout, or a raw test payload) into a consistent schema with customer details, subject, body text, and a source URL. 3. Sends the normalized message to Anthropic Claude and parses the response into structured JSON containing escalation flags, severity, trigger phrases, a summary, and a suggested reply opening. 4. Stops processing silently when the message is not an escalation (severity is none). 5. Builds a formatted Slack alert and Linear issue payload, including SLA guidance, detected signals, and links back to the original conversation. 6. Posts the escalation alert to a configured Slack channel. 7. Creates a Linear ticket for critical, high, and medium severity escalations and sends a Slack DM to a manager for critical and high cases. ## Setup 1. Add an Anthropic API credential for the Anthropic Chat Model node. 2. Add a Slack OAuth2 credential, set the target channel (for example, #escalations), and set the manager’s Slack user ID for direct messages. 3. Add a Linear OAuth2 credential and replace the placeholder Linear team ID used when creating tickets. 4. Copy the webhook URL from the webhook trigger and configure Gmail/Zendesk/Intercom/HelpScout (or your custom source) to POST message payloads to it in one of the supported formats.

View

Triage construction incidents with GPT-4o, Slack, Gmail and Google Sheets

## Quick Overview This workflow ingests construction incident webhooks, normalizes the payload, and uses OpenAI GPT-4o-mini to classify each incident by type and urgency, then routes alerts to Slack and Gmail and logs incidents to Google Sheets, with a daily Slack digest generated from the sheet. ## How it works 1. Receives an incoming incident via a POST webhook. 2. Normalizes the incoming Procore/Fieldwire-style payload into a consistent incident object (ID, title, description, location, reporter, assignee, and timestamps). 3. Sends the incident details to OpenAI (GPT-4o-mini) to classify issue type and urgency and generate a short summary, recommended action, and tags. 4. Routes incidents by urgency, sending Critical incidents to Slack with an @channel mention and emailing details to a project manager via Gmail. 5. Sends High-urgency incidents to Slack as a formatted notice. 6. Appends every incident to a Google Sheets log with status set to open. 7. Runs daily at 18:00 server time, reads the incident log from Google Sheets, builds an urgency-grouped digest, and posts it to a Slack channel. ## Setup 1. Add credentials for OpenAI, Slack (OAuth2), Gmail (OAuth2), and Google Sheets (OAuth2). 2. Copy the webhook URL from the Webhook trigger and register it in your source system (for example, Procore or Fieldwire) as the incident-created endpoint. 3. Replace the placeholder Slack channel IDs for Critical, High, Digest, and Error alerts. 4. Update the Gmail recipient address ([email protected]) to your real project manager email. 5. Set the Google Sheets spreadsheet (document ID) and ensure the target sheet exists with columns that match the incident log fields used by the workflow. 6. Confirm the schedule trigger time (cron: 0 18 * * *) matches your desired timezone/server time for the daily digest.

View

Create and triage support tickets with HubSpot, reCAPTCHA and Gmail

## Quick Overview This webhook-based workflow validates form submissions with Google reCAPTCHA, creates or updates a contact in HubSpot, checks for an existing open ticket, and either creates a new HubSpot ticket or flags it as a duplicate, then emails support and returns an HTML response to the requester. ## How it works 1. Receives a POST request via a webhook containing the customer and complaint details. 2. Verifies the request using Google reCAPTCHA and stops processing if the verification fails. 3. Creates or updates the contact in HubSpot and retrieves any tickets associated with that contact. 4. Looks up the pipeline stage of associated tickets and detects whether an open ticket already exists. 5. If an open ticket exists, emails the support team with the duplicate details and returns an “already logged” HTML response. 6. If no open ticket exists, creates a new HubSpot ticket, patches the ticket to set the city property, and returns a “ticket submitted” HTML response. 7. After returning the webhook response for a new ticket, sends a confirmation email to the customer and a detailed notification email to the support team via Gmail. ## Setup 1. Add a HubSpot App Private Token credential and ensure the configured ticket pipeline ID, stage ID, and ticket owner ID match your HubSpot account. 2. Replace the reCAPTCHA secret in the Google reCAPTCHA request and ensure your form sends the g-recaptcha-response field to the webhook. 3. Configure the webhook URL in your form or source system to POST to /hubspot-ticket-webhook with the expected fields (email, first_name, last_name, phone, city, remarks, order_no). 4. Set up Gmail credentials for the customer and CS team emails, and update sender/recipient addresses (for example, [email protected] and [email protected]). 5. Update placeholder values in the HTML/email content (YOUR_HUBSPOT_PORTAL_ID, example.com tracking URL, and YOUR_SUPPORT_PHONE) to match your environment.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Track post-therapy wellness with GPT-4o-mini, Telegram, Slack and Sheets

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Quick Overview

How it works

Setup

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Overview

Block 2 - Section: AI Check-In Generation

Block 3 - Section: Patient Reply Capture

Block 4 - Section: Sentiment Analysis

Block 5 - Section: Escalation & Logging

Block 6 - Credentials & Security

Block 7 - Schedule Trigger (Every Hour)

Block 8 - Read Completed Sessions

Block 9 - AI: Generate Personalised Check-In Message

Block 10 - Telegram: Send Check-In to Patient

Block 11 - Sheets: Mark Check-In Sent

Block 12 - Code: Parse Sentiment JSON

Block 13 - IF: At-Risk Detected?

Block 14 - Slack: Alert Therapist (Human-in-Loop)

Block 15 - Sheets: Append to Wellness Log

Block 16 - Filter: Due for Check-In (24h passed)1

Block 17 - Merge

Block 18 - Read Completed Sessions (Reply Branch)

Block 19 - AI: Sentiment Analysis on Reply

Block 20 - Sheets: Lookup Patient by Telegram ID

Block 21 - Telegram Trigger: Capture Patient Reply

Block 22 - Code: Parse Merge Output

Block 23 - Section: Trigger & Filter

Block 24 - On Workflow Error

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions