Workflow Templates

Streamline data from an n8n form into Google Sheet Airtable and and Email Sending Video for workflow process This workflow facilitates efficient data collection and management by leveraging the capabilities of various nodes within the n8n platform. It commences with the n8n Form Trigger node, where users provide their name, location, and email address. Subsequently, the data seamlessly flows through nodes like Google Sheets, Code, Set, Airtable, Gmail, and Gmail1 for processing and storage. n8n Form Trigger:** Gathers user input data, including Name, City, and Email. Google Sheets:** Manages data operations related to Google Sheets. Code:** Executes JavaScript code to manipulate data fields. Set:** Formats and sets data values for further processing. Airtable:** Facilitates data operations specific to Airtable. Gmail:** Sends custom emails to the provided Email address. Gmail:** Sends additional emails using different templates. Each node within the workflow performs specialized tasks such as extracting date and time fields, formatting data, appending it to Google Sheets and Airtable, and sending personalized emails to the submitter. This streamlined process ensures effective handling of collected information and enhances overall data management efficiency. Workflow Description: n8n Form Trigger: A trigger node that initiates the workflow upon form submission. Captures essential user details like Name, City, and Email. Extracting Date and Time Fields from 'submittedAt' Field: Utilizes a code node to extract Date and Time information from the submitted data. Format the Fields: Standardizes the format of extracted fields (Name, City, Date, Time, Email) for consistency. Airtable: Creates a new record in Airtable with the formatted data. Includes columns for Name, City, Email, Time, and Date. Google Sheets: Appends the formatted data to a designated Google Sheet. Includes columns for Name, City, Email, Date, and Time. Gmail: Sends an email to the provided Email address with a customized message. Subject: "Testing Text Message Delivery" Message: Personalized content with a Name placeholder. Gmail1: Sends another email using a different template. Subject incorporates the Date field for variation. Message content tailored to the subject line. Workflow Connections: n8n Form Trigger -> Extracting Date and Time Fields -> Format the Fields -> Google Sheets & Airtable -> Gmail Google Sheets -> Gmail1 This comprehensive workflow efficiently collects user data, processes it to extract Date and Time fields, stores the formatted information in Google Sheets and Airtable, and delivers tailored emails to the recipients. Copy these templates to get started : Google Sheet Airtable Links to Node Documentation: n8n Form Trigger Documentation Code Node Documentation Set Node Documentation Airtable Node Documentation Google Sheets Node Documentation Gmail Node Documentation

