Health monitoring system with Grok-3 AI analysis and family/doctor email alerts

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

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Introduction Automates patient health monitoring by analyzing submitted health data via AI, determining alert necessity, and notifying family and doctors when critical conditions detected. How It W...

Best for

Personal Productivity automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.webhook, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.if, n8n-nodes-base.emailsend, n8n-nodes-base.merge, n8n-nodes-base.respondtowebhook

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Cheng Siong Chin.

Original n8n.io source

1.1 Workflow description

Title: Health monitoring system with Grok-3 AI analysis and family/doctor email alerts
Workflow name: Health monitoring system with Grok-3 AI analysis and family/doctor email alerts

Introduction

Automates patient health monitoring by analyzing submitted health data via AI, determining alert necessity, and notifying family and doctors when critical conditions detected.

How It Works

Webhook receives health data, AI agent analyzes vitals using OpenRouter with structured parsing. Conditional logic checks alert necessity. If yes: prepares data, emails family, checks doctor criteria, sends doctor email, merges results. If no: skips alerts. Combines outcomes and responds to webhook.

Workflow Template

Webhook → Extract Data → AI Agent → [OpenRouter + Memory + Parser] → Check Alert → [Prepare + Email Family + Check Doctor + Email Doctor] OR [No Alert] → Merge → Combine → Respond

Workflow Steps

Reception & Extraction: Webhook receives vitals/symptoms, parses JSON payload
AI Analysis: OpenRouter analyzes vitals against ranges, accesses history via Memory Tool, formats assessment via Output Parser
Routing & Notification: Conditional logic checks severity. Alert path emails family/doctor if critical. No alert logs status
Consolidation: Merges outcomes, sends webhook response

Setup Instructions

Configure webhook endpoint with auth token. Add OpenRouter API key and select model. Set up AI Agent with Memory Tool and Output Parser. Connect Gmail/SMTP for notifications with recipient addresses. Configure alert thresholds (temp >38.5°C, BP >140/90, HR <60/>100). Set doctor notification criteria.

Prerequisites

n8n instance, OpenRouter API key, AI model access, Patient database, Gmail/SMTP credentials, Family contacts, Doctor contacts, Webhook authentication

Use Cases

Chronic Disease: Diabetic submits glucose readings. AI detects >250mg/dL, alerts family and endocrinologist. Elderly Care: Senior's vitals monitored via wearable. AI identifies irregular rhythm, emails caregiver and cardiologist.

Customization

Adjust thresholds by demographics. Add vital types (O2, glucose trends). Customize AI prompts for conditions. Integrate SMS via Twilio. Add escalation logic. Include medication tracking. Connect EHR systems. Implement frequency limits. Add dashboard reporting.

Benefits

Rapid Response: Detects emergencies in seconds. Intelligent Filtering: Prevents false alarms. Family Peace: Automated notifications keep loved ones informed. Clinical Efficiency:

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 - Webhook - Submit Health Data

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

Block 2 - Extract Health Data

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 3 - AI Health Analysis Agent

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 1.7

Block 4 - Structured Output Parser

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.2

Block 5 - Check If Alert Needed

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

Block 6 - Prepare Alert Data

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 7 - Send Email to Family

Type / Role: n8n-nodes-base.emailSend - emailSend
Config choices: Version 2.1

Block 8 - Check If Doctor Alert Needed

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

Block 9 - Send Email to Doctor

Type / Role: n8n-nodes-base.emailSend - emailSend
Config choices: Version 2.1

Block 10 - Merge Alert Results

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 11 - No Alert Required

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 12 - Combine Results

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

Block 13 - Respond to Webhook

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

Block 14 - OpenRouter Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices: Version 1

Block 15 - Sticky Note

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

Block 16 - Sticky Note1

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

Block 17 - Sticky Note2

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

3. Summary Table

Workflow	Health monitoring system with Grok-3 AI analysis and family/doctor email alerts
Complexity	advanced
Nodes	17
Categories	Personal Productivity, AI Summarization
Author	Cheng Siong Chin
Published	05 Nov 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/10525/10525.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 Personal Productivity workflows AI Summarization workflows

Frequently asked questions

What does Health monitoring system with Grok-3 AI analysis and family/doctor email alerts 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 Personal Productivity, AI Summarization use case.

Cheng Siong Chin

203 workflows

Nodes

n8n-nodes-base.webhook n8n-nodes-base.set @n8n/n8n-nodes-langchain.agent @n8n/n8n-nodes-langchain.outputparserstructured n8n-nodes-base.if n8n-nodes-base.emailsend n8n-nodes-base.merge n8n-nodes-base.respondtowebhook

Complexity

advanced

Published 05 Nov 2025

Likes 0

View on n8n.io Download Workflow

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

Share Your Workflow

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

Submit Your Template How to Submit

Related Workflows

Manage Google Calendar events with Zalo Bot, OpenAI and Gemini

## Quick Overview This workflow lets users manage Google Calendar by sending text or voice messages to a Zalo Official Account bot, transcribing voice notes with Google Gemini and using an OpenAI-powered agent to create, update, list, or delete events, then replying in Zalo with the result. ## How it works 1. Receives an incoming text or voice message through a Zalo Bot trigger. 2. Sends a typing indicator back to the Zalo chat and normalizes key message fields (chat ID, type, text, and voice URL). 3. If the message is a voice note, sends the audio URL to Google Gemini to transcribe it into text. 4. Sends the combined text/transcription to an OpenAI chat model agent that interprets the request in Vietnamese and decides whether to list, create, update, or delete a Google Calendar event. 5. Uses Google Calendar tools to get events and then create, update, or delete the targeted event based on the agent’s extracted parameters. 6. Sends the agent’s Markdown-formatted response back to the user in Zalo, and posts an error message to Zalo if the agent run fails. ## Setup 1. Install the community node package `n8n-nodes-zalo-bot-official` and restart n8n if required. 2. Connect your Zalo Bot API credentials and configure the Zalo webhook URL in your Zalo Official Account so incoming messages reach this workflow. 3. Add a Google Calendar OAuth2 credential and set the target calendar account (currently configured as `[email protected]`) for all calendar operations. 4. Add a Google Gemini (PaLM) API credential for audio transcription and ensure voice messages include a reachable `voice_url`. 5. Add an OpenAI API credential, select the chat model you want to use (currently `gpt-5-mini`), and adjust the system prompt/tone if needed.

View

Screen LinkedIn jobs and generate tailored resume and cover PDFs with Anthropic and DocRaptor

## Quick Overview This workflow collects your job preferences and resume via an n8n form, scrapes fresh LinkedIn job listings with Apify, screens and ranks matches using Anthropic Claude, generates tailored resume and cover letter PDFs via DocRaptor, then emails them to you and logs each match in Google Sheets. ## How it works 1. Receives a form submission with your email, target role, seniority, locations, skills, deal-breakers, and resume text. 2. Calls the Apify LinkedIn Job Scraper API to fetch up to 150 jobs posted in the last 7 days for the provided keywords and location. 3. Removes duplicates and filters out obvious mismatches based on seniority, required years of experience patterns, and location rules. 4. Uses Anthropic Claude (Haiku) to score each remaining job for relevance and eligibility and returns a JSON verdict and fit score. 5. Ranks the results, drops rejected roles, and keeps the top five best-scoring matches. 6. Uses Anthropic Claude (Sonnet) to generate a structured resume JSON and cover letter JSON tailored to each shortlisted job using only facts from your provided profile. 7. Renders the resume and cover letter to HTML, converts them to PDF files with DocRaptor, emails the PDFs to you via Gmail, and appends a tracker row to Google Sheets. ## Setup 1. Add credentials for Anthropic (Claude), Gmail, Google Sheets, and DocRaptor (HTTP Basic Auth with your API key as the username and a blank password). 2. Replace YOUR_APIFY_TOKEN in the Apify HTTP request URL and ensure you have access to the Apify LinkedIn Jobs Scraper actor endpoint used in the workflow. 3. Create a Google Sheet with a “Tracker” tab and set the document ID (YOUR_TRACKER_SHEET_ID) to match your sheet. 4. If you want non-watermarked PDFs, set DocRaptor "test" to false in both PDF generation requests.

View

Triage and route tasks with Google Sheets, GPT-4o-mini, Gmail, Slack, and Google Tasks

## Quick Overview This workflow collects tasks via a webhook, stores validated tasks in Google Sheets, and runs a daily prioritization routine that creates urgent items in Google Tasks with Slack alerts while summarizing medium/low tasks with OpenAI and emailing the digest via Gmail. ## How it works 1. Receives a POST webhook request containing task details and normalizes fields like priority and due date. 2. Validates required fields (including allowed priority values) and rejects invalid submissions with an error. 3. Appends valid tasks to Google Sheets with a pending status and returns a success response to the webhook caller. 4. Runs daily on a schedule, reads tasks from Google Sheets, keeps only pending items, removes duplicates, and sorts them by priority. 5. For high-priority tasks, creates a Google Tasks item and sends a Slack alert. 6. For medium and low-priority tasks, compiles a digest, generates an email-ready summary with OpenAI, and sends it via Gmail. 7. Updates each handled task in Google Sheets with a Processed status and a processed timestamp. ## Setup 1. Create a Google Sheet with columns for taskName, priority, category, dueDate, status, createdAt, and processedAt, and update the spreadsheet and sheet IDs in the Google Sheets steps. 2. Add Google Sheets OAuth2 credentials for both reading and updating/appending rows. 3. Add credentials for Google Tasks, Slack (OAuth2), Gmail, and OpenAI, and set the target Google Task list, Slack destination, and email recipients/subject as needed. 4. Copy the webhook URL from the webhook trigger and configure your task intake source to send POST requests with fields like "Task Name", "Priority", "Category", and "Due Date". 5. Adjust the schedule time and any validation rules (required fields and accepted priority values) to match your process.

View

Need Custom Automation?

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

Health monitoring system with Grok-3 AI analysis and family/doctor email alerts

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Introduction

How It Works

Workflow Template

Workflow Steps

Setup Instructions

Prerequisites

Use Cases

Customization

Benefits

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Webhook - Submit Health Data

Block 2 - Extract Health Data

Block 3 - AI Health Analysis Agent

Block 4 - Structured Output Parser

Block 5 - Check If Alert Needed

Block 6 - Prepare Alert Data

Block 7 - Send Email to Family

Block 8 - Check If Doctor Alert Needed

Block 9 - Send Email to Doctor

Block 10 - Merge Alert Results

Block 11 - No Alert Required

Block 12 - Combine Results

Block 13 - Respond to Webhook

Block 14 - OpenRouter Chat Model

Block 15 - Sticky Note

Block 16 - Sticky Note1

Block 17 - Sticky Note2

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