Workflow Templates

How it works This workflow is designed to take user inputs in order to generate an image using the Riverflow 2.0 model through the Replicate API. It can handle both image generation as well as image editing. Additionally, for specific text modifications, the source text and font can be provided to help guide the model. Here is a high-level overview of how this workflow operates: An initial input form acts as the trigger for this workflow. It takes in all the parameters required by Riverflow 2.0, including: Model Font URLs + Texts Resolution Initial Image Instruction (Required) Aspect Ratio Transparency Enhance Prompt Max Iterations Safety Checker Super Resolution References Number of Outputs These inputs are then sanitized using a script and passed into a sub-workflow that handles the HTTP requests. Sub-Workflow: This workflow takes all the given parameters and makes a POST request to start the Riverflow 2.0 generation, followed by a looped GET request to check once the status is complete. The outputs are then stored in a data table, which is very important. This is done in a sub-workflow so that images can be generated in parallel when multiple outputs are required. The data table allows communication between the parent workflow and the parallel-running sub-workflows. In the parent workflow, we poll the data table to check if outputs from the sub-workflow have been generated. This is done using a loop and querying the data table to see if the outputs have been inserted. Once we have the outputs (as URLs), the raw image is also provided so that the image can be viewed or downloaded directly from the workflow (the URLs are also given if they need to be used). Setup This workflow requires a Replicate API key, which can be obtained from https://replicate.com/. Additionally, a n8n data table is needed to store outputs from parallel processes. Ideal for E-commerce Brands**: Riverflow 2.0 is heavily used for product and packaging designs and images and was developed by Sourceful. Using this workflow will help brands create images for e-commerce purposes. Marketers**: Teams can generate multiple creative variations in parallel for paid ads, social media, email campaigns, and A/B testing. Instead of manually editing assets, marketers can automate background changes, color variations, and creative iterations to rapidly test and scale winning campaigns. Design and Creative Teams**: Creative teams can use this workflow to quickly prototype visual concepts, enhance product renders, upscale images, and generate multiple design directions in minutes. It reduces repetitive production work and allows designers to focus on higher-level creative decisions. Customization Connect to External Systems**: Outputs from this workflow can be passed to an external database or system such as Shopify or Google Drive. Post-processing Automation**: This workflow can be extended into a larger image automation pipeline. Generated assets can automatically undergo resizing, background removal, format conversion, watermarking, compression optimization, or thumbnail generation, ensuring images are production-ready without manual intervention. Ad Monitoring and Reports**: Generated images can feed directly into marketing workflows (e.g., paid ads or social campaigns). Performance metrics such as CPM, CTR, and conversion rate can be tracked and logged, enabling teams to measure creative effectiveness and iterate on prompts or variations based on real performance data. More Infomation about Riverflow 2.0: www.riverflow.ai

Quick overview This workflow receives HeyReach campaign event webhooks and syncs them to Salesforce by finding or creating a Lead and logging each event as a completed Task with the message transcript and LinkedIn profile link. How it works Receives a POST webhook from HeyReach for lead and messaging events. Normalizes the payload, extracts lead identity (email and LinkedIn URL), and builds a Salesforce Task subject/description including the event label and message transcript. Searches Salesforce for an existing Lead matching the email and/or a custom LinkedIn_Profile__c field. If a matching Lead exists, creates a completed Salesforce Task linked to that Lead. If no Lead is found, creates a new Salesforce Lead (including email, title, and LinkedIn_Profile__c) and then creates a completed Task linked to the new Lead. Setup Add a Salesforce OAuth2 connection and ensure your Salesforce Lead object has a custom field API name LinkedIn_Profile__c to store the LinkedIn profile URL. In HeyReach, create a webhook pointing to this workflow’s webhook URL path (/heyreach-events) and subscribe it to the event types you want to track. Review and adjust the Salesforce field mappings (LeadSource, title, and Task status/fields) to match your Salesforce setup and reporting needs.

