Centralized error monitoring & alerts via Telegram, Slack & other messengers
Who is this for?
This workflow is designed for developers, DevOps engineers, and automation specialists who manage multiple n8n workflows and need a reliable way to monitor for failures and receive alerts in real time.
What problem is this workflow solving?
Monitoring multiple workflows can be challenging, especially when silent failures occur. This workflow helps ensure you're immediately informed whenever another workflow fails, reducing downtime and improving system reliability.
What this workflow does
The solution consists of two parts: ERROR NOTIFIER: A centralized workflow that sends alerts through your chosen communication channel (e.g., Telegram, WhatsApp, Gmail). ERROR ALERTER: A node snippet to be added to any workflow you want to monitor. It captures errors and triggers the ERROR NOTIFIER workflow. Once set up, this system provides real-time error alerts for all integrated workflows.
Setup
-
Import both workflows:
- ERROR NOTIFIER (centralized alert handler)
- ERROR ALERTER (to be added to your monitored workflows)
-
Add credentials for your preferred alert channel:
- WhatsApp (OAuth or API)
- Telegram
- Gmail
- Discord
- Slack
-
Activate the workflows:
- Ensure ERROR NOTIFIER is active and ready to receive triggers.
- Paste ERROR ALERTER at the end of each workflow you want to monitor, connecting it to the error branch.
Sign up for a free consultation and find out how n8n can help you.
Centralized Error Monitoring and Alerts via Multiple Messengers
This n8n workflow provides a robust and centralized system for monitoring errors across your n8n instance and delivering immediate notifications to various communication channels. It acts as a dedicated error handling mechanism, ensuring that no critical workflow failure goes unnoticed.
What it does
This workflow is designed to be triggered by any failing workflow within your n8n instance. Upon an error, it collects the error details and then dispatches alerts to multiple configured messaging services, providing comprehensive coverage for your error notifications.
- Listens for Workflow Errors: The workflow is initiated whenever another n8n workflow execution fails.
- Collects Error Details: It automatically captures detailed information about the failed workflow, including its name, ID, error message, and execution details.
- Sends Alerts to Multiple Messengers: It is pre-configured to send error notifications to:
- Slack: Posts a detailed error message to a specified Slack channel.
- Telegram: Sends an error alert to a Telegram chat.
- Discord: Dispatches an error message to a Discord channel.
- Gmail: Sends an email with error details.
- WhatsApp Business Cloud: Sends an error notification via WhatsApp.
- Supports Sub-workflows for Advanced Logic: Includes an "Execute Sub-workflow" node, allowing for modular error handling logic or more complex notification strategies if needed.
- Includes a Code Node: Provides a "Code" node for custom JavaScript logic, enabling advanced data manipulation or conditional routing of error messages.
Prerequisites/Requirements
To use this workflow effectively, you will need:
- n8n Instance: An active n8n instance where this workflow will be imported and run.
- Slack Account: A Slack workspace and a bot token or webhook URL for sending messages.
- Telegram Bot: A Telegram bot token and chat ID to which messages will be sent.
- Discord Webhook: A Discord webhook URL for posting messages to a channel.
- Gmail Account: A configured Gmail credential in n8n for sending emails.
- WhatsApp Business Cloud Account: A configured WhatsApp Business Cloud credential in n8n.
Setup/Usage
- Import the Workflow:
- In your n8n instance, navigate to "Workflows".
- Click "New" or "Import from JSON".
- Paste the provided JSON into the import dialog.
- Configure Credentials:
- For each messaging node (Slack, Telegram, Discord, Gmail, WhatsApp Business Cloud), you will need to set up the respective credentials in n8n.
- Click on each messaging node and select or create a new credential. Follow the n8n documentation for each app node to correctly configure them (e.g., Slack Bot Token, Telegram Bot API Key, Discord Webhook URL, Gmail OAuth).
- Activate as an Error Workflow:
- After importing and configuring, save the workflow.
- Go to "Settings" in your n8n instance.
- Under "Error Workflow", select this workflow from the dropdown list. This will ensure that whenever any other workflow fails, this error handling workflow is triggered.
- Customize Notifications (Optional):
- You can modify the message content in each messaging node to include specific error details from the "Error Trigger" node's output (e.g.,
{{ $json.workflow.name }},{{ $json.error.message }}). - The "Code" node can be used to format messages, filter errors, or add custom logic before sending notifications.
- The "Execute Sub-workflow" node can be linked to another workflow for more complex error processing (e.g., logging to a database, attempting a retry).
- You can modify the message content in each messaging node to include specific error details from the "Error Trigger" node's output (e.g.,
- Test the Workflow:
- To test, create a simple workflow that is designed to fail (e.g., an HTTP Request node to a non-existent URL).
- Execute that failing workflow. This error monitoring workflow should then trigger and send notifications to your configured channels.
Related Templates
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
By Daniel NkenchoAuto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.
By gotoHumanSynchronizing WooCommerce inventory and creating products with Google Gemini AI and BrowserAct
Synchronize WooCommerce Inventory & Create Products with Gemini AI & BrowserAct This sophisticated n8n template automates WooCommerce inventory management by scraping supplier data, updating existing products, and intelligently creating new ones with AI-formatted descriptions. This workflow is essential for e-commerce operators, dropshippers, and inventory managers who need to ensure their product pricing and stock levels are synchronized with multiple third-party suppliers, minimizing overselling and maximizing profit. --- Self-Hosted Only This Workflow uses a community contribution and is designed and tested for self-hosted n8n instances only. --- How it works The workflow is typically run by a Schedule Trigger (though a Manual Trigger is also shown) to check stock automatically. It reads a list of suppliers and their inventory page URLs from a central Google Sheet. The workflow loops through each supplier: A BrowserAct node scrapes the current stock and price data from the supplier's inventory page. A Code node parses this bulk data into individual product items. It then loops through each individual product found. The workflow checks WooCommerce to see if the product already exists based on its name. If the product exists: It proceeds to update the existing product's price and stock quantity. If the product DOES NOT exist: An If node checks if the missing product's category matches a predefined type (optional filtering). If it passes the filter, a second BrowserAct workflow scrapes detailed product attributes from a dedicated product page (e.g., DigiKey). An AI Agent (Gemini) transforms these attributes into a specific, styled HTML table for the product description. Finally, the product is created in WooCommerce with all scraped details and the AI-generated description. Error Handling: Multiple Slack nodes are configured to alert your team immediately if any scraping task fails or if the product update/creation process encounters an issue. Note: This workflow does not support image uploads for new products. To enable this functionality, you must modify both the n8n and BrowserAct workflows. --- Requirements BrowserAct API account for web scraping BrowserAct n8n Community Node -> (n8n Nodes BrowserAct) BrowserAct templates named “WooCommerce Inventory & Stock Synchronization” and “WooCommerce Product Data Reconciliation” Google Sheets credentials for the supplier list WooCommerce credentials for product management Google Gemini account for the AI Agent Slack credentials for error alerts --- Need Help? How to Find Your BrowseAct API Key & Workflow ID How to Connect n8n to Browseract How to Use & Customize BrowserAct Templates How to Use the BrowserAct N8N Community Node --- Workflow Guidance and Showcase STOP Overselling! Auto-Sync WooCommerce Inventory from ANY Supplier
By Madame AI Team | Kai