Workflow Templates

v1 Helper ℹ️ This workflow is to be run after upgrading to n8n v1. This workflow returns all locations where a node in an active workflow contains a parameter using an expression extension affected by v1 changes. For every location, please check that the workflow still behaves as intended.

The workflow starts by listening for messages from Telegram users. The message is then processed, and based on its content, different actions are taken. If it's a regular chat message, the workflow generates a response using the OpenAI API and sends it back to the user. If it's a command to create an image, the workflow generates an image using the OpenAI API and sends the image to the user. If the command is unsupported, an error message is sent. Throughout the workflow, there are additional nodes for displaying notes and simulating typing actions.

This n8n workflow serves as a powerful cybersecurity and threat intelligence tool to look up URLs or IP addresses through industry standard threat intelligence vendors. It starts with either a form submission or a webhook trigger, allowing users to input data, URLs or IPs that require analysis. The workflow then splits into two paths depending on whether the input data is an IP or URL. If an IP was given, it sets the ip variable to the IP; however if a URL was given the workflow will perform a DNS lookup using Google Public DNS and sets the ip variable based on the results from Google. The workflow then checks the obtained IP addresses against GreyNoise services, with one branch utilizing GreyNoise RIOT IP Lookup to assess IP reputation and association with known benign services, and the other using GreyNoise IP Context to evaluate potential threats. The results from both GreyNoise services are merged to create a comprehensive analysis which includes the IP, classification (benign, malicious, or unknown), IP location, tags to identify activity or malware, category, and trust level. In parallel, a VirusTotal scan is initiated for the URL/IP to identify if it is malicious. A 5-second wait ensures proper processing, and the workflow subsequently polls the scan result to determine when the analysis is complete. The workflow then summarizes the analysis including the overall security vendor analysis results, blockList analysis, OpenPhish analysis, the URL, and the IP. Finally, the workflow combines the summarized intelligence from both GreyNoise and VirusTotal to provide a thorough analysis of the URL/IP. This summarized intelligence can then be emailed to the user that filled out the form via Gmail or it can be sent to the user via a Slack message. Setting up this workflow may require proper configuration of the form submission or webhook trigger, and ensuring that the GreyNoise and VirusTotal API credentials are correctly integrated. Users should also consider the potential volume of data and API rate limits, as excessive requests could lead to issues. Proper documentation and validation of input data are crucial to ensure accurate and meaningful results in the final report.

This n8n workflow is designed for security monitoring and incident response when suspicious login events are detected. It can be initiated either manually from within the n8n UI for testing or automatically triggered by a webhook when a new login event occurs. The workflow first extracts relevant data from the incoming webhook payload, including the IP address, user agent, timestamp, URL, and user ID. It then splits into three parallel processing paths. In the first path, it queries GreyNoise's Community API to retrieve information about the investigated IP address. Depending on the classification and trust level received from GreyNoise, the alert is given a High, Medium, or Low priority. This priority is assigned based on the best practices documentation from GreyNoise on how to apply their data to analysis. Once a priority is assigned, a message is sent to a Slack channel to notify users about the alert. The second path involves fetching geolocation data about the IP address using IP-API's Geolocation API and merging it with data from the UserParser node. This data is then combined with the data obtained from GreyNoise. In the third path, the UserParser node queries the Userparser IP address and user agent lookup API to obtain information about the user's IP and user agent. This data is merged with the IP-API data and GreyNoise data. The workflow then checks if the IP address is considered an unknown threat by examining both the noise and riot fields from GreyNoise. If it is considered an unknown threat, the workflow proceeds to retrieve the last 10 login records for the same user from a Postgres database. If there are any discrepancies in the login information, indicating a new location or device/browser, the user is informed via email. Potential issues when setting up this workflow include ensuring that credentials are correctly entered for GreyNoise and UserParser nodes, and addressing any discrepancies in the data sources that could lead to false positives or negatives in threat detection. Additionally, the usage of hardcoded API keys should be replaced with credentials for security and flexibility. Thorough testing and validation with sample data are crucial to ensure the workflow performs as expected and aligns with security incident response procedures.