This workflow automatically collects historical price data from Polymarket Up/Down markets and stores it in Supabase, creating a structured and query-ready dataset for analysis. By continuously fetching price movements from prediction markets such as Bitcoin, S&P 500, and other Up/Down series, the automation enables reliable historical tracking without manual intervention. The data is normalized and persisted in Supabase, making it easy to run SQL queries, build dashboards, perform quantitative analysis, or integrate with analytics and AI pipelines. This setup is ideal for traders, data analysts, and developers who need accurate Polymarket price history for research, strategy testing, or long-term market monitoring How it works Provide the slug of the serial market you want to analyze in the initial form. The workflow is designed for live Polymarket “Up or Down” markets; copy the slug from the current market and submit it. From the slug, the workflow extracts the event ID and derives the corresponding series ID. All events in that series are retrieved, organized, and stored in an internal n8n table. This process runs only once per series to avoid duplicate data. A second workflow reads the stored events, retrieves the Up and Down token IDs, records market closing times, and filters out open markets so only historical data is processed. Market end times are converted to Unix timestamps, and start times are calculated. The workflow is structured for 1-hour markets, but the time-conversion node can be adjusted for other durations. Historical price data is then fetched and stored in a Supabase table for later analysis. How to use Copy the slug of the desired Up or Down market from Polymarket and submit it through the form. After the first workflow finishes, run the second workflow to collect historical price data. Events are processed in batches of 100 to avoid performance issues. If execution stops, simply rerun the workflow and it will continue from where it left off. Need help with implementation or customization? If you require assistance setting up this workflow, adapting it to your infrastructure, or extending it for advanced analytics, feel free to reach out by email at caio@caravelsai.com .

