HTTP Request and Microsoft Teams integration

This workflow processes raw meeting recordings or handwritten notes, automatically transcribes and summarizes them, and then distributes the concise summary to all meeting participants via Microsoft Teams while also creating an action-item task in ClickUp. The goal is to save time, keep everyone aligned, and ensure follow-up tasks are tracked in your project management workspace. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or n8n.cloud) ScrapeGraphAI community node installed Microsoft Teams tenant with permissions to create Incoming Webhooks or use Bot Framework ClickUp workspace and a target List to hold meeting action items Optional: OpenAI or any LLM API account for high-quality summarization Required Credentials Microsoft Teams Webhook URL** – to post summary messages ClickUp Personal Access Token** – to create tasks OpenAI API Key** (optional but recommended) – for AI-powered summarization ScrapeGraphAI API Key** – placeholder key to satisfy the template requirement Specific Setup Requirements | Item | Description | Example | |------|-------------|---------| | Teams Channel Webhook | Create an Incoming Webhook in the desired Teams channel and copy the URL | https://outlook.office.com/webhook/... | | ClickUp List ID | The numeric ID of the list where tasks will be created | 90123456 | | Summarization Model | The LLM model or API you prefer to use | gpt-3.5-turbo | How it works This workflow transcribes or parses meeting content, leverages an LLM to generate a concise summary and action items, then distributes the results to participants in Microsoft Teams and creates a follow-up task in ClickUp. Everything runs in a single automated flow triggered manually or on a schedule. Key Steps: Manual Trigger**: Start the workflow after a meeting ends. Sticky Note**: Provides on-canvas documentation for quick reference. Set Node – Upload Metadata**: Define meeting title, date, and participants. HTTP Request – Transcription**: Send audio/video file to a transcription service (e.g., Azure Speech-to-Text). Wait**: Pause until the transcription is complete. Code – Summarize**: Use OpenAI to summarize the transcript and extract action items. IF Node – Validate Output**: Ensure the summary exists; handle errors otherwise. Merge**: Combine summary with participant list. Microsoft Teams Node**: Send the summary to each participant or channel via webhook. ClickUp Node**: Create a task containing the summary and action items. Set up steps Setup Time: 10-15 minutes Create Teams Webhook: In Microsoft Teams, navigate to the target channel → Manage channel → Connectors → Incoming Webhook → give it a name (e.g., “MeetingBot”) and copy the generated URL. Generate ClickUp Personal Access Token: ClickUp → Settings → Apps → Generate Token → copy and store it securely. Get ClickUp List ID: Open the list in ClickUp and copy the numeric ID from the URL bar. Optional – Obtain OpenAI API Key: Sign in to OpenAI → API Keys → Create new secret key. Add Credentials in n8n: In n8n, go to Credentials → New → add Microsoft Teams, ClickUp, and OpenAI (Generic HTTP). Import Workflow: Paste the JSON workflow into n8n or use “Templates → Import”. Configure Nodes: In the Set Node: update meeting_title, date, and participants array. In HTTP Request: set the transcription service endpoint and authentication. In Code – Summarize: paste your OpenAI key or select credential. In Microsoft Teams Node: select the Teams credential and webhook URL. In ClickUp Node: select ClickUp credential and enter the List ID. Test: Click “Execute Workflow” on the Manual Trigger node. Verify that a message appears in Teams and a task is created in ClickUp. Node Descriptions Core Workflow Nodes: Manual Trigger** – Initiates the workflow manually or on a schedule. Sticky Note** – Documentation block outlining purpose and credential usage. Set** – Stores meeting metadata and participants list. HTTP Request** – Sends meeting recording to a transcription service and fetches results. Wait** – Holds the workflow until transcription is ready. Code** – Summarizes transcript and extracts action items via OpenAI. IF** – Validates summarization success; branches on failure. Merge** – Combines summary text with participant emails/usernames. Microsoft Teams** – Posts summary to Teams channel or direct messages. ClickUp** – Creates a task containing summary and action items. Data Flow: Manual Trigger → Set → HTTP Request → Wait → Code → IF → Merge → Microsoft Teams Merge → ClickUp Customization Examples Change summarization prompt // Inside the Code node const prompt = ` You are an expert meeting assistant. Summarize the following transcript in under 150 words. List action items in bullet points with owners. Transcript: ${items[0].json.transcript} `; Send summary as a PDF attachment // Add Convert & Save node before Teams // Convert markdown summary to PDF and attach in Teams node Data Output Format The workflow outputs structured JSON data: { "meeting_title": "Q3 Strategy Sync", "date": "2024-05-10", "participants": ["[email protected]", "[email protected]"], "summary": "We reviewed Q3 OKRs, decided to ...", "action_items": [ { "owner": "John", "task": "Prepare budget draft", "due": "2024-05-20" }, { "owner": "Jane", "task": "Compile market research", "due": "2024-05-25" } ], "clickup_task_id": "abcd1234", "teams_message_id": "msg7890" } Troubleshooting Common Issues Teams message not sent – Verify the Incoming Webhook URL and that the Teams node uses the correct credential. ClickUp task missing – Ensure the List ID is correct and the ClickUp token has tasks:write scope. Empty summary – Check that the transcription text is populated and the OpenAI prompt is valid. Performance Tips Compress large audio/video files before sending to the transcription service. Use batching in the Teams node if participant list is >20 to avoid rate limits. Pro Tips: Schedule the workflow to auto-run 5 minutes after recurring meeting end-times. Customize the ClickUp task description template to include embedded links. Add a “Send Email” node for participants not on Teams.