n8n Workflow: Exponential Backoff for Google APIs Overview This n8n workflow implements an Exponential Backoff mechanism to handle retries when interacting with Google APIs. It ensures that failed API requests are retried with increasing delays, up to a specified maximum retry count. This approach helps mitigate transient errors (e.g., rate limits or temporary network issues) while maintaining workflow efficiency. Key Features: Exponential Backoff Logic**: Dynamically increases wait time between retries based on the retry count. Error Handling**: Stops the workflow and raises an error after a specified number of retries. Dynamic Waiting**: Waits for a calculated duration before each retry. Scalable Design**: Modular nodes for easy debugging and customization. Workflow Details Nodes in the Workflow: Trigger (When clicking "Test Workflow"): Manually starts the workflow for testing. Loop Over Items: Iterates over multiple input items to process Google API requests row by row. Google API Node (Example: Update Sheet): Sends a request to a Google API endpoint (e.g., updating a row in Google Sheets). On success: Moves to the next item in the loop. On error: Passes the error to the Exponential Backoff node. Exponential Backoff: Calculates the delay for the next retry based on the retry count. Logic: const retryCount = $json["retryCount"] || 0; const maxRetries = 5; const initialDelay = 1; // in seconds if (retryCount < maxRetries) { const currentDelayInSeconds = initialDelay * Math.pow(2, retryCount); return { json: { retryCount: retryCount + 1, waitTimeInSeconds: currentDelayInSeconds, status: 'retrying', } }; } else { return { json: { error: 'Max retries exceeded', retryCount: retryCount, status: 'failed' } }; } Wait: Dynamically waits for the waitTimeInSeconds value calculated in the Exponential Backoff node. Configuration: Resume: After Time Interval Wait Amount: {{ $json["waitTimeInSeconds"] }} Unit: Seconds Check Max Retries: Evaluates whether the retry count has exceeded the maximum limit. Routes the workflow: True: Passes to the Stop and Error node. False: Loops back to the Google API node for retry. Stop and Error: Stops the workflow and logs the error when the maximum retry count is reached. Parameters Configurable Settings: Max Retries: Defined in the Exponential Backoff node (const maxRetries = 5). Adjust this value based on your requirements. Initial Delay: The starting wait time for retries, defined as 1 second. Google API Configuration: Ensure your Google API node is properly authenticated and configured with the desired endpoint and parameters. How to Use Import the Workflow: Copy the workflow JSON and import it into your n8n instance. Configure Google API Node: Set up the Google API node with your credentials and target API endpoint (e.g., Google Sheets, Gmail, etc.). Test the Workflow: Manually trigger the workflow and observe the retry behavior in case of errors. Monitor Logs: Use the console logs in the Exponential Backoff node to debug retry timings and status. Example Scenarios Scenario 1: Successful Execution The Google API processes all requests without errors. Workflow completes without triggering the retry logic. Scenario 2: Transient API Errors The Google API returns an error (e.g., 429 Too Many Requests). The workflow retries the request with increasing wait times. Scenario 3: Maximum Retries Exceeded The workflow reaches the maximum retry count (e.g., 5 retries). An error is raised, and the workflow stops. Considerations Jitter: This workflow does not implement jitter (randomized delay) since it's not required for low-volume use cases. If needed, jitter can be added to the exponential backoff calculation. Retry Storms: If multiple workflows run simultaneously, ensure your API quotas can handle potential retries. Error Handling Beyond Max Retries: Customize the Stop and Error node to notify stakeholders or log errors in a centralized system. Customization Options Adjust the maximum retry limit and delay calculation to suit your use case. Add additional logic to handle specific error codes differently. Extend the workflow to notify stakeholders when an error occurs (e.g., via Slack or email). Troubleshooting Retry Not Triggering**: Ensure the retryCount variable is passed correctly between nodes. Confirm that the error output from the Google API node flows to the Exponential Backoff node. Incorrect Wait Time**: Verify the Wait node is referencing the correct field for waitTimeInSeconds. Request for Feedback We are always looking to improve this workflow. If you have suggestions, improvements, or ideas for additional features, please feel free to share them. Your feedback helps us refine and enhance this solution!

This template is designed for community managers, developers, and enthusiasts who want to monitor and capture discussions on the n8n community forum by specific keywords. By tracking new topics that match your provided keyword, the workflow automatically logs them into a Google Sheet, helping you keep a pulse on trending discussions and manage community insights effortlessly. How it Works Keyword Monitoring: The workflow continuously monitors the n8n community forum for new topics containing your specified keyword. Data Extraction: When a matching topic is found, relevant details such as id, title, URL, and posting time are extracted. Google Sheets Integration: The extracted information is automatically appended as a new row in your Google Sheet, providing an organized log of community discussions. Alert Option: Optionally, you can add notifications (e.g., Slack messages or emails) to alert you when a new topic is captured, ensuring you never miss an important update. Set Up Steps Import the Workflow: Download and import the workflow into your n8n instance. Configure Keyword Monitoring: In the HTTP Request node, set your desired keyword to filter the n8n community topics. Set Up Google Sheets: Connect your Google Sheets account and specify the target sheet where the new topics should be logged. Customize Data Fields: Adjust the data extraction node parameters if you wish to capture additional details from each topic. Deploy and Test: Deploy the workflow and perform a test run to confirm that new topics matching the keyword are correctly added to your Google Sheet. Set Up Messaging Channels (Optional): Connect to Slack, Email or other providers to get instant messages when new topics are added into your Google Sheet. This template streamlines the process of tracking community discussions, ensuring you have timely and organized insights to enhance your community engagement and strategic decision-making. Enjoy seamless monitoring and easy data management with this ready-to-use n8n workflow template!

This tutorial demonstrates the creation of the HTML report via Markdown node. The main idea is to prepare a very long gext variable via the Function Node and then convert it to the HTML file. The resulting report can be downloaded from the workflow canvas directly or send via email as an attachment.

This workflow illustrates how HTML reports can be created using Markdown Node. An example data consists of a Time Sheet table for 2 persons. Based on this table a markdown document is generated using Function Node. After that a final HTML report is created and is saved as binary file. This file can be either downloaded directly from the workflow canvas or sent as an email attachement.