LLM Cost Monitor & Usage Tracker for n8n 🎯 What This Workflow Does This workflow provides comprehensive monitoring and cost tracking for all LLM/AI agent usage across your n8n workflows. It extracts detailed token usage data from any workflow execution and calculates precise costs based on current model pricing. The Problem It Solves When running LLM nodes in n8n workflows, the token usage and intermediate data are not directly accessible within the same workflow. This monitoring workflow bridges that gap by: Retrieving execution data using the execution ID Extracting all LLM usage from any nested structure Calculating costs with customizable pricing Providing detailed analytics per node and model WARNING: it works after the full execution of the workflow (i.e. you can't get this data before completion of all tasks in the workflow) ⚙️ Setup Instructions Prerequisites Experience Required: Basic familiarity with n8n LLM nodes and AI agents Agent Configuration: In your monitored workflows, go to agent settings and enable "Return Intermediate Steps" For getting execution data, you need to set upthe n8n API in your instance (also available onthe free version) Installation Steps Import this monitoring workflow into your n8n instance Go to Settings >> select n8n API from left bar >> define an API. Now you can add this as the credential for your "Get an Execution" node Configure your model name mappings in the "Standardize Names" node Update model pricing in the "Model Prices" node (prices per 1M tokens) To monitor a workflow: Add an "Execute Workflow" node at the end of your target workflow Select this monitoring workflow Important: Turn OFF "Wait For Sub-Workflow Completion" Pass the execution ID as input 🔧 Customization When You See Errors If the workflow enters the error path, it means an undefined model was detected. Simply: Add the model name to the standardize_names_dic Add its pricing to the model_price_dic Re-run the workflow Configurable Elements Model Name Mapping**: Standardize different model name variations (e.g., "gpt-4-0613" → "gpt-4") Pricing Dictionary**: Set costs per million tokens for input/output Extraction Depth**: Captures tokens from any nesting level automatically 📊 Output Data Per LLM Call Cost Breakdown**: Prompt, completion, and total costs in USD Token Metrics**: Prompt tokens, completion tokens, total tokens Performance**: Execution time, start time, finish reason Content Preview**: First 100 chars of input/output for debugging Model Parameters**: Temperature, max tokens, timeout, retry count Execution Context**: Workflow name, node name, execution status Flow Tracking**: Previous nodes chain Summary Statistics Total executions and costs Breakdown by model type Breakdown by node Average cost per call Total execution time ✨ Key Benefits No External Dependencies**: Everything runs within n8n Universal Compatibility**: Works with any workflow structure Automatic Detection**: Finds LLM usage regardless of nesting Real-time Monitoring**: Track costs as workflows execute Debugging Support**: Preview actual prompts and responses Scalable**: Handles multiple models and complex workflows 📝 Example Use Cases Cost Optimization**: Identify expensive nodes and optimize prompts Usage Analytics**: Track token consumption across teams/projects Budget Monitoring**: Set alerts based on cost thresholds Performance Analysis**: Find slow-running LLM calls Debugging**: Review actual inputs/outputs without logs Compliance**: Audit AI usage across your organization 🚀 Quick Start Import workflow Update model prices (if needed) Add monitoring to any workflow with the Execute Workflow node View detailed cost breakdowns instantly Note: Prices are configured per million tokens. Default includes GPT-4, GPT-3.5, Claude, and other popular models. Add custom models as needed.

Tags*: Supply Chain, Inventory Management, ABC Analysis, Pareto Principle, Demand Variability, Automation, Google Sheets Context Hi! I’m Samir — a Supply Chain Engineer and Data Scientist based in Paris, and founder of LogiGreen Consulting. I help companies optimise inventory and logistics operations by combining data analytics and workflow automation. This workflow is part of our inventory optimisation toolkit, allowing businesses to perform ABC classification and Pareto analysis directly from their transactional sales data. > Automate inventory segmentation with n8n! 📬 For business inquiries, feel free to connect with me on LinkedIn Who is this template for? This workflow is designed for supply chain analysts, demand planners, or inventory managers who want to: Identify their top-performing items (Pareto 80/20 principle) Classify products into ABC categories based on sales contribution Evaluate demand variability (XYZ classification support) Imagine you have a Google Sheet where daily sales transactions are stored: The workflow aggregates sales by item, calculates cumulative contribution, and assigns A, B, or C classes. It also computes mean, standard deviation, and coefficient of variation (CV) to highlight demand volatility. How does it work? This workflow automates the process of ABC & Pareto analysis from raw sales data: 📊 Google Sheets input provides daily transactional sales 🧮 Aggregation & code nodes compute sales, turnover, and cumulative shares 🧠 ABC class mapping assigns items into A/B/C buckets 📈 Demand variability metrics (XYZ) are calculated 📑 Results are appended into dedicated Google Sheets tabs for reporting 🎥 Watch My Tutorial Steps: 📝 Load daily sales records from Google Sheets 🔎 Filter out items with zero sales 📊 Aggregate sales by store, item, and day 📈 Perform Pareto analysis to calculate cumulative turnover share 🧮 Compute demand variability (mean, stdev, CV) 🧠 Assign ABC classes based on cumulative share thresholds 📥 Append results into ABC XYZ and Pareto output sheets What do I need to get started? You’ll need: A Google Sheet with sales transactions (date, item, quantity, turnover) that is available here: Test Sheet A Google Sheets account connected in n8n Basic knowledge of inventory analysis (ABC/XYZ) Next Steps 🗒️ Use the sticky notes in the n8n canvas to: Add your Google Sheets credentials Replace the Sheet ID with your own sales dataset Run the workflow and check the output tabs: ABC XYZ, Pareto, and Store Sales This template was built using n8n v1.107.3 Submitted: September 15, 2025

Quick Overview This workflow simulates an autonomous ROV mission using multi-agent control logic, runs a closed-loop 6-DOF dynamics integration, and posts mission telemetry and performance results to an external HTTP endpoint. How it works Starts when you manually trigger the workflow to begin the mission simulation. Initializes mission timing, hydrodynamic parameters, waypoints, vehicle state, and agent configurations for sonar, navigation, fault monitoring, and communications. Repeats a control-loop cycle where a simulated multibeam sonar generates obstacle detections, the mission planner advances waypoints with dwell timing, and the navigation logic computes thrust commands with PD control and artificial potential field avoidance. Detects faults such as thruster degradation, overspeed, and actuator saturation, and switches to a safe mode that scales thrust commands down when needed. Packages and logs telemetry with simulated packet loss and latency, then integrates the vehicle state forward using a 6-DOF Euler dynamics model with drag and thruster-efficiency effects. Stops when the mission time reaches the configured end time or all waypoints are completed, then computes performance metrics such as distance traveled, average speed, completion rate, packet loss, and fault summary. Sends the performance report, trajectory log, telemetry log, and fault details to a configurable HTTP endpoint and returns a final message indicating the trajectory visualization step. Setup Set the target URL in the HTTP Request node to your mission log/telemetry ingestion endpoint. If your endpoint requires authentication, add the appropriate HTTP credentials/headers in the HTTP Request node. Adjust mission parameters in the initialization code (waypoints, T_END, hydrodynamic coefficients, fault thresholds, and communication loss/latency settings) to match your scenario.

Empower your property management with a high-efficiency automated support desk. This workflow manages the complete maintenance lifecycle—from initial issue classification and ticket creation to team assignment, status updates, and tenant feedback—all centralized through WhatsApp using WATI and Google Sheets. 🎯 What This Workflow Does Turns WhatsApp into an intelligent bridge between tenants, maintenance teams, and landlords: 📝 Instant Ticket Creation Tenants can report any property issue via WhatsApp. The system automatically classifies the problem (Plumbing, Electrical, etc.) and assigns a priority level based on keywords. 🚦 Smart Command Routing A master switch node handles incoming messages based on intent: New Issue: Classifies and logs a new ticket. update <id> <status>: Allows maintenance teams to update progress. rate <id> <1-5>: Captures tenant satisfaction scores. mystatus: Provides tenants a view of their active tickets. dashboard: Gives landlords an overview of property health. 🛠️ Maintenance Coordination Simultaneously notifies the tenant of their Ticket ID and pings the relevant maintenance team with full issue details and an SLA deadline. 🚨 Proactive SLA Monitoring A daily morning trigger scans all open tickets for SLA breaches (e.g., High Priority overdue after 4 hours) and alerts the landlord and teams for immediate action. ✨ Key Features Keyword Intelligence:** Uses built-in logic to detect urgent issues like "leak" or "no power" and auto-flags them as High Priority. Team Mapping:** Automatically routes requests to specific teams (Plumbing, Electrical, Structural) based on the detected category. Service Rating Loop:** Automatically prompts tenants for a 1-5 star rating once a ticket is marked "resolved," logging feedback directly for the landlord. Property Dashboard:** Landlords receive a visual summary including total open tickets, average ratings, and category breakdowns. Audit Trail:** Every status change and team note is timestamped and saved in the lastUpdated column in Google Sheets. 💼 Perfect For Property Managers:** Handling requests for multiple buildings without a manual call center. Landlords:** Keeping a transparent, timestamped record of all repairs and contractor performance. Facility Management Firms:** Coordinating various specialized technical teams across different sites. Co-living Spaces:** Providing a modern, mobile-first support experience for young professional tenants. 🔧 What You'll Need Required Integrations WATI** – To receive tenant issues and send status updates to all parties. Google Sheets** – To act as your centralized ticket database and landlord dashboard. Optional Customizations Photo Evidence:** Add a node to allow tenants to upload photos of the damage to be saved in a Google Drive folder. AI Summarization:** Integrate OpenAI to summarize long tenant descriptions for quicker team review. 🚀 Quick Start Import Template – Copy the JSON and import it into your n8n instance. Set Credentials – Connect your WATI and Google Sheets accounts. Configure Teams – Edit the teamMap in the Classify Issue node to include your contractors' actual WhatsApp numbers. Configure Sheets – Ensure your Google Sheet has a Tickets tab with headers: ticketId, phone, tenantName, issueText, category, priority, status, assignedTeam, teamPhone, createdAt, slaDueAt, rating, lastUpdated, notes Test the Loop – Send "My sink is leaking" to your WATI number, then use a team number to reply update <ID> in-progress. 📈 Expected Results Zero manual routing: Issues reach the right technician without administrative intervention. Improved transparency: Tenants are never "left in the dark" about the status of their repairs. Data-driven management: Identify recurring structural issues and underperforming teams via the dashboard. Accountability: SLA breach alerts ensure no emergency ticket is forgotten. Ready to simplify your property management? Import this template and connect your Google Sheets to start tracking maintenance requests today!

Who’s it for This template is for teams using n8n in production who want immediate visibility into workflow failures. It’s ideal for DevOps teams, automation engineers, and operations teams who need reliable error monitoring, alerting, and historical logs without building custom observability tooling. What it does / How it works This workflow automatically captures and logs errors whenever any other n8n workflow fails. Here’s how it works: The Error Trigger node activates automatically when a workflow execution fails. It captures key error details: Workflow name Execution URL Last node executed Error message A formatted alert message is generated. The error summary is immediately sent to a designated slack channel for real-time visibility. At the same time, the full error details are appended as a new row in a Google Sheets document for long-term tracking and analysis. All of this runs automatically with no manual intervention. Requirements To use this workflow, you’ll need: Slack API credentials Google Sheets OAuth2 credentials A Slack channel for workflow alerts (e.g. #alerts-n8n-workflows) A Google Sheet with columns for: Workflow name Execution URL Node name Error message How to set up Import this workflow into your n8n instance. Connect your Slack credentials in the Slack node. Select the Slack channel where alerts should be sent. Connect your Google Sheets credentials. Replace the Google Sheet ID with your own error log sheet. Ensure the column mappings match your sheet structure. Activate the workflow. Once enabled, it will automatically monitor all workflows for failures. How to customize the workflow You can easily adapt this template to your needs: Change the Slack message format in the Set message node. Log additional metadata (execution time, environment, tags, etc.). Add more notification channels (Email, PagerDuty, Microsoft Teams). Extend logging to databases or observability tools. Why use this template 🚀 Instant visibility into workflow failures 🧠 Centralized error history for debugging and audits 🔁 Fully automated, no manual checks required 🛠️ Easy to extend as your automation stack grows This template helps you keep your n8n automations reliable, observable, and production-ready.

Video Introduction Want to automate your inbox or need a custom workflow? 📞 Book a Call | 💬 DM me on Linkedin Overview This workflow automatically sends personalized SMS notifications to customers when their order status changes in Airtable. Monitor your order management base and instantly notify customers about updates like "Confirmed" or "Shipped" without manual intervention. When an order status changes in your Orders table, a notification record is automatically created in a Status Notifications table. The workflow monitors this table, prepares personalized messages using the customer's name and order status, sends the SMS via Twilio, and updates the delivery status back to Airtable for complete tracking and logging. Key Features Automated SMS sending triggered by Airtable record changes Personalized messages with customer name and order status Complete delivery tracking with success/error status updates Error handling for invalid phone numbers Works with Twilio's free trial account for testing Common Use Cases E-commerce order status updates Shipping notifications Order confirmation messages Customer communication logging Setup Instructions Step 1: Duplicate the Airtable Base Copy the Order Management Base template to your Airtable workspace. You must use your own copy as the workflow needs write permissions. Step 2: Connect Your Accounts Add your Airtable Personal Access Token credentials to the workflow nodes Create a Twilio account (free trial available) From your Twilio dashboard, obtain your Account SID, Auth Token, and Twilio phone number Add Twilio credentials to the "Send Order Status SMS" node Step 3: Configure the Workflow In the Config node, update these URLs with your duplicated Airtable base: notifications_table_url: Your Status Notifications table URL orders_table_url: Your Orders table URL from_number: Your Twilio phone number Step 4: Customize the Message Modify the "Prepare SMS Content" node to personalize the message template with your brand voice and additional order details. Step 5: Activate Toggle the workflow to 'Active' and the automation will monitor your Airtable base every minute, sending notifications automatically.

GLPI Pending Tickets Notification to Microsoft Teams 📋 Overview Automate daily notifications for pending GLPI tickets directly to Microsoft Teams. Never miss critical support cases with this workflow that monitors assigned tickets and sends personal alerts. 🔧 How It Works Connect to GLPI - Authenticates and searches for your assigned tickets Filter Results - Finds tickets in "In Progress" status within your entity Send Notifications - Delivers formatted alerts to your Teams chat Clean Up - Properly closes GLPI session for security 📊 What Gets Monitored Tickets assigned to specific technician (configurable) Status: "In Progress/Assigned" Entity: Your organization (customizable) Date range: Tickets after specified date ⚡ Key Benefits Never Miss Deadlines - Daily automated reminders Personal Focus - Only your assigned tickets Time Savings - Eliminates manual checking (15-30 min daily) Rich Details - Shows ticket title, ID, and due date ⚙️ Setup Steps Time Required: ~30 minutes Import Template - Add workflow to your n8n instance Configure GLPI - Set server URL, credentials, and app token Set Technician ID - Update to your GLPI user ID Connect Teams - Link your Microsoft Teams account Customize Filters - Adjust entity name and date range Test & Schedule - Verify notifications and set daily trigger 🎨 Easy Customization Change technician ID for different users Adjust notification schedule (default: 8 AM daily) Modify entity filters for your organization Add multiple technicians by duplicating workflow 📋 Prerequisites GLPI instance with API enabled GLPI user account with ticket read permissions Microsoft Teams account (basic license) n8n with Microsoft Teams integration Perfect for support technicians who want automated reminders about their pending GLPI tickets without manual daily checks.

Who's it for This template is for sales teams, marketing operations (M-Ops), or freelancers who use Airtable as a "control panel" or staging area for new leads. If you're tired of manually copying and pasting approved leads into HubSpot, this workflow automates the entire process for you. How it works This workflow runs on a schedule (e.g., every 5 minutes) to check for new leads. 1. Before: Your Airtable has new leads with a '📥 New Lead' status. 2. The Trigger: You (or a teammate) manually review and change a lead's status to '👍 Ready to Sync'. 3. The Workflow Runs: n8n fetches all leads in that view (up to 50 at a time) and loops through them one by one. For each lead, it: Finds (or creates) a Company in HubSpot based on the email domain. Creates (or updates) a Contact in HubSpot based on the email. Automatically associates that Contact with that Company. 4. After: The workflow automatically updates the same Airtable row with the new HubSpot IDs and a '✅ Synced' status, completing the 2-way sync. This template includes a full batch-processing loop, robust error-handling (it logs failures back to Airtable), and detailed sticky notes to guide you. How to set up Setup should take less than 10 minutes. All detailed instructions are in the sticky notes inside the workflow. Copy the Airtable Base: This is a mandatory first step! You must use this template. ➡️ Click Here to Copy the Base Template (First time using Airtable? Sign up here with my link) Add Your Credentials: How to connect Airtable to n8n (Video) How to connect HubSpot to n8n (Video) Configure 3 Nodes: Schedule Trigger: Set how often you want it to run (e.g., every 5 minutes). get 👍Ready to Sync: Select your Airtable credential and the Base you copied. Also, Do this for the other Airtable nodes. Search company: Select your HubSpot credential. Also, Do this for the othe HubSpot nodes. Activate! Save and activate the workflow. To test it, just change a lead's 'Status' in Airtable to '👍 Ready to Sync'. Requirements An Airtable account. A HubSpot account (a free developer sandbox account is recommended for testing). n8n credentials for both Airtable and HubSpot (using a Private App Token for HubSpot). How to customize the workflow Add More Fields:** Easily sync more data (like 'Phone Number' or 'Lead Source') by adding columns in your Airtable, then adding those fields to the Create or update a contact node in n8n. Change the Schedule:** Adjust the Schedule Trigger to run more or less frequently. Add Notifications:** Connect a Slack or email node to the 👍Done! Going for next record (success) or specially 👎Failed! Going for next record1 (error) paths to get real-time alerts.

💊 WhatsApp Medication Adherence & Caregiver Alert Automation Ensure health and safety with a fully automated medication adherence system. This workflow manages the entire patient care cycle—from scheduled dosage reminders to interactive logging and automated caregiver escalations—all through WhatsApp using WATI and Google Sheets. 🎯 What This Workflow Does Turns WhatsApp into a proactive health assistant and caregiver's dashboard: 📝 Timed Dosage Reminders A scheduled trigger fires 3x daily (Morning, Afternoon, Night) to identify which medications are due and send personalized WhatsApp alerts. 🚦 Smart Patient Routing A Switch node detects patient replies to manage their health data in real-time: taken: Logs the dose as complete and updates the patient's "Streak". skip: Records the skipped dose and empathetic feedback while checking for consecutive skips. snooze: Schedules a 30-minute follow-up reminder. mystats: Generates a 7-day adherence report with visual progress bars. mymeds: Provides the full daily medication schedule and instructions. 👁️ Automated Caregiver Alerts An hourly check detects "Pending" reminders. If a patient hasn't responded within 2 hours, the bot automatically alerts the designated caregiver via WhatsApp. 📊 Comprehensive Analytics Caregivers can request a full patient report (e.g., report <phone>) to view a categorized summary of taken vs. missed doses. ✨ Key Features Slot-Based Intelligence:** Automatically determines if it is Morning, Afternoon, or Night to send only relevant medications. Gamified Adherence:** Tracks "Streaks" (consecutive days taken) with motivational emojis to encourage patient consistency. Visual Bar Charts:** Patients and caregivers receive structured reports using visual bars (███░░) to show adherence percentages. Temporary Snooze Queue:** Uses a dedicated "SnoozeQueue" tab to ensure follow-up reminders aren't forgotten. Proactive Safety:** Built-in logic to detect 2+ consecutive skips, alerting caregivers before it becomes a health risk. 💼 Perfect For Elderly Care:** Providing automated support for seniors managing multiple daily medications. Chronic Condition Management:** Ensuring strict adherence for long-term treatments like hypertension or diabetes. Home Healthcare Agencies:** Scaling patient monitoring without increasing manual staff check-ins. Clinical Trials:** Tracking participant adherence with a digital, timestamped audit trail. 🔧 What You'll Need Required Integrations WATI** – To deliver medication reminders and process patient responses. Google Sheets** – To store the master medication list, adherence logs, and snooze queue. Optional Customizations AI Analysis:** Integrate OpenAI to answer patient questions about specific medication side effects. Emergency Escalation:** Add a voice call node if a high-priority medication is missed 3 times in a row. 🚀 Quick Start Import Template – Copy the JSON and import it into your n8n instance. Set Credentials – Connect your WATI and Google Sheets accounts. Configure Sheets – Ensure your Google Sheet has three tabs: Medications: phone, patientName, medName, dosage, frequency, timeSlots, status, caregiverPhone AdherenceLog: logKey, phone, patientName, date, slot, status, sentAt, respondedAt, caregiverPhone SnoozeQueue: phone, patientName, followUpAt, snoozedAt, status Test Reminders – Add a test row to your sheet and manually trigger the 8 AM node. Simulate a Reply – Reply taken or mystats to your WATI number to see your report generated live. 🎨 Customization Options Custom Time Windows:** Modify the Filter Medications by Time Slot code to align with specific clinic hours. Empathetic Messaging:** Customize the reinforce messages in the Process Taken and Process Skip nodes to match your brand voice. Adherence Thresholds:** Adjust the caregiver alert logic to trigger after 1 hour or 4 hours depending on medication sensitivity. 📈 Expected Results 95% adherence transparency for caregivers and family members. Reduced health risks by identifying missed doses within a 2-hour window. Improved patient morale through positive streak reinforcement and visual progress. Efficient monitoring: One caregiver can monitor dozens of patients through a single WhatsApp interface. Ready to launch your digital health assistant? Import this template and connect your Google Sheets to start improving patient adherence today!