Who it's for This n8n workflow is designed for content creators, digital marketers, and social media managers who want to automate their entire content creation and publishing process across multiple platforms. It provides a complete end-to-end system capable of taking a single specific idea and automatically generating a full piece of content from it—complete with images, translations, and platform-optimized formatting. The workflow then publishes the final content to WordPress, Facebook, LinkedIn, and Telegram. Features Multi-platform publishing:** WordPress, Facebook, LinkedIn, Telegram AI-powered content generation using OpenAI (LangChain):* Can generate a full article or content piece from a single specific idea or topic* Multi-language support:** Automatic translation via Google Translate API Automatic image processing:** Resizing, optimization, and WordPress upload Google Sheets integration:** For topic management, content queueing, and status tracking Notifications:** Send updates via Discord, Telegram, WhatsApp, and Gmail Flexible workflow triggers:** Supports both manual form submissions and automated scheduled publishing Requirements OpenAI API access for content generation Google Translate API credentials WordPress API access Social media API credentials (Facebook, Telegram, LinkedIn) Google Sheets OAuth2 credentials Google Drive access for image storage Configure Credentials Google APIs**: Configure Google Sheets, Google Drive, and Google Translate with proper OAuth2 credentials OpenAI API**: Set up with appropriate model access (gpt-4.1-mini) WordPress API**: Configure with your WordPress site credentials Social Media APIs**: Set up each platform with proper API keys and target IDs Notification Services**: Configure each service with proper API keys and target IDs Important Notes Form captures topic, type, user, word count, company info, domain, language, and image AI content generation uses customizable prompts Images resized up to 5000x5000 px before upload Content can be translated via Google Translate API Workflow publishes text and image posts across platforms Google Sheets tracks content status in real-time Support & Help WhatsApp**: Chat on WhatsApp Discord**: SpaGreen Community Facebook Group**: SpaGreen Support Website**: https://spagreen.net Developer Portfolio**: Codecanyon SpaGreen