What Problem Does it Solve This workflow automates the process of finding and collecting job postings from LinkedIn, eliminating the need for manual job searching. It’s designed to save time and ensure you don’t miss out on new opportunities by automatically populating a spreadsheet with key job details. Key Features Automated Data Collection:** The workflow pulls job posts from a LinkedIn search via an RSS feed. Intelligent Data Extraction:** It scrapes the full job description and uses AI to summarize the key benefits and job responsibilities into a concise format. Centralized Database:** All collected and processed information is automatically saved to a Google Sheet, providing a single source of truth for your job search. How It Works The workflow starts when manually triggered. It reads the job posts from a given RSS feed, processing each one individually. For each job, it fetches the full webpage content to extract structured data. This data is then cleaned and passed to an AI model, which generates a brief summary of the job and its benefits. Finally, a new row is either added or updated in a Google Sheet with all the collected details, including the job title, company name, and AI-generated summary. Configuration & Customization This workflow is highly customizable to fit your specific needs. RSS Feed:** To get started, you'll need to provide the RSS feed URL for your desired LinkedIn job search. We can help you set this up. AI Model:** The workflow uses Google Gemini by default, but it can be adjusted to work with other AI platforms. Data Destination:** The output is configured to a Google Sheet, but it can easily be changed to a different platform like Notion or a CRM. AI Prompting:** The AI's instructions are customizable, so you can tailor the output to extract different information or match a specific tone. If you need any help Get In Touch

This workflow allows you to create, add an attachment, and send a draft using the Microsoft Outlook node. Microsoft Outlook node: This node creates a draft message with HTML content. You can either set the content as Text or HTML. You can also add the recipients to the draft in this node. HTTP Request node: This node fetches the logo of n8n from a URL and returns the binary data. You might want to fetch files from your machine or another email or a database. You can replace this node with the relevant node. Microsoft Outlook1 node: This node adds the attachment that we receive from the previous node to the draft message that we created. Microsoft Outlook2 node: This node sends the draft message to a recipient. Since we didn't mention the recipient in the Microsoft Outlook node, we add the recipient in this node. You can also enter multiple recipients.

This n8n workflow is designed to analyze email headers received via a webhook. The workflow splits into two main paths based on the presence of the received and authentication results headers. In the first path, if received headers are present, the workflow extracts IP addresses from these headers and then queries the IP Quality Score API to gather information about the IP addresses, including fraud score, abuse history, organization, and more. Geolocation data is also obtained from the IP-API API. The workflow collects and aggregates this information for each IP address. In the second path, if authentication-results headers are present, the workflow extracts SPF, DKIM, and DMARC authentication results. It then evaluates these results and sets fields accordingly (e.g., SPF pass/fail/neutral). The paths merge their results, and the workflow responds to the original webhook with the aggregated analysis, including IP information and authentication results. Potential issues during setup include ensuring proper configuration of the webhook calls with header authentication, handling authentication and API keys for the IP Quality Score API, and addressing any discrepancies or errors in the logic nodes, such as handling SPF, DKIM, and DMARC results correctly. Additionally, thorough testing with various email header formats is essential to ensure accurate analysis and response.

