Discord and WhatsApp Business Cloud integration

The Error Notification workflow is designed to instantly notify you whenever any other n8n workflow encounters an error, using popular communication channels like Telegram and Gmail—with optional support for Discord, Slack, and WhatsApp. 💡 Why Use Error Notification workflow? Immediate Awareness:** Get instant alerts when workflows fail, preventing unnoticed errors and downtime. Multi-Channel Flexibility:** Notify your team via Telegram, Gmail, and optionally Slack, Discord, or WhatsApp. Detailed Context:** Receive rich error information including the error message, node name, time, and execution link for quicker fixes. Easy Integration:** Built with native n8n nodes and customizable code, simple to adopt without complex setup. Open Source & Free:** Use and adapt this workflow at no cost, making professional error monitoring accessible. ⚡ Who Is This For? n8n Workflow Developers:** Quickly spot and respond to automation issues in development or production. Operations Teams:** Maintain uptime and swiftly troubleshoot errors across multiple workflows. Small to Medium Businesses:** Gain professional error alerting without expensive monitoring tools. Automation Enthusiasts:** Enhance your automation reliability with real-time failure notifications. ❓ What Problem Does It Solve? This workflow embedd error detection and notification directly within your n8n instance. It automates the process of catching errors as they occur, compiling meaningful context, and delivering it instantly via your preferred messaging platforms. This drastically reduces your response time to issues and streamlines error management, improving your automation reliability and operational confidence. 🔧 What This Workflow Does ⏱ Trigger: Listens for any error generated in your n8n workflows using the n8n Error Trigger node. 📎 Step 2: Executes a Code node that formats a detailed error message capturing workflow name, error node, description, timestamp, and an execution URL. 🔍 Step 3: Sends the formatted error notification to multiple communication channels: Telegram and Gmail by default, plus optionally Discord, Slack, and WhatsApp (disabled by default). 💌 Step 4: Delivers rich, parsed HTML-formatted messages to ensure error readability and immediate actionability. 🔐 Setup Instructions Import the provided .json file into your n8n instance (Cloud or self-hosted). Set up credentials: Gmail OAuth credentials for sending emails via Gmail node Telegram API credentials for Telegram notifications (Optional) Discord Webhook URL credential for Discord notifications (Optional) Slack Webhook credential for Slack notifications (Optional) WhatsApp connection credentials (if enabled) Customize the Code node if needed to adjust the error message format or target chat IDs. Update the chat IDs and recipient details in each notification node according to your channels. Test the workflow by manually triggering an error in another workflow to verify proper notifications. 🧩 Pre-Requirements Active n8n instance (cloud or self-hosted) with version supporting Error Trigger node Telegram bot credentials and chat ID (Optional) Gmail, Discord, Slack, or WhatsApp accounts and webhook credentials if you want to use those channels 🛠️ Customize It Further Enable and configure additional notification nodes like Slack or WhatsApp to fit your team's communication style. Customize the error message template in the Code node to include extra metadata or format it differently (e.g., markdown). Integrate with incident management tools via webhook nodes or create tickets automatically on error. 🧠 Nodes Used Error Trigger Code Telegram Gmail Discord (disabled) Slack (disabled) WhatsApp (disabled) Sticky Note (for description) 📞 Support Made by: khaisa Studio Tag: notification,error,monitoring,workflow,automation,alerts Category: Monitoring & Alerts Need a custom? Need a custom? contact me on LinkedIn or Web