About The Post to X Automation Seamlessly automate posting to X using Airtop and Make. How to Automate Posting to X with Airtop Consistently engaging your audience on X (formerly Twitter) can be a challenge, particularly when done manually. Developers and automation engineers often struggle with repetitive tasks like scheduling tweets, maintaining consistent posting cycles, and integrating content from various sources or AI-generated feeds. Manually managing content updates increases fatigue, human error, and decreases scalability. This n8n automation, powered by Airtop, simplifies automated content publishing onto X. Whether you're sharing daily updates, integrating dynamically generated AI content, or streamlining your marketing content pipeline, Airtop’s automation helps eliminate manual labor and reduces potential execution errors. Who is this Automation for? Social Media Managers scheduling recurring or automated posts on X Content Marketers integrating AI-generated content into their publishing process Developers implementing automated social media pipelines Automation Engineers minimizing errors and manual posting efforts Key Benefits Real-time, authenticated API postings via X Reliable structured workflows minimize manual errors Seamless integration with AI content pipelines Use Cases Automatically publish scheduled daily content updates Seamlessly post AI-generated insights, news summaries or industry updates Distribute alerts and event announcements reliably at set intervals Maintain active audience engagement by automating regular, high-frequency posts How the Post to X Automation Works This Airtop automation works by using your Airtop Profile signed-in into X via Airtop. Once authenticated securely with your X credentials, n8n handles the structured data flow, which can come from manual inputs, AI-generated sources, databases, or RSS feeds. Airtop then securely publishes the posts, providing reliable scheduled updates directly on X, removing manual oversight and streamlining your social media workflows. What You’ll Need An Airtop API key Your X (Twitter) account An Airtop Profile signed into X Setting Up the Automation Connect your Airtop account using your free Airtop API key Create an Airtop Profile and connect it to your X account Activate and schedule your scenario to automate regular posting Customize the Automation Customize your posting workflow extensively using Airtop's built-in node in n8n: Integrate diverse sources like RSS feeds and AI tools to dynamically customize automated posts Schedule precise posting intervals or diversify times for maximum audience engagement Set conditional logic to automate content posting based on predefined triggers and events Utilize Airtop’s structured data flows to manage categories, hashtags, or mentions in your posts Automation Best Practices Consistently update security credentials for uninterrupted access Clearly structure your workflow to simplify troubleshooting and logic updates Monitor posting frequency to ensure optimal audience reach and engagement Regularly review content sources to maintain quality control of automated postings Happy Automating!

This n8n workflow automatically detects high‑spending hotel guests after checkout and emails them a personalized, one‑time reward offer. 🔧 What it does Watches Salesforce Guest__c custom object for checkout updates. Pulls guest spend data on optional paid amenities: Room Service Minibar Laundry Late Checkout Extra Bed Airport Transfer Calculates total spend to identify VIP guests (≥ $50). Uses AI to: Spot unused services. Randomly pick one unused service. Generate a realistic, short promo like: "Free late checkout on your next stay" Parses AI output into JSON. Sends a polished HTML email to the guest with their personalized offer. 📦 Key nodes Salesforce Trigger → monitors new checkouts. Salesforce → fetches detailed spend data. Function → sums up total amenity spend. IF → filters for VIP guests. LangChain LLM + Google Vertex AI → drafts the offer text. Structured Output Parser → cleans AI output. Brevo → delivers branded email. 📊 Example output > Subject: John, We Have Something Special for Your Next Stay > Offer in email: Enjoy a complimentary minibar selection on your next stay. ✨ Why it matters Rewarding guests who already spend boosts loyalty and repeat bookings — without generic discounts. The offer feels personal, relevant, and exclusive.