🧾 Automated Invoice Processing - n8n Workflow 📖 Workflow Description This n8n workflow automates the complete processing of PDF invoices with AI-powered data extraction. The workflow monitors a Google Drive folder, extracts important invoice data, and automatically organizes files in a structured filing system. 🎯 Features 🔍 Automatic monitoring** of a Google Drive folder for new PDF files 🤖 AI-powered data extraction** from invoices (customer, amount, date, etc.) 📁 Intelligent file sorting** by year and month 📝 Automatic renaming** following a consistent schema 📊 Central documentation** in Google Sheets 🔧 Required Integrations Required Accounts: Google Drive (with folder permissions) Google Sheets (with write permissions) Google Gemini API (for AI data extraction) Used n8n Nodes: Google Drive Trigger Google Drive (File Operations) Google Sheets Extract from File (PDF) Information Extractor (LangChain) Google Gemini Chat Model Split in Batches 📋 Workflow Steps in Detail 1. Monitoring & Triggering Google Drive Trigger** monitors a defined input folder Automatically starts when new PDF files are detected Split in Batches** enables batch processing of multiple files 2. File Processing GetFile** downloads PDF files from Google Drive ExtractFromPDF** converts PDF content to text Supports scanned documents as well 3. AI Data Extraction The Information Extractor node with Google Gemini extracts: Company name/sender Customer name and customer number Invoice number and date Net and gross amount Value-added tax Article description Month and year (for sorting) 4. Automatic Filing GetYearFolder** searches/creates year folders GetMonthFolder** searches/creates month folders MoveFile** moves invoice to correct folder UpdateFileName** renames file (schema: "Customer Month Year") 5. Documentation AddToOverview** enters all data into Google Sheets table Enables central overview and analysis ⚙️ Setup Instructions Step 1: Prepare Google Drive Create the following folder structure in Google Drive: 📁 [Input Folder] (e.g., "Invoices-Inbox") 📁 [Main Folder] (e.g., "Accounting") └── 📁 2024 ├── 📁 January ├── 📁 February ├── 📁 March └── ... (all months) └── 📁 2025 └── ... (all months) Step 2: Create Google Sheets Table Create a spreadsheet with the following columns: Customer Number Customer [Company Name] Location Invoice Date Invoice Number VAT Net Amount Month Year Step 3: Configure Workflow Configure Google Drive Trigger: Select your input folder as "Folder to Watch" Set "Event" to "fileCreated" Activate the trigger Search files and folders: Select the same input folder as filter Customize Information Extractor: Adapt attribute names to your needs Change company name in description Adjust system prompt if needed GetYearFolder & GetMonthFolder: Set the correct folder ID for your main folder Check query string for year/month search AddToOverview: Select your Google Sheets table Map columns according to your table 🔧 Customization Options Extend Data Extraction: Add more attributes in the Information Extractor node: { "name": "Payment Terms", "description": "Days until payment due", "required": false } Customize File Naming: Change the schema in the UpdateFileName node: "{{ $('Information Extractor').item.json.output.InvoiceNumber }} - {{ $('Information Extractor').item.json.output.Customer }}" Change Monitoring Interval: In Google Drive Trigger under "Poll Times" select different intervals. 🚨 Important Notes ⚠️ Permissions: Google Drive: Full access to configured folders Google Sheets: Write permission for target table Google Gemini: Valid API key required 📝 Data Format: Works with German number formats (comma as decimal separator) Date format: YYYY-MM-DD Supports various PDF formats 🔄 Error Handling: Workflow fails if folders are missing Incomplete PDFs may lead to incomplete extractions Check logs for troubleshooting 📊 Performance & Limitations Processing time:** 30-60 seconds per invoice Supported formats:** PDF (text and OCR) Batch processing:** Yes, multiple files simultaneously AI accuracy:** ~95% for standardized invoices 🧪 Testing Run Test: Upload a test PDF to the input folder Monitor workflow execution in n8n Check results in Google Sheets Verify correct file movement and renaming Error Diagnosis: For errors: check n8n logs Consider Google API quotas Validate folder permissions 📄 License & Support This workflow can be used and customized freely. For configuration questions or issues, check the n8n community or Google API documentation. Tip: Start with a few test invoices before using the workflow in production!

This n8n workflow template allows you to write WordPress posts by just providing a few keywords. It uses AI technology to write the text and to create the post's featured image. The text includes an introduction, chapters, and conclusions. Each chapter is written independently and this allows you to create also very long articles. The workflow uses technologies provided by Open AI: Chat GPT for the text and Dall-E for the image. I suggest reviewing the created posts before publishing them on your WordPress website. The article generation might take some minutes as each chapter is created independently. Features Easy to use:** Easy web interface to start the generation of the WordPress post AI-powered:** Text and image generation is done by artificial intelligence Long-text ready:** Possibility to create very long articles Configurable:** Possibility to provide as many keywords as you want, to choose the number of chapters and the length of the article Plugs into your WordPress:** Easily integrates with your WordPress website Tweak it as you want:** Fine-tune the Open AI prompts and the workflow as you want Workflow Steps User form:** An n8n form is used to trigger the post creation Settings:** This node is used to set your WordPress URL (which is used later in the workflow) Article structure:** First AI action that writes the introduction, the conclusions, and the chapter structure. Data check:** Check that the data provided by the AI is valid Chapters split/Chapters text:** Splits the data for each chapter in a separate item and generates each chapter's text with AI Content preparation:** Prepares the text for posting merging the introduction, the chapters, and the conclusions. Adds some basic HTML formatting Draft on WordPress:** Creates the draft post on WordPress Featured image:** Creates a featured image and adds it to the post on WordPress User feedback:** Sends a feedback to the user on the n8n form Getting Started To deploy and use this template: Import the workflow into your n8n workspace Set your WordPress URL in the wordpress_url field in the "Settings" node. Include the slash (/) at the end of the URL Set up your Open AI n8n credentials by following this guide. The Open AI credentials are used by the Open AI nodes ("Create post title and structure", "Create chapters text", and "Generate featured image") Set up your WordPress n8n credentials by following this guide. The WordPress credentials are used by the WordPress and HTTP Request nodes ("Post on Wordpress", "Upload media", and "Set image ID for the post"). Pay attention that the "Password" in the WordPress credentials is not the user's password by the Application Password How use the workflow to create a WordPress post Activate the workflow Open the "Form" node and copy the "Production URL". This is the public URL of the form to AI-write the post Open the URL in a browser and fill in the form Wait a few minutes till you get the feedback in the form that the post was created Go to WordPress and check the newly created draft post. Review and publish your post!