Notion Status-Based Alert Template Who is this for? Teams that live in Notion and want an instant ping to the right person when a task changes state. Perfect for content creators, project managers, or any small team that tracks work in a Notion database and prefers Slack / Telegram / Discord / e-mail notifications over manually checking a board. What problem does this solve? Polling Notion or checking a kanban board is slow and error-prone. This workflow watches a Notion database and routes an alert to specific people based on the item’s Status. One central map decides who gets pinged for “On Deck”, “In Progress”, “Ready for Review”, or “Ready to Publish”. How it works Trigger – choose either method Polling (Notion Trigger) – fires every minute. Push (Webhook) – register the production URL in a Notion automation and disable polling. Set Notion Page Info – copies Title, Status, URL, etc. into top-level fields. Switch (Status router) – routes the item down a branch that matches its Status. Set-Mention nodes – one per Status. Each node sets a single field mention (e.g. <@U123456>). Add or edit these nodes to map new statuses or recipients. Build Message – assembles a rich text block: Task title Status: <@UserIDs> <Notion URL|Open in Notion> Send nodes – Slack (active) + optional Telegram / WhatsApp / Discord / Email (disabled by default). All reuse the same {{$json.message}}. Setup steps Import this template into n8n. Connect credentials Notion API token Slack OAuth (and any other channels you enable) Edit the Status → Mention map Open each Set-Mention node and replace the placeholder with the real Slack ID / chat ID / phone / email. Copy a node for every extra Status you use, wire it to a new Switch output, and update the value. Set environment variables (recommended) NOTION_DB_ID, SLACK_CHANNEL, EMAIL_FROM, etc. Pick your trigger style Keep polling enabled or disable it and enable the Webhook, then register the webhook URL in Notion. Test – change a task’s Status in Notion → watch Slack for the ping. Example output > Title: “Draft blog post – AI productivity” > Status: Ready for Review > Slack message: > > Draft blog post – AI productivity > Status: Ready for Review > <@U789012> > <https://www.notion.so/…|Open in Notion> > Extending the flow Wire additional channels after Build Message—they all consume the same {{$json.message}}. Add richer logic (e.g. due-date reminders) in the Set Notion Page Info node. Verify Notion webhook signatures in a Function node if you rely on push triggers. This template is the leanest possible setup: one table of statuses → direct pings to the right people. Swap the IDs, flip on your favourite channels, and ship.

This workflow automatically summarizes your team's daily meetings from multiple Google Calendars daily at 9AM and sends the digest to your preferred communication channels. It uses AI to identify and format meeting details, making it easy to see your schedule at a glance. Good to Know Multi-Calendar Support**: This workflow is designed to pull events from any number of Google Calendars you've connected, providing a single, consolidated summary. AI-Powered Summaries**: The AI Agent, powered by Google Gemini, is instructed to format the output with key details like title, time, duration, and a link to join the meeting. This saves you from sifting through calendar invites. How It Works A Schedule Trigger starts the workflow at a set time each day e.g at 9 AM (or any other time you choose). An AI Agent with access to the Google Calendar tool is prompted to fetch today's events from all connected calendars. The Google Calendar nodes retrieve all meetings for the current day. The AI Agent processes this information and generates a clean, structured summary. Finally, the formatted summary is sent to your team's chosen communication platforms: Slack, Discord, and WhatsApp. How to Use Set the Schedule: Adjust the Schedule Trigger to run at a time that works best for your team—for example, every morning before the workday begins. Connect Your Accounts: Add your Google Calendar credentials to connect all the calendars you want to monitor. Choose Your Channels: Connect the appropriate Slack, Discord, and/or WhatsApp nodes and configure them to send the message to your desired channels or groups. Requirements Google Gemini account**: A Google Gemini account is needed for the AI Agent and Chat Model to function. Google Calendar account(s)**: You'll need to connect the Google Calendar accounts you wish to pull data from. Communication platform account(s)**: Credentials for the communication apps you want to use (Slack, Discord, WhatsApp). Customizing This Workflow Modify the Trigger: You can change the **Schedule Trigger to a different interval or even trigger the workflow manually with a webhook. Adjust the AI Prompt**: Fine-tune the AI Agent's prompt to change the summary format, include more details, or even ask it to highlight the most important meetings of the day. Add More Platforms**: Easily add more communication nodes to send the daily summary to other platforms like Microsoft Teams, email, or even a custom CRM.

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.