Turn Gumroad buyers into newsletter subscribers on Beehiiv, log to Google Sheets and get notified on Telegram Requirements Gumroad account** Gumroad application* + *API key** Product listed** on Gumroad Beehiiv account** Publication created** on Beehiiv Beehiiv API key** Google Sheets access** (with API credentials) Telegram Bot** created + Bot Token Telegram Channel** created and Bot added as admin Set Up 1. Trigger on a New Gumroad Sale Create a new application in Gumroad (Settings > Advanced). Copy your API key (access token). Paste it into the Gumroad Sale Trigger node. 2. Connect to Beehiiv Newsletter Create a publication inside Beehiiv. Generate and copy your Beehiiv API key. Use it to list publications and post a new subscription. 3. Load Into CRM (Google Sheets) Set up your Google Sheets API credentials Append the subscriber's data into your CRM 4. Send a Telegram Message Create a Telegram Bot and get your Bot Token. Add the Bot to your Telegram Channel and make it an admin. In the Telegram Send Message node: Use your Bot Token. Set your Channel Username or Chat ID. Customize the message content (e.g., "New Sale from {{customerEmail}} 🎉"). Further Optimizations Add more data to Beehiiv**: Include optional fields like first name, last name, custom tags, etc., when posting the subscription. Customize your Telegram message**: Personalize the message with product name, sale amount, or customer name. Enhance CRM data**: Add additional sale details into Google Sheets, like product ID, purchase timestamp, or affiliate code if available. Error Handling**: Add an error workflow to retry failed Beehiiv or Google Sheets updates automatically or log the error messages in your team chat in Slack or Microsoft Teams. ✅ That's it! Every time a new sale happens, the customer is added to your Beehiiv newsletter, saved in your CRM, and you receive an instant notification on Telegram! Get in touch with us Feel free to contact us at 1 Node. Get instant access to a library of free resources we created.

Description This n8n workflow template allows users to check if a Tron wallet address is blacklisted on the USDT contract via a Telegram bot. When a user sends the command {walletAddress} through the Telegram bot, the workflow queries the Tronscan API to determine if the provided wallet address is blacklisted. The result is then sent back to the user via the Telegram bot. Detailed Description Workflow Overview This workflow is designed to interact with users through a Telegram bot and check if a given Tron wallet address is blacklisted on the USDT contract. The workflow consists of four main nodes: Telegram Trigger Node: Listens for messages from the Telegram bot. HTTP Request Node: Sends a GET request to the Tronscan API to check the blacklist status of the provided wallet address. Function Node: Processes the API response and formats the message to be sent back to the user. Telegram Send Message Node: Sends the formatted message back to the user via the Telegram bot. Nodes Configuration 1.Telegram Trigger Node Event: Message Update Types: Message Command: /sorgu Description: This node listens for the {walletAddress} command followed by a wallet address from the user. 2.HTTP Request Node Method: GET URL: https://apilist.tronscanapi.com/api/stableCoin/blackList?blackAddress={{ $json.message.text }} Response Format: JSON Description: This node sends a GET request to the Tronscan API using the wallet address provided by the user. 3.Code Node Check Api Response: let message; if (response.total && response.total > 0) { message = 🚨🛑 This Wallet is Blacklisted! 🛑🚨: ${response.data[0].blackAddress}; } else { message = ✅💚 This Wallet is NOT Blacklisted! 💚✅.; } return [ { json: { text: message, }, }, ]; Description:** This node processes the API response to determine if the wallet address is blacklisted and formats the message to be sent back to the user. 4.Telegram Send Message Node Resource: Message Operation: Send Chat ID: ={{$json["chat_id"]}} Text: ={{$json["text"]}} Description: This node sends the formatted message back to the user via the Telegram bot. How to Use Set Up Telegram Bot: Create a Telegram bot and obtain the API token. Configure the bot to listen for the {walletAddress} command. Import Workflow: Import this workflow into your n8n instance. Configure Credentials: Add your Telegram API credentials to the Telegram Trigger and Telegram Send Message nodes. Run Workflow: Start the workflow. Users can now send the {walletAddress} command to the Telegram bot to check if a Tron wallet address is blacklisted. Example Usage User Telegram Command: {TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t} API Request: https://apilist.tronscanapi.com/api/stableCoin/blackList?blackAddress=TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t API Response: "total": 1, "data": [ { "blackAddress": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t", "tokenName": "USDT", "num": "367583344429", "time": 1593184959, "transHash": "af4bc4d793f82ca5ba500cf13cf93ca3e7a56fccc2aabf8b09e55fc756500ea8", "contractAddress": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t" } ] } Bot Response: 🚨🛑 This Wallet is Blacklisted! 🛑🚨: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t > This workflow provides a simple and efficient way to check the blacklist status of Tron wallet addresses via a Telegram bot, making it easy for users to stay informed about the status of their wallets.

Description Automates error detection and notification to prevent production downtime. Monitors incoming webhooks, filters critical errors, and triggers alerts or bug reports. Ensures rapid response to critical issues in real-time. Essential Information Processes webhook triggers to detect errors instantly. Filters and categorizes errors as critical or non-critical. Sends Slack alerts for critical errors and creates Jira bugs as needed. System Architecture Error Detection Pipeline**: Webhook Trigger: Captures incoming error data via POST requests. Filter Critical Errors: Identifies and separates critical errors. Alert Generation Flow**: Send Slack Alert: Notifies the team via Slack for critical errors. Create Jira Bug: Logs critical errors as Jira issues. Non-Critical Handling**: No Action for Non-Critical: Skips non-critical errors with no further action. Implementation Guide Import the workflow JSON into n8n. Configure webhook URL and test with sample error data. Set up Slack and Jira credentials for alerts and bug creation. Test error filtering and notification flows. Monitor alert accuracy and adjust filter rules as needed. Technical Dependencies Webhook service for error data ingestion. Slack API for real-time notifications. Jira API for bug tracking and issue creation. n8n for workflow automation. Customization Possibilities Adjust Filter Critical Errors node to refine error severity rules. Customize Slack alert messages in Send Slack Alert node. Modify Jira issue templates in Create Jira Bug node. Add logging node to track all errors for analysis. Integrate with additional notification tools (e.g., email).

🎬 YouTube Video to Blog – Multilingual Blog Generator Convert YouTube videos into SEO-friendly blog posts in just seconds using this fully automated n8n workflow. Perfect for content creators, marketers, educators, and bloggers looking to repurpose video content without manual transcription or formatting. 🔧 What It Does 📥 Accepts a YouTube video URL and preferred language via a simple form 🧠 Uses a third-party API to convert the video into a blog-style article 📄 Automatically inserts the generated content into a Google Docs document 🌍 Supported Languages Supports all major languages, including but not limited to: English Hindi French German Gujarati 🎯 The workflow is flexible and can generate blog content in any language supported by the API. Just select your language when submitting the form. 🚀 Benefits ⏱️ Time-Saving: Eliminate manual video transcription and formatting 🌐 Multilingual: Easily generate blogs in multiple languages 📚 Centralized Storage: Store all generated blogs in a single Google Docs file 🔧 Customizable: Extend the flow to auto-publish, email, or analyze content 🧠 Use Cases Repurpose YouTube content into keyword-rich blog posts Generate multilingual content for global reach Convert educational videos into study guides or summaries Create email newsletters or social media posts from video content 🛠️ Requirements ✅ An n8n instance (self-hosted or cloud) 🔑 RapidAPI key for youtube-to-blog.p.rapidapi.com 🧾 A Google Docs account with API access 🚨 Note: Be sure to update the API key and Google Docs URL with your own credentials before activating the workflow. 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!

Reduce human delays between malware detection and remediation in MSSP/SOC environments. This workflow automates full endpoint antivirus scanning immediately after high-severity endpoint infection wazuh alerts, closing the gap between alerting and action. Why Use This Workflow? Malware alerts are only effective if acted upon swiftly. Manual follow-ups are slow or often missed, letting threats persist. Automates detection, triage, scan initiation, and notification—all within one minute of alerting. Ensures consistent, auditable actions across endpoints running Linux or Windows. 🔑 Key Features Listens for high-severity Wazuh AV infection alerts (e.g., rule 52502). Uses GPT-4 for AI-powered alert summaries to speed triage and decision making. Extracts exact infected file paths using AI and regex for targeted scanning. Runs ClamAV/defender scans directly on endpoints via SSH with least-privilege credentials. Sends real-time scan results and remediation updates through Telegram, Slack, or email. Runs locally with limited permissions—no need for elevated Wazuh manager access. 🎯 Impact Eliminates manual lag—scans start automatically and immediately. Standardizes response playbooks for reliable, repeatable remediation. Reduces threat dwell time, minimizing risk exposure. Provides full event-to-remediation visibility via logs and notifications. 🚀 Get Started Configure Wazuh Manager to forward AV alerts to this n8n webhook. Import this workflow JSON into your n8n instance. Set up required credentials: OpenAI API, SSH access for ClamAV scanning, notification channels (Telegram/Slack/email). Activate the workflow and monitor alerts triggering automated scans and reports. 📂 Enjoy customizing Swap ClamAV with your preferred antivirus commands (e.g., Defender) as needed. Integrate with your existing communication or ticketing systems. Extend or adapt for multi-endpoint orchestration or other alert rules. Created by Mariskarthick M Senior Security Analyst | Detection Engineer | Threat Hunter | Open-Source Enthusiast