Workflow Templates

This workflow uses a WooCommerce trigger that will run when an order has been updated and the status is refunded. If the value of this is over 100 it will post it to a Slack channel. To use this workflow you will need to set the credentials to use for the WooCommerce and Slack nodes, You will also need to pick a channel to post the message to.

Automated YouTube to MP3 Conversion and Storage with Google Sheets This automated workflow allows seamless conversion of YouTube videos to MP3, using the YouTube to MP3 Downloader API. The converted MP3 files are uploaded to Google Drive, and all relevant conversion data like download links and file sizes are logged in Google Sheets. Ideal for content creators and download enthusiasts, it enhances efficiency and accuracy in handling YouTube-to-MP3 conversions. Node-by-Node Explanation: On form submission Triggers the workflow when a user submits a YouTube video URL for conversion. HTTP Request Sends a POST request to the YouTube to MP3 Downloader API to initiate the conversion of the YouTube URL to MP3 format. Google Drive Uploads the converted MP3 file to Google Drive for cloud storage. Google Sheets (Initial Log) Logs initial details such as URL and status in Google Sheets before the conversion is complete. Google Sheets (Final Log) After successful conversion, logs the download link, file size, and other relevant data in Google Sheets. If Condition Filters the process to only proceed if the conversion status is "done." Wait Pauses the workflow until the conversion process is completed. Code Converts file size from bytes to megabytes (MB) for easier reference in Google Sheets. Download MP3 Triggers the MP3 file download once the conversion is finished. Problem Solved: Converting YouTube videos to MP3 manually is time-consuming and tedious. The process involves multiple steps, such as downloading the video, extracting audio, and organizing the files, which can be a hassle, especially if you need to do it frequently. Additionally, managing and tracking these files and their statuses can be chaotic, leading to disorganization. This workflow automates the entire process: Conversion automation**: No need for third-party apps or websites to handle YouTube-to-MP3 conversion. Efficient tracking**: All conversion details (file size, download link, etc.) are logged in Google Sheets, keeping everything organized. Cloud storage**: Directly stores converted MP3s in Google Drive, ensuring files are secure, easy to access, and well-managed. By leveraging the YouTube to MP3 Downloader API, this workflow removes all the manual steps, allowing you to save time and effort while keeping everything organized. Benefits of the Flow: Time-Saving Automation: Automatically converts YouTube videos to MP3 using the **YouTube to MP3 Downloader API, eliminating the need for manual conversion. Data Logging**: Automatically logs essential conversion details (like file size, download link, etc.) in Google Sheets for easy reference. Cloud Storage Integration**: Converted MP3 files are directly uploaded to Google Drive for secure, cloud-based storage. No Hassle**: Eliminates the need for third-party tools or manual tracking of conversions. Use Cases: Content Creators If you’re a YouTuber or a podcast creator, you might need to convert and store multiple audio files for your content. This workflow can help by automatically converting YouTube videos or podcasts to MP3 and saving them to Google Drive, all while keeping a detailed log in Google Sheets. Educators and Trainers Teachers or trainers often use YouTube videos for educational purposes and might want to extract the audio (e.g., for podcasts or lectures). With this automation, they can easily convert YouTube content into MP3 format for use in offline teaching or sharing with students. Social Media Managers Social media managers working with audio content can use this workflow to quickly convert YouTube videos to MP3 files and upload them to Google Drive for easy sharing with their team or posting on social platforms. Music Enthusiasts Music lovers who want to save YouTube music videos or tracks into MP3 format for personal use or offline listening can benefit from this automated conversion process. The workflow makes it fast and easy to convert, store, and track MP3 files. Content Archivists If you’re working on archiving online media or curating content libraries, this system allows for quick and efficient conversion, storing, and cataloging of YouTube videos in MP3 format with all relevant metadata stored in Google Sheets for easy management. Create your free n8n account and set up the workflow in just a few minutes using the link below: 👉 Start Automating with n8n Save time, stay consistent, and grow your LinkedIn presence effortlessly!

This is a workflow for a Telegram-echo bot. This bot is useful for debugging and learning purposes of the Telegram platform. Add your Telegram bot credentials for both nodes. Activate the workflow. Send data to the bot (i.e. a message, a forwarded message, sticker, emoji, voice, file, an image...). Second node will fetch the incoming JSON object, format it and send back.

Use case Error workflows are an important part of running workflows in production. Get alerts for errors directly in your inbox. How to setup Add your Gmail creds Add your target email Add this error workflow to other workflows docs here

A workflow to receive weather updates on demand using a Telegram bot. The workflow is triggered using the Telegram Trigger node by issuing a message to the Telegram bot. The OpenWeatherMap node queries the weather API and returns the result using the Telegram node.

