Smart IoT device health monitor with ScrapeGraphAI and Telegram
Smart IoT Device Health Monitor with AI-Powered Dashboard Analysis and Real-Time Alerting
π― Target Audience
- IT operations and infrastructure teams
- IoT system administrators and engineers
- Facility and building management teams
- Manufacturing and industrial operations managers
- Smart city and public infrastructure coordinators
- Healthcare technology administrators
- Energy and utilities monitoring teams
- Fleet and asset management professionals
- Security and surveillance system operators
- Property and facility maintenance teams
π Problem Statement
Monitoring hundreds of IoT devices across multiple dashboards is overwhelming and reactive, often leading to costly downtime, missed maintenance windows, and system failures. This template solves the challenge of proactive IoT device monitoring by automatically analyzing device health metrics, detecting issues before they become critical, and delivering intelligent alerts that help teams maintain optimal system performance.
π§ How it Works
This workflow automatically monitors your IoT dashboard every 30 minutes using AI-powered data extraction, analyzes device health patterns, calculates system-wide health scores, and sends intelligent alerts only when intervention is needed, preventing alert fatigue while ensuring critical issues are never missed.
Key Components
- Schedule Trigger - Runs every 30 minutes for continuous device monitoring
- AI Dashboard Scraper - Uses ScrapeGraphAI to extract device data from any IoT dashboard without APIs
- Health Analyzer - Calculates system health scores and identifies problematic devices
- Smart Alert System - Sends notifications only when health drops below thresholds
- Telegram Notifications - Delivers formatted alerts with device details and recommendations
- Activity Logger - Maintains historical records for trend analysis and reporting
π Device Health Analysis Specifications
The template monitors and analyzes the following device metrics:
| Metric Category | Monitored Parameters | Analysis Method | Alert Triggers | Example Output | |-----------------|---------------------|-----------------|----------------|----------------| | Device Status | Online/Offline/Error | Real-time status check | Any offline devices | "Device-A01 is offline" | | Battery Health | Battery percentage | Low battery detection | Below 20% charge | "Sensor-B03 low battery: 15%" | | Temperature | Device temperature | Overheating detection | Above 70Β°C | "Gateway-C02 overheating: 75Β°C" | | System Health | Overall health score | Online device ratio | Below 80% health | "System health: 65%" | | Connectivity | Network status | Connection monitoring | Loss of communication | "3 devices offline" | | Performance | Response metrics | Trend analysis | Degraded performance | "Response time increasing" |
π οΈ Setup Instructions
Estimated setup time: 15-20 minutes
Prerequisites
- n8n instance with community nodes enabled
- ScrapeGraphAI API account and credentials
- Telegram bot token and chat ID
- Access to your IoT dashboard URL
- Basic understanding of your device naming conventions
Step-by-Step Configuration
1. Install Community Nodes
# Install required community nodes
npm install n8n-nodes-scrapegraphai
2. Configure ScrapeGraphAI Credentials
- Navigate to Credentials in your n8n instance
- Add new ScrapeGraphAI API credentials
- Enter your API key from ScrapeGraphAI dashboard
- Test the connection to ensure it's working
3. Set up Schedule Trigger
- Configure the monitoring frequency (default: every 30 minutes)
- Adjust timing based on your operational needs:
- Every 15 minutes:
*/15 * * * * - Every hour:
0 * * * * - Every 5 minutes:
*/5 * * * *
- Every 15 minutes:
4. Configure Dashboard URL
- Update the "Get Data" node with your IoT dashboard URL
- Customize the AI prompt to match your dashboard structure
- Test data extraction to ensure proper JSON formatting
- Adjust device field mappings as needed
5. Set up Telegram Notifications
- Create a Telegram bot using @BotFather
- Get your chat ID from @userinfobot
- Configure Telegram credentials in n8n
- Test message delivery to ensure alerts work
6. Customize Health Thresholds
- Adjust health score threshold (default: 80%)
- Set battery alert level (default: 20%)
- Configure temperature warning (default: 70Β°C)
- Customize alert conditions based on your requirements
7. Test and Validate
- Run the workflow manually with your dashboard
- Verify device data extraction accuracy
- Test alert conditions and message formatting
- Confirm logging functionality works correctly
π Workflow Customization Options
Modify Monitoring Frequency
- Adjust schedule for different device criticality levels
- Add business hours vs. off-hours monitoring
- Implement variable frequency based on system health
- Add manual trigger for on-demand monitoring
Extend Device Analysis
- Add more device metrics (memory, CPU, network bandwidth)
- Implement predictive maintenance algorithms
- Include environmental sensors (humidity, air quality)
- Add device lifecycle and warranty tracking
Customize Alert Logic
- Implement escalation rules for critical alerts
- Add alert suppression during maintenance windows
- Create different alert channels for different severity levels
- Include automated ticket creation for persistent issues
Output Customization
- Add integration with monitoring platforms (Grafana, Datadog)
- Implement email notifications for management reports
- Create executive dashboards with health trends
- Add integration with maintenance management systems
π Use Cases
- Industrial IoT Monitoring: Track manufacturing equipment and sensors
- Smart Building Management: Monitor HVAC, lighting, and security systems
- Fleet Management: Track vehicle telematics and diagnostic systems
- Healthcare Device Monitoring: Ensure medical device uptime and performance
- Smart City Infrastructure: Monitor traffic lights, environmental sensors, and public systems
- Energy Grid Monitoring: Track smart meters and distribution equipment
π¨ Important Notes
- Respect your dashboard's terms of service and rate limits
- Implement appropriate delays between requests to avoid overloading systems
- Regularly review and update device thresholds based on operational experience
- Monitor ScrapeGraphAI API usage to manage costs effectively
- Keep your credentials secure and rotate them regularly
- Ensure alert recipients are available to respond to critical notifications
- Consider implementing backup monitoring systems for critical infrastructure
- Maintain device inventories and update monitoring parameters as systems evolve
π§ Troubleshooting
Common Issues:
- ScrapeGraphAI connection errors: Verify API key and account status
- Dashboard access issues: Check URL accessibility and authentication requirements
- Data extraction failures: Review AI prompt and dashboard structure changes
- Missing device data: Verify device naming conventions and field mappings
- Alert delivery failures: Check Telegram bot configuration and chat permissions
- False alerts: Adjust health thresholds and alert logic conditions
Support Resources:
- ScrapeGraphAI documentation and API reference
- n8n community forums for workflow assistance
- Telegram Bot API documentation
- IoT platform-specific monitoring best practices
- Device manufacturer monitoring guidelines
- Industrial IoT monitoring standards and frameworks
Smart IoT Device Health Monitor with ScrapegraphAI and Telegram
This n8n workflow automates the monitoring of smart IoT device health and sends critical alerts to Telegram. It's designed to periodically check a condition and notify a designated channel if the condition is met, ensuring timely awareness of potential issues.
What it does
This workflow simplifies the process of monitoring and alerting by:
- Scheduled Polling: Periodically triggers the workflow at a specified interval (e.g., every hour, daily).
- Custom Logic Execution: Executes custom JavaScript code, likely to fetch or process IoT device health data, or to interact with a service like ScrapegraphAI to gather insights.
- Conditional Evaluation: Evaluates the results from the custom code using an If node. This node determines if a specific condition (e.g., device health status, anomaly detected) is met.
- Telegram Notification: If the condition evaluates to TRUE, a message is sent to a specified Telegram chat, providing an immediate alert.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Telegram Account: A Telegram account and a Bot Token for sending messages. You will need to create a Telegram Bot and obtain its API token.
- Telegram Chat ID: The chat ID where the alerts should be sent. This can be a private chat or a group chat.
- Custom Code Logic: The JavaScript code within the "Code" node needs to be configured to interact with your IoT device data source or ScrapegraphAI, and define the health monitoring logic.
Setup/Usage
- Import the Workflow:
- In your n8n instance, go to "Workflows".
- Click "New" or "Import from JSON".
- Paste the provided JSON into the import dialog.
- Configure Credentials:
- Telegram:
- Locate the "Telegram" node.
- Click on the "Credential" field and select "Create New Credential".
- Enter your Telegram Bot Token.
- In the Telegram node's "Chat ID" field, enter the ID of the chat where you want to receive notifications.
- Telegram:
- Customize the Code Node:
- Locate the "Code" node.
- Edit the JavaScript code to implement your specific IoT device health check logic. This might involve:
- Making HTTP requests to an IoT platform API.
- Processing data received from a previous node (if you add one).
- Integrating with ScrapegraphAI to analyze data or generate insights.
- The output of this node should be structured in a way that the "If" node can easily evaluate a condition (e.g., a boolean
isAlertNeededor a status string).
- Configure the If Node:
- Locate the "If" node.
- Set up the condition(s) based on the output of your "Code" node. For example, if your "Code" node outputs
{{ $json.isAlertNeeded }}, you would set a condition likeValue1: {{ $json.isAlertNeeded }} | Operation: Is True.
- Configure the Schedule Trigger:
- Locate the "Schedule Trigger" node.
- Set the desired interval for the workflow to run (e.g., every 1 hour, every 30 minutes, daily).
- Activate the Workflow:
- Once all configurations are complete, save the workflow and activate it by toggling the "Active" switch in the top right corner.
The workflow will now run automatically based on your schedule, check the IoT device health, and send Telegram alerts if necessary.
Related Templates
AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp
This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The βvirtual executive team,β is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier π― Core Features π§βπΌ 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. π 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. π΅οΈββοΈ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. β° 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline β key traits for early-stage success. ποΈ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. π¬ WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. βοΈ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. π§© Integrations Required Gemini API β for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API β for business and competitor analysis SerpAPI β for market research and opportunity scouting Google OAuth β to connect Sheets, Calendar, and Gmail WhatsApp Business API β for message triggers and responses π Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. π§° Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startupβs needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you π‘ Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API
Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. Itβs designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this β€ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen