Browse 12,955 Workflows

By n8n Team

This workflow sends new Mailchimp subscribers to HubSpot as new or updated contacts. Prerequisites Mailchimp account and Mailchimp credentials HubSpot account and HubSpot credentials How it works Cron node triggers this workflow every day at 7:00. Mailchimp node searches for new subscribers. New Mailchimp subscribes get sent to HubSpot. HubSpot node either updates the existing contact or adds a new one to the pipeline. An n8n automation workflow template by n8n Team.

By n8n Team

This workflow adds new HubSpot contacts to the Mailchimp email list. Prerequisites HubSpot account and HubSpot credentials Mailchimp account and Mailchimp credentials How it works Cron node triggers this workflow every day at 7:00. HubSpot node searches for the new contacts created. Mailchimp node creates a new contact in a certain audience and add a 'subscribed' status. An n8n automation workflow template by n8n Team.

By n8n Team

This workflow syncs data between Notion and Asana whenever a new task or an update is done in one of the apps. Prerequisites Asana account and Asana credentials Notion account and Notion credentials How it works Go to Asana account. Create a new task in Asana. Notice a new task created in Notion account. Update the task in Asana. Notice the task is updated in Notion. An n8n automation workflow template by n8n Team.

By n8n Team

This workflow let's a bot in Slack notify a specific channel when a new product in WooCommerce is published and live on the site. Prerequisites WooCommerce account Slack and a Slack bot How it works Listen for WooCommerce product creation If permalink starts with https://[your-url-here].com/product/ Slack bot notifies channel that a new product has been added. Please note, you must update the URL in the IF node to match your url. If your WooCommerce doesn't use the slug /product/, that will need to be updated too. An n8n automation workflow template by n8n Team.

By n8n Team

This automated workflow takes a Typeform form, and once it is filled out, it is automatically uploaded as a Lead in Pipedrive. There is an option for custom fields (this workflow works with company size), and leaves notes in the note section based on questions answered. Prerequisites Typeform account and Typeform credentials and a form for people to fill out Pipedrive account and Pipedrive credentials Nodes Typeform node gets the data after the survey is completed Set node extracts data from the Typeform node and keeps only relevant data Function node maps the company size Pipedrive node populates a pipeline with a deal and adds custom fields. An n8n automation workflow template by n8n Team.

By Tom

This workflow shows a low code approach to creating a HTML table based on Google Sheets data. It's similar to this workflow, but allows fully customizing the HTML output. To run the workflow: Make sure you have a Google Sheet with a header row and some data in it. Grab your sheet ID: Add it to the Google Sheets node: Activate the workflow or execute it manually Visit the URL provided by the webhook node in your browser (production URL if the workflow is active, test URL if the workflow is executed manually). An n8n automation workflow template by Tom.

By Tom

This workflow shows a no code approach to creating a HTML table based on Google Sheets data. To run the workflow: Make sure you have a Google Sheet with a header row and some data in it. Grab your sheet ID: Add it to the Google Sheets node: Activate the workflow or execute it manually Visit the URL provided by the webhook node in your browser (production URL if the workflow is active, test URL if the workflow is executed manually). An n8n automation workflow template by Tom.

By Tom

This workflow identifies new rows in Google Sheets using a separate column keeping track of already processed rows. For this approach to work, the sheet needs to meet two requirements: A unique identifier for each row is required A column used to differentiate new/processed rows is present Our example sheet looks like this: So the row identifier is named ID, the new/processed column is called Processed. Update the workflow accordingly if your columns have different names. Now if the workflow runs, it discovers all three rows as new. After processing them, it will add a timestamp to the Processed column: The next time the workflow is executed it will skip the existing rows and only process newly added data:. An n8n automation workflow template by Tom.

By Lorena

This workflow queries a table in MySQL and inserts the data into Google Sheets. An n8n automation workflow template by Lorena.

By Jonathan

Task: Control your data flow with rate limits and external cues Main use cases: Control the rate of items flow into one or more services in your workflow Wait for external events to occur before continuing with the rest of the workflow. An n8n automation workflow template by Jonathan.

By Jonathan

Task: Conditional filtering and branching items Why: Filtering and branching data based on conditions allows you to build complex workflows that work with more than one data flow scenario Main use cases: Filter out data that is not relevant for the rest of the workflow Split data to several branches of the workflow, where we want the data to be treated differently in the rest of the workflow. An n8n automation workflow template by Jonathan.

By Lorena

This workflow illustrates how to convert data from JSON to binary format and import JSON data or files into Google Sheets or local spreadsheets. An n8n automation workflow template by Lorena.

By Lorena

This workflow gets data from an API and exports it into Google Sheets and a CSV file. An n8n automation workflow template by Lorena.

By Lorena

This workflow exports the contents of a JSON file to Google Sheets. An n8n automation workflow template by Lorena.

By Lorena

This workflow imports a JSON file from an email attachment and saves the content into a spreadsheet. An n8n automation workflow template by Lorena.

By Lorena

This workflow exports a local CSV file to a JSON file. An n8n automation workflow template by Lorena.

By Eduard

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. An n8n automation workflow template by Eduard.

By Eduard

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. An n8n automation workflow template by Eduard.

By Ron

This sample workflow allows you to forward alerts from TheHive 5 to SIGNL4 in order to send reliable alerts to your team. There are two nodes for testing the TheHive connection ("TheHive Read Alerts" and "TheHive Create Alert"). The node "TheHive Webhook Request" will receive requests for new alerts from TheHive. You need to configure the webhook and the notifications in TheHive accordingly. The node "SIGNL4 Send Alert" sends the alert to SIGNL4 and the node "SIGNL4 Resolve Alert" will close the alert in SIGNL4 in case it has been closed in TheHive. An n8n automation workflow template by Ron.

By Tom