Employee Directory Sync – Microsoft Teams & Coda ⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n instance before using this template. This workflow keeps your employee directory perfectly synchronized across your HRIS (or any REST-compatible HR database), Microsoft Teams, Coda docs, and Slack channels. It automatically polls the HR system on a schedule, detects additions or updates, and propagates those changes to downstream tools so everyone always has the latest employee information. Pre-conditions/Requirements Prerequisites An active n8n instance (self-hosted or n8n cloud) ScrapeGraphAI community node installed A reachable HRIS API (BambooHR, Workday, Personio, or any custom REST endpoint) Existing Microsoft Teams workspace and a team/channel for announcements A Coda account with an employee directory table A Slack workspace and channel where directory updates will be posted Required Credentials Microsoft Teams OAuth2** – To post adaptive cards or messages Coda API Token** – To insert/update rows in your Coda doc Slack OAuth2** – To push notifications into a Slack channel HTTP Basic / Bearer Token** – For your HRIS REST endpoint ScrapeGraphAI API Key** – (Only required if you scrape public profile data) HRIS Field Mapping | HRIS Field | Coda Column | Teams/Slack Field | |------------|-------------|-------------------| | firstName| First Name| First Name | | lastName | Last Name | Last Name | | email | Email | Email | | title | Job Title | Job Title | | department| Department| Department | (Adjust the mapping in the Set and Code nodes as needed.) How it works This workflow keeps your employee directory perfectly synchronized across your HRIS (or any REST-compatible HR database), Microsoft Teams, Coda docs, and Slack channels. It automatically polls the HR system on a schedule, detects additions or updates, and propagates those changes to downstream tools so everyone always has the latest employee information. Key Steps: Schedule Trigger**: Fires daily (or at your chosen interval) to start the sync routine. HTTP Request**: Fetches the full list of employees from your HRIS API. Code (Delta Detector)**: Compares fetched data with a cached snapshot to identify new hires, departures, or updates. IF Node**: Branches based on whether changes were detected. Split In Batches**: Processes employees in manageable sets to respect API rate limits. Set Node**: Maps HRIS fields to Coda columns and Teams/Slack message fields. Coda Node**: Upserts rows in the employee directory table. Microsoft Teams Node**: Posts an adaptive card summarizing changes to a selected channel. Slack Node**: Sends a formatted message with the same update. Sticky Note**: Provides inline documentation within the workflow for maintainers. Set up steps Setup Time: 10-15 minutes Import the workflow into your n8n instance. Open Credentials tab and create: Microsoft Teams OAuth2 credential. Coda API credential. Slack OAuth2 credential. HRIS HTTP credential (Basic or Bearer). Configure the HRIS HTTP Request node Replace the placeholder URL with your HRIS endpoint (e.g., https://api.yourhr.com/v1/employees). Add query parameters or headers as required by your HRIS. Map Coda Doc & Table IDs in the Coda node. Select Teams & Slack channels in their respective nodes. Adjust the Schedule Trigger to your desired frequency. Optional: Edit the Code node to tweak field mapping or add custom delta-comparison logic. Execute the workflow manually once to verify proper end-to-end operation. Activate the workflow. Node Descriptions Core Workflow Nodes: Schedule Trigger** – Initiates the sync routine at set intervals. HTTP Request (Get Employees)** – Pulls the latest employee list from the HRIS. Code (Delta Detector)** – Stores the previous run’s data in workflow static data and identifies changes. IF (Has Changes?)** – Skips downstream steps when no changes were detected, saving resources. Split In Batches** – Iterates through employees in chunks (default 50) to avoid API throttling. Set (Field Mapper)** – Renames and restructures data for Coda, Teams, and Slack. Coda (Upsert Rows)** – Inserts new rows or updates existing ones based on email match. Microsoft Teams (Post Message)** – Sends a rich adaptive card with the update summary. Slack (Post Message)** – Delivers a concise change log to a Slack channel. Sticky Note** – Embedded documentation for quick reference. Data Flow: Schedule Trigger → HTTP Request → Code (Delta Detector) Code → IF (Has Changes?) If No → End If Yes → Split In Batches → Set → Coda → Teams → Slack Customization Examples Change Sync Frequency // Inside Schedule Trigger { "mode": "everyDay", "hour": 6, "minute": 0 } Extend Field Mapping // Inside Set node items[0].json.phone = item.phoneNumber ?? ''; items[0].json.location = item.officeLocation ?? ''; return items; Data Output Format The workflow outputs structured JSON data: { "employee": { "id": "123", "firstName": "Jane", "lastName": "Doe", "email": "[email protected]", "title": "Senior Engineer", "department": "R&D", "status": "New Hire", "syncedAt": "2024-05-08T10:15:23.000Z" }, "destination": { "codaRowId": "row_abc123", "teamsMessageId": "msg_987654", "slackTs": "1715158523.000200" } } Troubleshooting Common Issues HTTP 401 from HRIS API – Verify token validity and that the credential is attached to the HTTP Request node. Coda duplicates rows – Ensure the key column in Coda is set to “Email” and the Upsert option is enabled. Performance Tips Cache HRIS responses in static data to minimize API calls. Increase the Split In Batches size only if your API rate limits allow. Pro Tips: Use n8n’s built-in Version Control to track mapping changes over time. Add a second IF node to differentiate between “new hires” and “updates” for tailored announcements. Enable Slack’s “threaded replies” to keep your #hr-updates channel tidy.

How It Works Aggregates communication data from Slack, Microsoft Teams, Gmail, GitHub, and Confluence into a single, unified AI-powered analysis workflow designed for quality review and automated documentation updates. This solution is specifically aimed at teams managing distributed content and knowledge workflows across multiple platforms. It addresses the challenges of fragmented communication and isolated information silos that often prevent rapid content review and timely decision-making. The workflow begins with a scheduled trigger, followed by multi-source data collection, merging and normalizing inputs, Claude AI-powered analysis, validation and quality checks, formatting, and finally publishing updates to Notion and Confluence, accompanied by Slack notifications to ensure stakeholders are promptly informed. Setup Steps -Connect credentials: Slack API, Teams, Gmail OAuth, GitHub PAT. -Confluence API, Anthropic API key, Notion Integration. -Configure monitored channels/repositories. -Set schedule frequency. -Map output destinations (Notion/Confluence). -Test merged output before enabling automation. Prerequisites Slack workspace, Teams account, Gmail access, GitHub repository, Confluence space, Anthropic API key, Notion workspace, n8n instance. Use Cases Content review teams processing feedback, documentation teams aggregating updates, QA teams reviewing communications Customization Add/remove source nodes, adjust Claude prompts for analysis type, modify output destinations Benefits Saves 6+ hours weekly, eliminates missed content, AI-driven quality assurance

Auto-Routing Nicereply Feedback to Microsoft Teams by Team and Sentiment Automatically collect client feedback from Nicereply, analyze sentiment, and send it to the right Microsoft Teams channels — smartly split by team, tone, and comment presence. About this Workflow This workflow pulls customer satisfaction feedback from Nicereply, filters out irrelevant or test entries, and evaluates each item based on the team it belongs to and the sentiment of the response (Great, OK, Bad). It automatically routes the feedback to Microsoft Teams — either as a summary in a channel or a direct message — depending on the team's role and whether a comment is included. Perfect for support, delivery, consulting, and documentation teams that want to stay in the loop with customer sentiment. It ensures that positive feedback reaches the teams who earned it, and that negative feedback is escalated quickly to leads or management. Use Cases Send daily customer feedback directly to the responsible teams in MS Teams Automatically escalate negative responses to leads or managers Avoid clutter by filtering out unimportant or test entries Keep internal teams motivated by sharing only the most relevant praise How it works Schedule Trigger Starts the workflow on a set schedule (e.g., daily at 7:00 AM) Get Feedback Pulls customer feedback from Nicereply using survey ID Split Out Processes each feedback entry separately Edit Feedbacks Renames or adjusts fields for easier filtering and readability Change Survey ID Maps internal survey identifiers for accurate team routing (Survey ID can be found in Nicereply: Settings > Surveys > [Survey] > ID) Filter Excludes old responses Code Node Tag unknown clients Change Happiness Value Converts score into “Great”, “OK”, or “Bad” for routing logic Without Comment Checks if feedback includes a text comment or not Send Feedback Without Comment Routes simple feedback (no comment) to MS Teams based on team + score Send Feedback With Comment Routes full feedback with comment to MS Teams for closer review Feedback Routing Logic Each team receives only what’s most relevant: Support, Docs, Consulting* get only Great* feedback to boost morale Team Leads* receive OK and Bad* feedback so they can follow up Management* is only alerted to Bad* feedback for critical response These rules can be freely customized. For example, you may want Support to receive all responses, or Management only when multiple Bad entries are received. The structure is modular and easily adjustable. How to Use Import the workflow Load the .json file into your Easy Redmine automation workspace Set up connections Nicereply API key or integration setup Microsoft Teams integration (chat and/or channel posting) Insert your Survey ID(s) You’ll find these in the Nicereply admin panel under Survey settings Customize team logic Adjust survey-to-team mappings and message routing as needed Edit Teams message templates Modify message text or formatting based on internal tone or content policies Test with real data Run manually and verify correct delivery to MS Teams Deploy and schedule Let it run on its own to automate the feedback cycle Requirements Nicereply account with active surveys Microsoft Teams account with permissions to post to channels or send chats Optional Enhancements Add AI to summarize long comments Store feedback history in external DB Trigger follow-up tasks or alerts for repeated Bad scores Localize messages for multilingual feedback systems Integrate additional tools like Slack, Easy Redmine, etc. Tips for a Clean Setup Keep team routing logic in one place for easy updates Rename all nodes clearly to reflect their function (e.g., Change Happiness Value) Add logging or alerting in case of failed delivery or empty feedback pull Use environment variables for tokens and survey IDs where possible

Overview This n8n workflow provides an automated notification system that monitors tickets in GLPI (Gestionnaire Libre de Parc Informatique) and sends proactive alerts through Microsoft Teams when tickets are approaching their expiration dates. Key Features 🕘 Automated Scheduling Daily execution scheduled at 9:00 AM Continuous monitoring without manual intervention Customizable scheduling configuration 🎯 Intelligent Deadline Detection Automatic identification of tickets expiring within the next 2 days Configurable date-based filtering criteria Efficient processing of multiple simultaneous tickets 👥 Targeted Notifications Personalized alerts sent to specific technicians via Microsoft Teams Automatic assignment based on ticket assignee Structured messages with key ticket information 🔧 Complete GLPI Integration Secure connection through GLPI REST API Authentication with application tokens Automatic session management (initiation and closure) Technical Functionalities Data Processing Extraction: Automatic queries to GLPI database Filtering: Ticket separation by assigned technician Transformation: Data formatting for readable notifications Conditional Flow Automatic evaluation of responsible technician Intelligent notification routing Handling of cases without specific assignment Session Management Automatic session initiation with GLPI Secure session token maintenance Controlled session closure upon completion Ticket Information Included Each alert contains: Ticket Title: Clear problem description Ticket ID: Unique identifier for tracking Time Remaining: Days/hours until expiration System Requirements Infrastructure GLPI server with REST API enabled Running n8n instance Microsoft Teams account with API permissions Required Credentials GLPI user with application administrator privileges Valid GLPI application token OAuth2 credentials for Microsoft Teams GLPI User ID Identification For complete workflow configuration, it's necessary to identify the correct IDs of technical users for proper notification assignment. User IDs can be obtained by accessing user management in GLPI and observing the ID directly in the browser URL when selecting a specific user. Path: Administration > Users > [Select User] When clicking on the desired user, you can see the user ID directly in the browser URL (e.g., id=7 for Support Technician 1, id=8 for Support Technician 2). Configuration Environment Variables json{ "glpi_url": "https://your-glpi-server.com", "app_token": "your-application-token-here" } Available Customization Alert Period**: Modifiable from 2 days to any desired range Execution Schedule**: Configurable according to operational needs Recipients**: Adaptable to specific team structure Operational Benefits For Support Teams Reduction of expired tickets Improved response times Proactive workload management For Organizations Higher SLA compliance Increased customer satisfaction Optimized technical support resources Ideal Use Cases IT Service Centers**: Incident and request management Technical Support Teams**: Critical case tracking Organizations with Strict SLAs**: Service agreement compliance IT Departments**: Internal ticket monitoring Scalability This workflow is designed to: Handle high ticket volumes Adapt to teams of different sizes Integrate with multiple communication channels Expand with additional functionalities Installation and Deployment Import the JSON workflow into n8n Configure GLPI and Microsoft Teams credentials Update configuration variables Activate the scheduled trigger Perform functionality tests This workflow represents a robust and scalable solution for proactive ticket management in enterprise environments, significantly improving operational efficiency and service commitment compliance.

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.

⚙️ Advanced Equipment Health Monitor with MS Teams Integration (n8n | API | Google Sheets | MSTeams) This n8n workflow automatically monitors equipment health by fetching real-time metrics like temperature, voltage and operational status. If any of these parameters cross critical thresholds, an alert is instantly sent to a Microsoft Teams channel and the event is logged in Google Sheets. The workflow runs every 15 minutes by default. ⚡ Quick Implementation Steps Import the workflow JSON into your n8n instance. Open the "Set Config" node and update: API endpoint Teams webhook URL Threshold values Google Sheet ID Activate the workflow to start receiving alerts every 15 minutes. 🎯 Who’s It For Renewable energy site operators (solar, wind) Plant maintenance and operations teams Remote infrastructure monitoring services IoT-integrated energy platforms Enterprise environments using Microsoft Teams 🛠 Requirements | Tool | Purpose | |------|---------| | n8n Instance | To run and schedule automation | | HTTP API | Access to your equipment or IoT platform health API | | Microsoft Teams | Incoming Webhook URL configured | | Google Sheets | Logging and analytics | | SMTP (optional) | For email-based alternatives or expansions | 🧠 What It Does Runs every 15 minutes** to check the latest equipment metrics. Compares values** (temperature, voltage, status) against configured thresholds. Triggers a Microsoft Teams message** when a threshold is breached. Appends the alert data** to a Google Sheet for logging and review. 🧩 Workflow Components Set Node:** Configures thresholds, endpoints, webhook URL and Sheet ID. Cron Node:** Triggers the check every 15 minutes. HTTP Request Node:** Pulls data from your equipment health monitoring API. IF Node:** Evaluates if conditions are within or outside defined limits. MS Teams Alert Node:** Sends structured alerts using a Teams incoming webhook. Google Sheets Node:** Logs alert details for recordkeeping and analytics. 🔧 How To Set Up – Step-by-Step Import Workflow: In n8n, click Import and upload the provided .json file. Update Configurations: Open the Set Config node. Replace the placeholder values: apiEndpoint: URL to fetch equipment data. teamsWebhookUrl: Your MS Teams channel webhook. temperatureThreshold: Example = 80 voltageThreshold: Example = 400 googleSheetId: Google Sheet ID (must be shared with n8n service account). Check Webhook Integration: Ensure your MS Teams webhook is properly authorized and points to a live channel. Run & Monitor: Enable the workflow and view logs/alerts. Adjust thresholds as needed. 🧪 How To Customize | Customization | How | |---------------|-----| | Add more parameters (humidity, pressure) | Extend the HTTP + IF node conditions | | Change alert frequency | Edit the Cron node | | Use Slack or Email instead of Teams | Replace MS Teams node with Slack or Email node | | Add PDF Report Generation | Use HTML → PDF node and email the report | | Export to Database | Add a PostgreSQL or MySQL node instead of Google Sheets | ➕ Add‑ons (Advanced) | Add-on | Description | |--------|-------------| | 📦 Auto-Ticketing | Auto-create issues in Jira, Trello or ClickUp for serious faults | | 📊 Dashboard Sync | Send real-time logs to BigQuery or InfluxDB | | 🧠 Predictive Alerts | Use machine learning APIs to flag anomalies | | 🗂 Daily Digest | Compile all incidents into a daily summary email or Teams post | | 📱 Mobile Alert | Integrate Twilio for SMS alerts or WhatsApp notifications | 📈 Example Use Cases Monitor solar inverter health for overheating or voltage drops. Alert field engineers via Teams when a wind turbine sensor fails. Log and visualize hardware issues for weekly analytics. Automate SLA compliance tracking through timely notifications. Ensure distributed infrastructure (e.g., substations) are always in operational range. 🧯 Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|----------| | No Teams alert | Incorrect webhook URL or formatting | Recheck the Teams webhook and payload | | Workflow not triggering | Cron node misconfigured | Ensure it’s set to run every 15 mins and workflow is active | | Google Sheet not updating | Sheet ID is wrong or not shared | Share Sheet with your n8n Google service account | | No data from API | Endpoint URL is down or wrong | Test the endpoint manually with Postman or browser | 📞 Need Assistance? Need help tailoring this to your exact equipment type or expanding the workflow? 👉 Contact WeblineIndia – Expert automation partners for renewable energy, infrastructure and enterprise workflows.

This Workflow does a HTTPs request to ConnectWise Manage through their REST API. It will pull all tickets in the "New" status or whichever status you like, and notify your dispatch team/personnel whenever a new ticket comes in using Microsoft Teams. Video Explanation https://youtu.be/yaSVCybSWbM

This Template gives the ability to monitor all uplinks for your Meraki Dashboard and then alert your team in a method you prefer. This example is a Teams notification to our Dispatch Channel Setup will probably take around 30 minutes to 1h provided with the Template. Most time intensive steps are getting a Meraki API key which I go over and setting up the Teams node which n8n has good documentation for. Tutorial & explanation https://www.youtube.com/watch?v=JvaN0dNwRNU