Check email and create new Nextcloud Deck card from incoming email. Import workflow. Change Nextcloud URL with target board id and stack id. Configure IMAP credential and Nextcloud userid / password. The workflow starts with new IMAP email. This workflow creates new Nextcloud Deck Card with email subject and email body. (Note that all the emails will be marked as read.)

🤖 AI-Powered Gmail MCP Server for n8n Description This n8n workflow template leverages an external AI Model Control Plane (MCP) Server to automate various Gmail tasks, such as composing emails, replying to threads, and handling follow-ups using dynamically generated content. It uses the native n8n Gmail nodes available from v1.88.0 onwards. Who is this template for? Ideal for developers, automation engineers, and power users using self-hosted n8n (v1.88.0+) who want to integrate artificial intelligence directly into their email workflows via a dedicated MCP Server for enhanced control and customization over AI interactions. What problem does this workflow solve? ⚙️ Reduces Manual Effort: Decreases the work involved in writing, sending, and following up on emails in Gmail. ✅ Consistency and Quality: Ensures standardized, professional responses free from typos by leveraging controlled AI prompts. 🔄 Complete Automation: Automates the entire email cycle: from the initial send, through waiting for a reply, to sending automated follow-ups based on AI logic. Workflow Overview This template provides a structured approach to integrating Gmail with an MCP Server: 📡 MCP Trigger (“MCP_GMAIL”): An n8n Webhook node that receives HTTP calls from your MCP Server. It standardizes the inputs (like recipient, subject, AI prompt) for all subsequent Gmail nodes. (You will need to configure your MCP Server to call this webhook URL). 📤 SEND_EMAIL (Gmail Node v2.1): Sends new messages. The email body (message field) is typically populated by content generated from an AI prompt processed by your MCP server and passed via the trigger. 🔄 REPLY_EMAIL (Gmail Node v2.1): Automatically replies to existing conversations (threads). It uses AI-generated content (via MCP) to formulate the reply based on the thread context. Requires Message ID and/or Thread ID. 📥 GET_EMAIL (Gmail Node v2.1): Fetches data for a specific message (using Message ID) for analysis, processing, or archiving. Useful for retrieving context before replying. ⏳ SEND_AND_WAIT (Gmail Node v2.1): Sends an email and pauses the workflow execution until a reply is received in that specific conversation (thread). This is crucial for building automated follow-up sequences. It then outputs data from the reply message. Note:* All Gmail nodes in this template use the native n8n *Gmail Tool*, integrated since v1.88.0. No additional installation of community nodes is required. See the official n8n documentation for more details on node configuration. Prerequisites Ensure you have the following before importing: 🚀 A self-hosted n8n instance running version 1.88.0 or higher. ☁️ A Google Cloud project with the Gmail API correctly enabled. 🔑 Gmail OAuth2 credentials configured in your n8n instance. Navigate to Settings > Credentials > New > Google > Gmail (OAuth2 API) to set this up if you haven't already. 🧠 Access to your MCP Server and an API Key (or other authentication method) required to interact with it via HTTP requests. How to Import and Configure Follow these steps to get the template running: In your n8n interface, navigate to Templates → Import from URL. Paste the JSON link provided for this workflow template. Configure the necessary credentials within n8n under Credentials: Gmail OAuth2: Select the Google OAuth2 credential you previously configured that has access to the desired Gmail account. MCP API Key: You'll likely need to configure credentials for interacting with your MCP Server. This might involve setting up a Header Auth credential in n8n with your MCP API Key, or configuring the HTTP Request node within the workflow directly, depending on your MCP's authentication scheme. Link this credential where needed (e.g., in the Trigger node if MCP calls n8n with auth, or in HTTP Request nodes if n8n calls MCP). Activate the Workflow: Ensure the workflow toggle is set to "Active" in the top right corner. Webhook URL: Copy the Webhook URL from the "MCP_GMAIL" Trigger node (Test or Production URL as needed) and configure your MCP Server to send requests to this URL. Recommendation: Rename the nodes with clear, descriptive names relevant to your specific use case (e.g., ✨ Generate Sales Email Body via MCP, 📥 Fetch Customer Replies). Utilize the workflow notes (sticky notes on the canvas) to document specific logic, prompt details, or configuration choices for future reference. Customization & Technical Guidance Tailor the workflow to your specific needs: 🔍 Search Filters: In nodes that fetch emails (like GET_EMAIL or if you add a Gmail - Get Many node), refine the search using the Search field (standard Gmail search operators) or filter by Label Names to process specific emails (e.g., unread from a specific sender, emails with a certain label). ✍️ AI Fine-Tuning (Prompt Engineering): The core of the AI integration happens in the prompts sent to your MCP Server. Modify these prompts (often constructed within function nodes or directly in the trigger input expected from MCP) in the message or body fields passed to the send/reply nodes. Adjust prompts to control: Tone & Style: Formal, informal, empathetic, technical, etc. Content & Format: Request bullet points, summaries, specific data extraction. Dynamic Variables: Inject data from previous n8n nodes (e.g., customer name, order details, previous email content) into the prompt for context-aware generation. Example: `"Reply to the following email thread [{{ $json.thread_content }}] addressing the customer {{ $json.customer_name }} about their query..."` 🔗 Post-Response Actions: Extend the workflow after key actions, especially the SEND_AND_WAIT node. Add nodes to: Log results to a database (MySQL, PostgreSQL, Airtable). Update CRM records (HubSpot, Salesforce). Send notifications (Slack, Discord, Telegram). Trigger other n8n workflows. 🛡️ Error Handling: Implement robust error handling. Connect the red output pins (error output) of critical nodes (like Gmail nodes or HTTP Requests to MCP) to an Error Trigger node. From there, you can: Log detailed error information to a monitoring tool or spreadsheet. Send failure notifications. Implement retry logic (using loops or specific retry settings on nodes). Route to alternative paths or fallback workflows.