This workflows helps with processing binary data. You'll often have binary objects with keys such as attachment_0, attachment_1, attachment_2, etc. attached to your items, for example when reading an incoming email. This binary data is hard to process because it's not an array you can simply loop through. This workflow solves this problem by providing a Function node that takes all incoming items and all their binary data and then returning a single item for each file with a data key containing your binary file. Incoming binary data: Processed binary data:. An n8n automation workflow template by Tom.

By Eduard

This workflow extends n8n and uses R language graphic capabilities. This is a Telegram bot which fetches weather data via the openweathermap.org API, plots an image using ggoplot2 package from R and sends the image to the Telegram user. An n8n automation workflow template by Eduard.

By v1d1an

With workflow, you analyze Email with TheHive/Cortex https://github.com/V1D1AN/S1EM/wiki/Soar-guide. An n8n automation workflow template by v1d1an.

By Alessio

A simple node to send new YouTube videos from a channel to a Telegram chat (private, group or channel). CheckTime: set how often videos should be fetched from YouTube. Default is 30 minutes. GetVideosYT: this node will fetch the list of videos from a given channel. Here you need to specify on "Limit" the number of videos to fetch, and on "Channel ID" the ID of the desired channel (it should be the ending part of the URL). You need Google OAuth2 credentials to make it work. A guide is available here. (If you use n8n's tunneling, you may need to adjust the OAuth callback URL on Google Cloud Platform) Set: this node will set some variables to work easily with the next nodes. You shouldn't edit this. Function: this node checks if the video was seen previously by the workflow, so that it won't be published a second time on Telegram. You shouldn't edit this. SendVideo: this node sends the message to Telegram. You need to set your bot's credentials (guide here), specify the Chat ID to send the message (how to get) and personalize the Text of your message. This workflow works correctly only when it's activated. If you manually execute the workflow, it will send every time the latest videos. An n8n automation workflow template by Alessio.

By Jason

Upload invoices from Gmail to Google Drive daily. An n8n automation workflow template by Jason.

By Aaron Smusz

This workflow automatically manages Acrobat Sign signatures, respond with "intent" to Acrobat-Sign webhooks. Prerequisites Adobe Acrobat Sign and Sign webhook Basic knowledge of JavaScript Nodes Webhook nodes trigger the workflow on new sign intents on a document Respond to Webhook node sets the response headers. Function node processes data returned by the previous node. Set node sets the required values. An n8n automation workflow template by Aaron Smusz.

By Eduard

An example workflow for a multilanguage Telegram bot. It allows adding many new languages to the bot without editing the workflow. Important note! Due to some breaking API changes in NocoDB some of its node options are not working at the moment (MAY 2022). These two nodes were replaced by HTTP request nodes. Functionality is still the same. An n8n automation workflow template by Eduard.

By Mario

Template to get your public IP address and push it to Namecheaps Dynamic DNS per subdomain. Open "yourdomain.com" Insert your domain and your Namecheap DDNS password Open "subdomains" Replaces and insert your subdomains Execute Workflow Have fun!. An n8n automation workflow template by Mario.

By Ghazi Triki

Fetches Zammad tickets at daily basis at 08:30 then sends them to #customer support>ticket on zulip for daily standups. An n8n automation workflow template by Ghazi Triki.

By Max Tkacz

This workflow shows you how to post a message to a Slack channel and add a file attachment. It also shows you the general pattern for working with Binary data in n8n (any file like a PDF, Image etc). Specifically, this workflow shows how to download a file from a URL into your workflow, and then upload it to Slack. Video walkthrough Watch this 3 min Loom video for a walkthrough and more context on this general pattern:. An n8n automation workflow template by Max Tkacz.

By Badr

Description This workflow, delivers real-time cryptocurrency market updates (default: Bitcoin) by fetching data from the CoinGecko API. It formats the information into a visually engaging message and shares it on X (formerly Twitter) and via email. The workflow is set to trigger hourly but is fully customizable to suit different schedules or cryptocurrencies. Key Features Real-Time Market Data Retrieval:** Fetches up-to-date cryptocurrency market data using CoinGecko API. AI-Driven Message Formatting:** Converts raw data into a structured, engaging message. Social Media Integration:** Posts updates to X with OAuth2 authentication. Email Notifications:** Sends updates via email to specified recipients. Flexible Customization:** Adaptable for tracking multiple cryptocurrencies or adding new notification channels. Workflow Steps Trigger Workflow: Default is hourly, but the interval can be customized. Fetch Cryptocurrency Data: Retrieves market data using the CoinGecko API. Format the Message: Converts the data into a readable and visually appealing format. Post Update on X: Shares the message on X (formerly Twitter). Send Email Notifications: Sends the update to a specified email address. Optional Notifications: Expand to additional channels like Slack or Telegram. An n8n automation workflow template by Badr.

By WeblineIndia

This smart automation workflow created by the AI development team at WeblineIndia, helps with the daily collection and storage of weather data. Using the OpenWeatherMap API and Airtable, this solution gathers vital weather details such as temperature, humidity, and wind speed. The automation ensures daily updates, creating a dependable historical record of weather patterns for future reference and analysis. Steps: Set Schedule Trigger Configure a Cron node to trigger the workflow daily, for example, at 7 AM. Fetch Weather Data (HTTP Request) Use the HTTP Request node to retrieve weather data from the OpenWeatherMap API. Include your API key and query parameters (e.g., q=London, unit=metric) to specify the city and desired units. Parse Weather Data Utilize a JSON Parse node to extract key weather details, such as temperature, humidity, and wind speed, from the API response. Store Data in Airtable Use the Airtable node to insert the parsed data into the designated Airtable table. Ensure proper mapping of fields like temperature, humidity, and wind speed. Save and Execute Save the workflow and activate it to ensure weather data is fetched and stored automatically every day. Outcome This robust solution, developed by WeblineIndia, reliably collects and archives daily weather data, providing businesses and individuals with an accessible record of weather trends for analysis and decision-making. About WeblineIndia We specialize in creating custom automation solutions and innovative software workflows to help businesses streamline operations and achieve efficiency. This weather data fetcher is just one example of our expertise in delivering value through technology. An n8n automation workflow template by WeblineIndia.

By Angel Menendez

Who is this for? This workflow is designed for IT teams, service desk personnel, and incident management professionals who need a streamlined way to monitor and report on recent ServiceNow incidents directly within Slack. What problem is this workflow solving? / Use Case Manually monitoring incidents in ServiceNow can be time-consuming, and keeping teams updated about new or specific incidents often involves additional manual effort. This workflow automates the process of querying recent incidents from ServiceNow based on user-defined parameters and delivering formatted results directly to Slack. It ensures faster response times and improved incident visibility. What this workflow does This workflow integrates Slack and ServiceNow to provide an automated system for retrieving and presenting incident details. Slack User Interaction: Users initiate the workflow via a Slack modal form, selecting incident parameters like priority and state. ServiceNow Query: The workflow queries ServiceNow for incidents matching the selected criteria. Results Delivery: Incident results are sent back to Slack as a message formatted using Block Kit. If no results are found, the workflow notifies the user with a detailed message, either in a Slack channel or via direct message. Error Handling: If no channel is selected or any issues arise, the workflow ensures graceful fallback with appropriate notifications. Setup Instructions Slack Setup: Integrate Slack with n8n using a Slack app. Configure the modal form to accept parameters like priority and state. Check out this video for setting up a modal slack app on YouTube. ServiceNow Integration: Use ServiceNow credentials to connect with n8n. Ensure appropriate permissions for querying incidents. n8n Workflow Configuration: Import this workflow into n8n. Verify all node configurations, particularly those for ServiceNow API queries and Slack outputs. Set up webhook URLs for Slack event handling. Testing: Trigger the workflow from Slack to test modal inputs and incident queries. Confirm the output is correctly formatted and delivered to the intended Slack channel or user. How to Customize this Workflow to Your Needs Modify the ServiceNow query logic to include additional filters or fields. Adjust the Slack Block Kit formatting to match your organization’s preferred notification style. Use conditional logic to add more advanced handling for specific priorities or states. Expand the workflow to include escalation steps, such as notifying a specific team or creating follow-up tasks. Workflow Highlights Slack Modal Form**: Allows users to specify search criteria for incidents interactively. Dynamic Results Delivery**: Automatically sends results to a Slack channel or direct message based on user input. Error Handling**: Provides fallback notifications when no incidents are found or user inputs are incomplete. Customizable Integration**: Easily adaptable to fit different organizational needs, including advanced filtering and formatting options. An n8n automation workflow template by Angel Menendez.

By Angel Menendez

Who is this for? This workflow is designed for teams using Slack for communication and ServiceNow for incident management. It simplifies incident lookup by enabling team members to fetch incident details directly within Slack via a Slash Command. What problem is this workflow solving? Manually switching between Slack and ServiceNow to retrieve incident details can be time-consuming and disrupt workflow efficiency. This workflow bridges the two platforms, providing instant access to critical incident information in Slack, saving time, and improving response efficiency. What this workflow does? The workflow listens for a Slash Command in Slack that includes an incident ID, extracts the ID from the incoming payload, queries ServiceNow for the corresponding incident details, and sends a formatted response back to Slack. Depending on the query result, it can: Display incident details (e.g., ID, description, severity, and priority). Notify the user if no matching incident is found. Alert the user if there’s an issue connecting to ServiceNow. Setup Slack Setup: Create a Slash Command in Slack with the appropriate endpoint URL. Configure the command to send a POST request to the webhook endpoint of this workflow. For details on how to setup the Slack app using Slash commands and n8n, check out this video. ServiceNow Setup: Create or use an existing account with the necessary permissions to access incident data. Configure the ServiceNow node with your ServiceNow credentials. n8n Workflow Activation: Deploy and activate the workflow in your n8n instance. Ensure all nodes are properly configured and connected. How to customize this workflow to your needs Modify Incident Query Parameters:** Adjust the query logic in the Search For Incident in ServiceNow node to include additional filters or data points based on your organization’s needs. Slack Response Customization:** Customize the Slack response template to display additional incident details or to match your team’s tone and style. Error Handling:** Enhance the error handling nodes to include more detailed logs or send alerts to a dedicated Slack channel. An n8n automation workflow template by Angel Menendez.

By Mario

Purpose This workflow snippet allows for advanced error catching during retry attempts. There are cases, where you want to check if an item exists first, so you can determine the following actions. Some API’s do not support an endpoint (e.g. Todoist: completed tasks) to do so, which is why you would work with the error branch, only that this does not work well in combination with the retry functionality. How it works Instead of the builtin retry function of a Node a custom loop is used, to get more granular control in between the iterations If the main executed node fails, the error can be filtered for an expected error, which can trigger a separate action The retries only happen, if an unexpected error happened The workflow only stops, if the defined amount of retries exceeded Setup Copy the nodes into your existing workflow Replace the “Replace me” placeholder with the Node you want to apply the retry logic on Follow the sticky notes for more instructions and optional settings. An n8n automation workflow template by Mario.

By WeblineIndia

This workflow, developed by our AI developers at WeblineIndia, is designed to automate the process of capturing form submissions and storing them in Airtable. By leveraging automation, it eliminates manual data entry, ensuring a smooth and efficient way to handle form data. The purpose of creating this workflow is to streamline data management, helping businesses save time, reduce errors, and maintain an organized, structured database for easy access and future use. Steps: Trigger on Form Submission (Form Node)** What It Does: Activates the workflow whenever a form is submitted. How to Set It Up: Use the Form Submission Trigger node to detect new form submissions. This ensures the workflow starts automatically when a user fills out the form. Store Data in Airtable (Airtable Node)** What It Does: Transfers the form data into an Airtable base. How to Set It Up: Use the Airtable Node to map form fields to corresponding columns in your Airtable table, storing the data accurately. Finalize and Activate** What It Does: Completes the setup to automate data storage upon form submission. How to Set It Up: Save and activate the workflow. Once active, it will automatically record all new form submissions in Airtable. An n8n automation workflow template by WeblineIndia.

By Keith Rumjahn

Case Study 📧 Want to collect email subscribers without paying expensive monthly fees? 💰 This workflow creates a free email collection system with built-in email verification to ensure you only collect legitimate email addresses! ✨ Learn more: 📺 Watch the tutorial: What this workflow does 🛠️ Creates a customizable email collection form that can be embedded on your website 🌐 Verifies email addresses using Hunter.io to filter out fake or invalid emails ✅ Stores verified email addresses in SendGrid for your email marketing needs 📊 Completely free solution (except for Hunter.io's 50 free monthly credits) 🆓 Setup ⚙️ Set up a free Hunter.io account for email verification Configure your SendGrid account credentials Customize the email collection form fields Get the embedded form code for your website How to adjust it to your needs 🔧 Add additional form fields beyond just email collection Customize the form's appearance and labels Modify the verification logic based on your requirements Connect to different email marketing platforms instead of SendGrid Add additional automation steps after email verification Benefits 🌟 No monthly subscription fees for email collection 💸 Built-in email verification prevents fake signups 🛡️ Scalable solution that won't lock you into expensive plans 📈 Clean email list with only verified addresses ✨ Simple setup and customization 🎯 This workflow is perfect for bloggers, small businesses, and anyone looking to build an email list without getting locked into expensive email marketing platforms as their subscriber count grows! 🚀 Built by rumjahn. An n8n automation workflow template by Keith Rumjahn.

By Solomon

Português Acompanhe todos os seus eventos do Hotmart em um só lugar e mantenha seus dados organizados para análise. Com este fluxo você pode registrar compras, reembolsos, eventos de assinatura e abandono de carrinho diretamente no Google Sheets. Como funciona O fluxo recebe os eventos da Hotmart e registra automaticamente no Google Sheets. Por exemplo: Compras são registradas com informações como nome do produto, valor pago e dados do comprador. Abandono de carrinho registra informações sobre o produto visualizado, dados de contato do cliente e horários. Eventos de assinatura mostram atualizações como cancelamentos ou renovações. Para quem é? Criadores, empreendedores e negócios que usam o Hotmart e precisam de uma forma clara e automatizada de acompanhar suas vendas e dados de assinatura. Remova a necessidade de transferir dados manualmente – este fluxo de trabalho faz isso por você, economizando tempo e reduzindo erros. Confira meus outros templates 👉 https://n8n.io/creators/solomon/ English Track all your Hotmart events in one place and keep your data organized for analysis. With this workflow, you can register purchases, refunds, subscription events, and cart abandonment directly in Google Sheets. How it works The workflow listens for events from Hotmart and automatically records the details in Google Sheets. For example: Purchases are logged with details like product name, amount paid, and buyer information. Cart abandonment records include the product viewed, customer contact details, and timestamps. Subscription events show updates like cancellations or renewals. Who is this for? Creators, entrepreneurs, and businesses using Hotmart who need a clear and automated way to track their sales and subscription data. No need to manually transfer data – this workflow does it for you, saving time and reducing errors. Check out my other templates 👉 https://n8n.io/creators/solomon/. An n8n automation workflow template by Solomon.

By Mauricio Perera

Workflow Description: Product Data Extractor This workflow automates the extraction of product data from Product Hunt by combining webhook interactions, HTML processing, AI-based data analysis, and structured output formatting. It is designed to handle incoming requests dynamically and return detailed JSON responses for further usage. Overview The workflow processes a product name submitted through a webhook. It fetches the corresponding Product Hunt page, extracts and analyzes inline scripts, and structures the data into a well-defined JSON format using AI tools. The final JSON response is returned to the client through the webhook. Workflow Steps 1. Webhook Listener Node:** Receive Product Request Function:** Captures incoming requests containing the product name to process. Details:** Accepts HTTP requests and extracts the product parameter from the query string, such as <custom_webhook_url>/?product=epigram. 2. Fetch Product HTML Node:** Fetch Product HTML Function:** Sends an HTTP request to retrieve the HTML content of the specified Product Hunt page. Details:** Constructs a dynamic URL using the product name and fetches the page data. 3. Extract Inline Scripts Node:** Extract Inline Scripts Function:** Parses the HTML content to extract inline scripts located within the <head> section. Details:** Excludes scripts containing src attributes and validates the presence of inline scripts. 4. Process Data with LLM Node:** Process Script with LLM Function:** Analyzes the extracted scripts using a language model to identify key product data. Details:** Processes the script to derive structured and meaningful insights. 5. Refine Data with Google Gemini Node:** Analyze Script with Google Gemini Function:** Leverages Google Gemini AI for enhanced analysis of script data. Details:** Ensures the extracted data is precise and enriched. 6. Format Product Data to JSON Node:** Format Product Data to JSON Function:** Structures the processed data into a clean JSON format. Details:** Defines a schema to ensure all relevant fields are included in the output. 7. Send JSON Response to Client Node:** Send JSON Response to Client Function:** Returns the final structured JSON response to the client. Details:** Sends the response back via the same webhook that initiated the request. For example, <custom_webhook_url>. Key Features Versatile Use Cases:** This workflow can be used to gather Product Hunt data for creating blog posts or as a tool for AI agents to research products efficiently. Dynamic Processing:** Adapts to various product names through dynamic URL construction. AI Integration:** Utilizes the Gemini 1.5 8B AI model, offering reduced latency and minimal or no cost depending on the use case. Selector Independence:** Functions even if Product Hunt's DOM structure changes, as it does not rely on direct DOM selectors. Reliable Data Output:** A low temperature setting (0) and a precisely defined JSON schema ensure accurate and real data extraction. Dynamic Processing:** Adapts to various product names through dynamic URL construction. AI Integration:** Utilizes advanced language models for data extraction and refinement. Structured Output:** Ensures the output JSON adheres to a predefined schema for consistency. Error Handling:** Includes validations to handle missing or malformed data gracefully. Customization Options Limitations Dependency on Product Hunt:** Significant changes to the way Product Hunt loads data on its pages might require modifications to the workflow. Adaptability:** Even if changes occur, the workflow can be updated to maintain functionality due to its reliance on AI and not direct DOM selectors. Modify the webhook path to suit your application. Adjust the prompt for the language model to include additional fields. Extend the JSON schema to capture more data fields as needed. Expected Output Performance Metrics Response Time:** Typically ~6 seconds per product. Accuracy:** Data extracted with >95% precision due to the pre-defined JSON schema. A JSON object containing detailed information about the specified product. Below is an example of a complete response for the product Epigram: { "id": "861675", "slug": "epigram", "followersCount": 181, "name": "Epigram", "tagline": "Open-Source, Free, and AI-Powered News in Short", "reviewsRating": 0, "logoUuid": "735c2528-554c-467c-9dcf-745ee4b8bbdd.png", "postsCount": 1, "websiteUrl": "https://epigram.news", "websiteDomain": "epigram.news", "metaTitle": "Epigram - Open-source, free, and ai-powered news in short", "postName": "Epigram", "postTagline": "Open-source, free, and ai-powered news in short", "dailyRank": "3", "description": "An open-source, AI-powered news app for busy people. Stay updated with bite-sized news, real-time updates, and in-depth analysis. Experience balanced, trustworthy reporting tailored for fast-paced lifestyles in a sleek, user-friendly interface.", "pricingType": "free", "userName": "Fazle Rahman", "userHeadline": "Co-founder & CEO, Hashnode", "userUsername": "fazlerocks", "userAvatarUrl": "https://ph-avatars.imgix.net/129147/f84e1796-548b-4d6f-9dcf-745ee4b8bbdd.jpeg", "makerName1": "Fazle Rahman", "makerHeadline1": "Co-founder & CEO, Hashnode", "makerUsername1": "fazlerocks", "makerAvatarUrl1": "https://ph-avatars.imgix.net/129147/f84e1796-548b-4d6f-9dcf-745ee4b8bbdd.jpeg", "makerName2": "Sandeep Panda", "makerHeadline2": "Co-Founder @ Hashnode", "makerUsername2": "sandeepg33k", "makerAvatarUrl2": "https://ph-avatars.imgix.net/101872/80b0b618-a540-4110-a6d1-74df39675ad0.jpeg", "primaryLinkUrl": "https://epigram.news/", "media1OriginalHeight": 1080, "media1OriginalWidth": 1440, "media1ImageUuid": "ac426fd1-3854-4734-b43d-34a5e06347ea.gif", "media1MediaType": "video", "media1MetadataUrl": "https://www.loom.com/share/b1a48a9b3cac4ba89ce772a3fbcc2847?sid=75efc771-25fa-4ac0-bb1b-5e38fc447deb", "media1VideoId": "b1a48a9b3cac4ba89ce772a3fbcc2847", "media2OriginalHeight": 630, "media2OriginalWidth": 1200, "media2ImageUuid": "8521a6bd-7640-487b-abd6-29b9f65fee32", "media2MediaType": "image", "media2MetadataUrl": null, "launchState": "featured", "thumbnailImageUuid": "735c2528-554c-467c-9dcf-745ee4b8bbdd.png", "link1StoreName": "Website", "link1WebsiteName": "epigram.news", "link2StoreName": "Github", "link2WebsiteName": "github.com", "latestScore": 233, "launchDayScore": 233, "userId": "129147", "topic1": "News", "topic2": "Open Source", "topic3": "Artificial Intelligence", "weeklyRank": "24", "commentsCount": 20, "postUrl": "https://www.producthunt.com/posts/epigram" } Target Audience This workflow is ideal for developers, marketers, and data analysts seeking to automate the extraction and structuring of product data from Product Hunt for analytics, reporting, or integration with other tools. An n8n automation workflow template by Mauricio Perera.

By AmirHossein MnasouriZade

Setting Up and Generating TOTP Step 1: Receive QR Code and Extract the Link 1. Receive the QR Code from the 2FA service After enabling two-factor authentication (2FA) on services like OpenAI, Google, GitHub, etc., a QR Code will be given to you, which you need to scan. This QR Code contains the TOTP link used to generate one-time passcodes. 2. Extract the link from the received QR Code To extract the link from the QR Code, use online tools. These tools will help you extract the corresponding link. After using an online tool, the extracted link will appear in the following format: otpauth://totp/ServiceName:username?secret=secret_key&issuer=ServiceName For example: otpauth://totp/OpenAI:amir676080@gmail.com?secret=test-test-test&issuer=OpenAI Step 2: Create TOTP Credential in n8n Create a new Credential To use TOTP in n8n, you need to create a new TOTP Credential. Enter the details in the Credential In the Secret field:* Enter the *secret key** (extracted from the QR Code link). For example: test-test-test In the Label field:* Enter *ServiceName:username** For example: OpenAI:amir676080@gmail.com Save the Credential After entering the information, click Save to save the Credential. Step 3: Get the TOTP Code Click on Test Workflow After setting up the credentials in n8n, click on Test, and the corresponding code will be delivered to you. Output: [ { "token": "720769", "secondsRemaining": 18 } ] ==This code is exactly the same as the one generated by apps and services like Google Authenticator or Authy. 🔐== Contact me on [Telegram]: https://t.me/amir676080. An n8n automation workflow template by AmirHossein MnasouriZade.

By Mauricio Perera

Purpose: This workflow exemplifies a sophisticated yet pragmatic mechanism for automating currency conversions by leveraging simple HTTP queries routed through a webhook. By intercepting user requests, sourcing real-time exchange rate data via Google search results, and formatting the data into actionable responses, it obviates the reliance on third-party APIs. This efficiency renders it an indispensable instrument for diverse applications, including dynamic pricing strategies for AI-driven systems, financial data automation, and real-time currency computation within complex workflows. The workflow's architectural simplicity ensures seamless integration across professional and academic domains, optimizing both scalability and reliability. Workflow Steps: Capture Conversion Query: The workflow initiates by intercepting user input delivered as a GET request through a configured webhook. Inputs should adhere to a structured syntax, such as 5usd to mxn, to ensure flawless processing. Testing Tip: Use tools like Postman or a browser to test GET requests and verify that the Webhook receives inputs correctly. Fetch Exchange Rate: Utilizing the HTTP Request node, a Google search query is executed to retrieve current exchange rate data. This method ensures the workflow remains economical and adaptable while circumventing API dependencies. Extract Conversion Data: By processing the returned HTML from Google's search results, this node extracts precise exchange rate figures and contextual information critical for accurate conversions. Error Handling: If extraction fails, verify that the input format is correct and update CSS selectors to reflect any changes in Google's HTML structure. Format Currency Response: The extracted data undergoes refinement and is formatted into a structured, user-friendly string that conveys the conversion results with clarity and precision. Send Conversion Response: The workflow culminates by dispatching the formatted response back to the request origin, completing the loop with efficiency and reliability. Required Configuration: Configure the Webhook node to accommodate GET requests. The query parameters should follow the format: https://your-webhook-url/currency-converter?q=5usd+to+mxn. Inputs must adhere strictly to the predefined syntax (e.g., 5usd to mxn). Deviations may induce processing errors or yield erroneous outputs. Customization Options: The Extract Conversion Data node’s CSS selectors can be fine-tuned to align with modifications in Google’s HTML structure, ensuring long-term operability. Adjustments to the Format Currency Response node enable bespoke output formatting, incorporating additional metadata or altering the response structure to meet specific project requisites. Advanced Features: This workflow’s modular design supports seamless integration into expansive systems. For instance, an e-commerce platform could employ it to dynamically localize product pricing based on user geolocation. Enhanced functionality can be achieved by appending nodes to log conversions, monitor performance metrics, or trigger auxiliary workflows conditioned on conversion outputs. Expected Results: For a query like 5usd to mxn, the workflow generates a response formatted as: 5 USD = 95 MXN. This output is optimized for readability and practical application. Use Case Examples: AI Integration:** Enables artificial intelligence agents to process real-time price conversions efficiently across diverse currencies, enhancing their computational capabilities. Financial Operations:** Automates precise currency conversions for corporate reports, international transactions, and market analytics. Personal Financial Planning:** Assists users in calculating currency conversions for investment decisions or travel budgeting with minimal manual effort. E-commerce Applications:** Facilitates dynamic price adjustments on online marketplaces, displaying localized prices to augment user experience and conversion rates. Workflow Integration:** Embeds seamlessly into larger systems, such as CRMs or ERPs, to streamline financial operations and enhance interoperability. Key Benefits: No API Dependency:** By leveraging publicly available data from Google, the workflow eliminates the complexities and costs associated with API integration, reducing overhead and enhancing accessibility. Precision and Currency:** Ensures accurate and real-time results by querying Google directly. Flexibility:** Designed to adapt to various operational contexts and input formats, making it a versatile asset in computational and commercial applications. Tags: currency conversion, automation, webhook, data extraction, AI integration, financial automation, e-commerce, real-time data, scalable workflows. An n8n automation workflow template by Mauricio Perera.

By Simon

📦 Zip Multiple Files Dynamically This template enables you to dynamically bundle multiple files into a ZIP archive. Designed to be used as a Subworkflow, it’s modular, flexible, and easy to integrate into various workflows. The output is a single ZIP file with a name that includes the current date, time, and fileName. Shoutout: Code from: Tom (mutedjam) 👤 Who is this for? This workflow is perfect for: 🚀 Businesses automating file archiving tasks. 💻 Developers managing files programmatically. 📂 Anyone needing a reusable solution for bundling files into ZIP archives. ❓ What problem is this workflow solving? Manually zipping multiple files is: 🕒 Time-consuming. 🤔 Prone to errors. This workflow automates the process and, as a Subworkflow, ensures: ⚡ Consistent file archiving across different workflows. 🛠️ Reduced manual effort. 📈 Streamlined integration into existing automation. 🔧 What this workflow does 🗂️ Dynamically collects binary files from the input. 📦 Bundles them into a single ZIP archive. 🕒 Names the ZIP file with the current date, time, and a customizable fileName. ✅ Outputs the ZIP file, ready for storage or further processing. ⚙️ Setup 🔗 Add this Subworkflow to your existing workflows. 📥 Pass the binary files as input to the Subworkflow. ▶️ Call the Subworkflow to generate a ZIP file. 🛠️ How to customize this workflow to your needs 🌐 File Sources**: Adjust the input nodes in your parent workflow to connect to your preferred file sources. 📝 File Naming**: Customize the logic for the output fileName in the Subworkflow. 🚀 Additional Use Cases**: Use this Subworkflow in various scenarios, such as: ✉️ Sending ZIP files via email. ☁️ Uploading ZIP files to cloud storage. 🔄 Triggering further automation. 🎉 Why use this as a Subworkflow? Instead of building a fixed ZIP functionality for every workflow, this template offers a reusable solution that can be integrated into many different workflows effortlessly. Save time and ensure consistency across your automation projects! 💡. An n8n automation workflow template by Simon.

By darrell_tw

This workflow automates the process of fetching agricultural transaction data from the Taiwan Agricultural Products Open Data Platform and storing it in a Google Sheets document for further analysis. Key Features Manual Trigger: Allows manual execution of the workflow to control when data is fetched. HTTP Request: Sends a request to the Open Data Platform's API to retrieve detailed transaction data, including: Pricing (Upper, Middle, Lower, Average) Transaction quantities Crop and market details Split Out Node: Processes each record individually, ensuring accurate handling of every data entry. Google Sheets Integration: Appends the data into a structured Google Sheets document for easy access and analysis. Node Configurations 1. Manual Trigger Purpose**: Start the workflow manually. Configuration**: No setup needed. 2. HTTP Request Purpose**: Fetch agricultural data. Configuration**: URL: https://data.moa.gov.tw/api/v1/SheepQuotation Query Parameters: Start_time: 2024/12/01 End_time: 2024/12/31 MarketName: 台北二 api_key: <your_api_key> Headers: accept: application/json 3. Split Out Purpose**: Split the API response data array into individual items. Configuration**: Field to Split Out: Data 4. Google Sheets Purpose**: Append the data to Google Sheets. Configuration**: Operation: Append Document ID: <your_document_id> Sheet Name: Sheet1 Mapped Fields: TransDate, TcType, CropCode, CropName, MarketCode, MarketName Upper_Price, Middle_Price, Lower_Price, Avg_Price, Trans_Quantity 此 Workflow 從 台灣農業產品開放資料平臺 獲取農產品交易數據，並將其儲存到 Google Sheets 文件 中進行進一步分析。 主要功能 Manual Trigger：允許手動執行工作流程，以控制數據獲取的時間。 HTTP Request：向開放資料平臺的 API 發送請求，獲取詳細的交易數據，包括： 價格 (Upper, Middle, Lower, Average) 交易數量 作物和市場詳細資料 Split Out Node：逐筆處理每一筆記錄，確保數據準確無誤。 Google Sheets Integration：將數據追加到結構化的 Google Sheets 文件中，方便存取和分析。 節點設定 1. Manual Trigger 用途**：手動啟動工作流程。 設定**：無需額外設定。 2. HTTP Request 用途**：抓取農產品數據。 設定**： URL: https://data.moa.gov.tw/api/v1/SheepQuotation 查詢參數 (Query Parameters)： Start_time: 2024/12/01 End_time: 2024/12/31 MarketName: 台北二 api_key: <your_api_key> 標頭 (Headers)： accept: application/json 3. Split Out 用途**：將 API 回應的數據陣列分解為個別項目。 設定**： Field to Split Out: Data 4. Google Sheets 用途**：將數據追加至 Google Sheets。 設定**： Operation：Append Document ID：<your_document_id> Sheet Name：Sheet1 映射欄位 (Mapped Fields)： TransDate, TcType, CropCode, CropName, MarketCode, MarketName Upper_Price, Middle_Price, Lower_Price, Avg_Price, Trans_Quantity 請多利用 Curl Import 功能 例如 curl -X GET "https://data.moa.gov.tw/api/v1/AgriProductsTransType/?Start_time=114.01.01&End_time=114.01.01&MarketName=%E5%8F%B0%E5%8C%97%E4%BA%8C" -H "accept: application/json" 農業資料開放平台 文件. An n8n automation workflow template by darrell_tw.

By Roger Filomeno

Introduction: This workflow template helps you determine if a Twitch user's stream is currently live or offline. Setup Instructions: The Document node holds the sample Twitch username you wish to check, you may adapt it in your workflow by replacing this with a chain that contains the Twitch username you want to check. This value is passed to the GraphQL node query as $('Document').item.json.twitch so make sure to change this based on your workflow. How it Works: The important nodes here are the GrapQL and IF nodes. The GrapQL queries the Twitch API, and then the output returns a document with the stream property. The IF node then checks if this property has a value, if null means the user is offline, otherwise the user is online or live. Common Use Cases: You can use this with other workflow templates to post live stream alerts to Twitter/X, Bluesky, and Discord via webhooks, etc to notify your community to join youR stream. You may also use an LLM node to write a custom alert based on the value of property title How to adjust this template If you want to check a list of Twitch channels, you can simply exchange the Document set node in the beginning with your list of channels. For more information on the GraphQL output please see the official Twitch API documentation: Get Streams. An n8n automation workflow template by Roger Filomeno.

By Sherlockes

What does this template help with? Save the data of activities recorded and stored in Strava to a Google Sheets document. How it works: We have a Google Sheets spreadsheet where each row represents a Strava activity with the date, reference, distance, time, and elevation. Periodically, the workflow checks the latest activities in our Strava account to see if any are missing from the spreadsheet and adds them to the list. All fields must be properly formatted according to how they are stored in the Google Sheets spreadsheet. Set up instructions Complete the Set up credentials step when you first open the workflow. You'll need a Google Sheets and Strava account. In the 'activities' node, you must enter the name of the file and the sheet where you want to save the imported data. In the 'Strava' node, you must select the corresponding credential. You can adjust the format of dates, times, and distances according to your needs in the 'strava_last' node. The rest of the information is available at sherblog.es Template was created in n8n v1.72.1. An n8n automation workflow template by Sherlockes.

By Solomon

Generating Stripe invoices through the API can be tricky since it requires four steps to generate and send it via email to the customer. With this workflow you can create Stripe invoices automatically and make Stripe send the invoices to the customer email. How it works To generate a Stripe invoice, you need to create a customer, specify the invoice items, create the invoice, and finalize it. What should be a simple task involves multiple steps. This workflow simplifies the process by providing everything pre-built for you. Who is this for? Anyone who wants to generate invoices automatically and send them to the customer’s email. Stripe will only send invoices to customers if you generate the invoice correctly through the API. . Check out my other templates 👉 https://n8n.io/creators/solomon/. An n8n automation workflow template by Solomon.

By Mauricio Perera

YouTube Subtitles Report Generator Overview This template enables users to generate analytical reports from YouTube video subtitles, providing insights into the thematic content of the video. Designed for efficiency and simplicity, it processes video subtitles without requiring an API key, making it an accessible solution for content analysis. The system assumes videos already have subtitles available, excluding live streams and videos without subtitle data. Key Features Trigger Webhook: Seamlessly receive video IDs through a webhook trigger. Fetch Video HTML: Retrieves the video’s HTML content directly from YouTube. Extract Subtitles URLs: Processes the HTML content to find and decode subtitle URLs. Fetch Subtitles Content: Downloads the subtitles from the decoded URLs in XML format. Generate Analytical Report: Utilizes an AI model to summarize and analyze the thematic essence of video content. The system supports models such as Google Gemini, OpenAI, and other compatible language models. The quality of the results may vary depending on the model used, with better models providing faster and more accurate summaries. The default prompt focuses on identifying and summarizing the main theme of the video while excluding content related to promotions, subscriptions, or sponsored content. Return Analytical Report: Delivers concise analytical reports as the final response to the webhook, suitable for various use cases like research, content creation, or consumption as plain text. Setup Instructions Step 1: Webhook Configuration Set up the webhook URL in your external system (e.g., app, API) to send YouTube video IDs to this workflow. Step 2: API Access Ensure that your environment has access to YouTube’s public HTML content. An API key is not required since the workflow parses publicly available data. Step 3: AI Integration Verify the connection to the AI model used for report generation. Supported models include Google Gemini and OpenAI. Note that the system can be customized by modifying the provided prompt to suit specific analysis needs. Step 4: Testing Run a sample test with a YouTube video ID to ensure subtitles are correctly retrieved and the report is generated successfully. Expected Outcomes Effortless Content Analysis:** Generate thematic reports with minimal setup. No API Key Dependency:** Simplified access by leveraging YouTube’s public HTML. Actionable Insights:** Gain valuable information on video content for business, research, or personal projects. Cost Considerations:** The execution cost depends primarily on the model used and the length of the video (affecting token usage). Leveraging the free tier of Google Gemini models is recommended to minimize costs. Main Theme Extraction:** The default prompt excludes irrelevant promotional content, providing clear and focused thematic summaries. Estimated setup time: 15–20 minutes with a ready environment. Prompt Description The workflow includes a customizable prompt used to process subtitles in XML format and generate analytical reports. The generated report includes: Title: A brief phrase capturing the essence of the main theme. Body: An analytical description of the main theme, structured into a maximum of three concise paragraphs. It focuses on summarizing key ideas, recurring themes, and connections without referencing the source explicitly (e.g., avoiding phrases like “this video”). The system also removes content related to sales, subscriptions, or promotions to maintain a clear thematic focus. Example Output Title: The Ethical Challenges of Artificial Intelligence Report: Artificial intelligence presents significant challenges in areas such as privacy, fairness, and automated decision-making. Its implementation in critical sectors such as healthcare, justice, and security has sparked debates about inherent biases and lack of transparency. Additionally, there is growing concern over the ethical implications of automation, including its impact on employment and the global economy. Finally, the importance of establishing strong regulatory frameworks is highlighted to balance technological innovation with the protection of human rights. An n8n automation workflow template by Mauricio Perera.

By Marcel Claus-Ahrens

Instructions This automation enables you to just upload any Image (via Form) of a Logo Sheet, containing multiple Images of Product Logos (most likely) which brings them in some context to one another. After submitting an AI-Agent eats that Logo Sheet, turning it into an List of "Productname" and "Attributes", also checks if Tools are kind of similar to another, given the Context of the Image. We utilize AI Vision capabilities for that. NOTE: It might not be able to extract all informations. For a "upload and forget it" Workflow it works for me. You can even run it multiple times, to be sure. But if you need to make sure it extracts everything you might need to think about an Multi-Agent Setup with Validation-Agent Steps. Once the Agent finishes the extraction, it will traditionally and deterministicly add those Attributes to Airtable (Creates those, if not already existing.) and also Upserts the Tool Informations. It uses MD5 Hashes for turning Product Names into.. something fancy really, you could also use it without that, but I wanted to have something that looks atleast like an ID. Setup Set Up the Airtable like shown below. Update and set Credentials for all Airtable Nodes. Check or Adjust the Prompt of the Agent matching your use-case. Activate the Workflow. Open the Form (default: https://your-n8n.io/form/logo-sheet-feeder) Enjoy growing your Airtable. Enjoy the workflow! ❤️ let the work flow — Workflow Automation & Development. An n8n automation workflow template by Marcel Claus-Ahrens.

By Danger

Automated Execution Pruning This workflow is designed to help you manage and optimize your n8n instance by automatically pruning old workflow executions, ensuring a cleaner environment and improved performance. You can customize the retention period to suit your needs. Key Features: Configurable Retention Period: The workflow is preconfigured to delete workflow executions older than 10 days. You can easily adjust this duration by modifying the condition in the If node. Daily Automation: Using the Schedule Trigger, the workflow runs daily at the specified time (default: 4:44 AM), retrieving all workflow executions and identifying those that are older than the defined retention period. On-Demand Testing: The Manual Trigger allows you to test the workflow at any time, ensuring everything is working as expected. Decision Making: The If node evaluates each execution based on its start date and determines whether it should be deleted or retained. Execution Pruning: Delete Action: Executions meeting the criteria are removed via the Delete Execution node. No-Operation: Executions that don't meet the criteria remain untouched. Workflow Nodes: Manual Trigger: Enables on-demand testing of the workflow. Schedule Trigger: Runs the workflow daily at the configured time. n8n List Execution: Fetches all executions in your n8n instance. If Node: Compares the execution's start date with the configured retention period. Delete Execution: Deletes executions older than the specified retention period. No Operation: Serves as a placeholder for executions that don't meet the pruning criteria. How to Customize: Retention Period**: Update the If node's condition to modify the retention period. For instance, change 10 * 24 * 60 * 60 * 1000 to the desired number of days in milliseconds. Schedule**: Adjust the timing of the Schedule Trigger to match your preferred automation schedule. This workflow ensures your instance remains efficient by keeping only the relevant execution logs. Use it to maintain a streamlined and clutter-free environment effortlessly. An n8n automation workflow template by Danger.