This AI-powered customer support automation built in n8n handles your e-commerce queries instantly — from order tracking to personalized product recommendations and support ticket management. Features: 🛒 Order Status Tracking: Instantly retrieve order details from your database. 🎯 AI Product Recommendations: GPT-powered suggestions based on customer preferences. 📩 Support Ticket Automation: Auto-create and manage tickets via email or CRM. 🔄 Context-Aware Conversations: AI agent with memory for smooth follow-ups. ⚡ Real-Time Webhook Responses: Instant, API-driven replies to customers. Tech Stack: n8n, OpenAI GPT, Webhooks, Supabase, Email API. Perfect for Shopify, WooCommerce, and custom e-commerce platforms looking to reduce response times and improve customer satisfaction.

This powerful n8n workflow helps you automatically re-engage cold leads by summarizing their past emails and generating personalized outreach with OpenAI. It pulls in contacts from Google Sheets, fetches their prior communication from Outlook, and then uses an AI agent to analyze, strategize, and write a draft re-engagement message — all automatically. ⚙️ What the Workflow Does 📄 Get Contacts from Google Sheets Pulls a list of contacts and their email addresses from a Google Sheet. 📥 Search Emails from Outlook For each contact, fetches all emails received from that address since January 1, 2025. 📊 Aggregate Emails Merges relevant email fields (subject, body, createdDateTime) into a single string for analysis. 🧠 Use OpenAI to Analyze and Draft Response AI Agent summarizes the lead’s communication history. Suggests how to re-engage them in bullet points. Writes a personalized draft email to re-initiate the conversation. 📝 Save to Google Sheets Appends or updates the original row with: Summary of communication Re-engagement ideas Suggested subject line Suggested email body 📤 Create Draft Email in Outlook Creates a draft email in your Microsoft Outlook account using the subject and body provided by OpenAI. The email is not sent automatically — giving you a chance to review and personalize further. 🧰 What You'll Need 🔐 Google Sheets API connection** OAuth2 credential setup in n8n Make a copy of this sample sheet 🔐 Microsoft Outlook OAuth2 connection** Connected inbox with access to historical messages 🔐 OpenAI API Key** Add your OpenAI key in the OpenAI Chat Model node Recommended model: gpt-4o-mini or higher 👨‍💼 Built By Robert Breen Automation Consultant | n8n Expert | Data Strategist 🔗 Website: https://ynteractive.com 📧 Email: robert@ynteractive.com 💼 LinkedIn: https://www.linkedin.com/in/robert-breen-29429625/ 🏷 Tags openai outlook email reengagement lead nurturing automation google sheets ai email gpt-4o crm sales automation

⚡ UPDATE on May 2025 – added section with all n8n instance webhooks Using n8n a lot? Soar above the limitations of the default n8n dashboard! This template gives you an overview of your workflows, nodes, and tags – all in one place. 💪 Built using XML stylesheets and the Bootstrap 5 library, this workflow is self-contained and does not depend on any third-party software. 🙌 It generates a comprehensive overview JSON that can be easily integrated with other BI tools for further analysis and visualization. 📊 Reach out to Eduard if you need help adapting this workflow to your specific use-case! 🚀 Benefits: Workflow Summary** 📈: Instant overview of your workflows, active counts, and triggers. Left-Side Panel** 📋: Quick access to all your workflows, nodes, and tags for seamless navigation. Workflow Details** 🔬: Deep dive into each workflow's nodes, timestamps, and tags. Node Analysis** 🧩: Identify the most frequently used nodes across your workflows. Tag Organization** 🗂️: Workflows are grouped according to their tags. Webhooks** ⚡: List of all webhook endpoints with the links to workflows. Visually Stunning** 🎨: Clean, intuitive, and easy-to-navigate dashboard design. XML & Bootstrap 5** 🛠️: Built using XML stylesheets and Bootstrap 5, ensuring a self-contained and responsive dashboard. No Dependencies** 🔒: The workflow does not rely on any third-party software. Bootstrap 5 files are loaded via CDN but can be delivered directly from your server. ⚠️ Important note for cloud users Since the cloud version doesn't support environmental variables, please make the following changes: get-nodes-via-jmespath node. Update the instance_url variable: enter your n8n URL instead of {{$env["N8N_PROTOCOL"]}}://{{$env["N8N_HOST"]}} Create HTML node. Please provide the n8n instance URL instead of {{ $env.WEBHOOK_URL }} 🌟Example: Follow me on LinkedIn for more tips on AI automation and n8n workflows!