Email Personal Assistant - Comprehensive Communication Manager This automation flow is designed to proactively monitor email, calendar, and Slack communications, analyze priorities across all channels, and generate a comprehensive daily briefing with actionable tasks for executive productivity management. ⚙️ How It Works (Step-by-Step): ⏰ Automated Daily Trigger Runs automatically on weekdays: Scheduled execution every weekday at 8:00 AM Manual trigger available for on-demand analysis Comprehensive daily communication audit 📧 Email Assistant Agent Analyzes inbox priorities and context: Scans unread emails across "To Respond" and "FYI" labels Checks email history to determine relationship context Identifies *company-related opportunities and partnerships Categorizes emails by urgency (High, Medium, Low) Cross-references with sent emails for follow-up context 📅 Follow-Up Assistant Agent Monitors meeting follow-up requirements: Reviews last 3 days of calendar meetings Fetches Fireflies transcripts for recorded sessions Identifies meetings without post-meeting communication Flags meetings requiring action items or follow-ups Checks sent emails and Slack for completed follow-ups 💬 Slack Assistant Agent Tracks Slack communication priorities: Monitors direct messages and @mentions Identifies unreplied Slack conversations Cross-references with email and calendar context Prioritizes responses based on sender importance Checks for threaded conversations requiring attention 🎯 Master Orchestrator Agent Synthesizes all communication data: Combines reports from all three assistant agents Cross-references with existing Google Sheets to-do list Prioritizes tasks by urgency and business impact Identifies correlations between different communication channels Creates comprehensive daily action plan 📊 Task Management Integration Automated tracking and delivery: Appends new tasks to Google Sheets to-do tracker Sends personalized daily briefing via Slack DM Maintains conversation memory for context continuity Tracks outstanding vs. completed items 🛠️ Tools Used: n8n: Workflow orchestration and scheduling Claude Sonnet 4 & Opus 4: Multi-agent AI analysis Gmail API: Email monitoring and history checking Google Calendar: Meeting tracking and scheduling Slack API: Message monitoring and user management Fireflies API: Meeting transcript analysis Google Sheets: Task tracking and persistence 📦 Key Features: Multi-channel communication monitoring (Email, Calendar, Slack) AI-powered priority assessment and context analysis Cross-platform relationship tracking and history Automated daily briefing generation and delivery Persistent task tracking with Google Sheets integration Meeting follow-up verification and flagging Conversation memory for continuity across sessions 🚀 Ideal Use Cases: C-level executives managing multiple communication channels Sales leaders tracking prospect interactions and follow-ups Business development professionals managing partnerships Busy professionals needing communication prioritization Teams requiring systematic follow-up management Anyone wanting automated daily productivity briefings `

Este workflow te permite crear un Bot para dar la Bienvenida y despedida en tu grupo de telegram. How To, Paso a Paso: https://comunidad-n8n.com/construye-tu-bot-con-n8n Comunidad de telegram: https://t.me/comunidadn8n

This workflow allows you to add new leads in Lemlist from Airtable. Airtable node: This node lists all the emails that are stored in your Table. You may have the email addresses stored in a Google Sheet, CRM, or database. Replace the Airtable node with the respective node to get the list of the email addresses. Lemlist node: This node creates new leads for a campaign in Lemlist taking the information from the previous node. Lemlist1 node: This node returns the information of a lead from Lemlist.

This workflow uses a WooCommerce trigger that will run a new product has been added, It will then post the product to Telegram and Twitter. To use this workflow you will need to set the credentials to use for the WooCommerce, Twitter and Telegram nodes.

A goal for 2022 is to write 1 thing I do each day. Combined with this workflow you will get daily messages via Telegram and when you reply to them they will be saved in a Google Sheet. Note: Make sure to configure your Telegram and Google Sheet credentials! You will also need to modify the functions to have your Telegram username and bot name.*