Workflow Templates

Who this template is for This template is for everyone who needs to work with XML data a lot and wants to convert it to JSON instead. Use case Many products still work with XML files as their main language. Unfortunately, not every software still supports XML, as many switched to more modern storing languages such as JSON. This workflow is designed to handle the conversion of XML data to JSON format via a webhook call, with error handling and Slack notifications integrated into the process. How this workflow works Triggering the workflow: This workflow initiates upon receiving an HTTP POST request at the webhook endpoint specified in the "POST" node. The endpoint, designated as , can be accessed externally by sending a POST request to that URL. Data routing and processing: Upon receiving the POST request, the Switch node routes the workflow's path based on conditions determined by the content type of the incoming data or any encountered errors. The Extract From File and Edit Fields (Set) nodes manage XML input processing, adapting their actions according to the data's content type. XML to JSON conversion: The XML data extracted from the input is passed through the "XML" node, which performs the conversion process, transforming it into JSON format. Response handling: If the XML-to-JSON conversion is successful, a success response is sent back with a status of "OK" and the converted JSON data. If there are any errors during the XML-to-JSON conversion process, an error response is sent back with a status of "error" and an error message. Error handling: in case of an error during processing, the workflow sends a notification to a Slack channel designated for error reporting. Set up steps Set up your own in the Webhook node. While building or testing a workflow, use a test webhook URL. When your workflow is ready, switch to using the production webhook URL. Set credentials for Slack.

This error handling workflow emails detailed notifications on workflow execution and trigger errors. It extends Send email via Gmail on workflow error template by covering trigger-level errors. Features Get notifications on both main workflow trigger and execution time errors. Subject line will have failed workflow id, name, error source (execution or trigger), error message. Body will contain links to both failed and error handling workflows as well as execution or trigger-level error details. Body will also contain a machine readable and enriched JSON from Error Trigger describing the error. Use this error handling workflow for as many workflows as you need. Configiration Copy this workflow to your workspace and, optionally, move it under the project that contains your main workflow In this error handling workflow settings, set This workflow can be called by as appropriate In Config node, define your app url, notifications recipient email, and sender name (useful to build filters in your inbox) In Gmail node, create and select credentials In your main workflow settings, pick this error handling workflow in the Error Workflow field (How to...) Related resources n8n Error Trigger documentation. Author Reach out Olek on community.n8n.io Olek on n8n creators hub

🧲 AI-Powered Lead Magnet Idea Generation from Topic List This n8n workflow automatically generates lead magnet ideas based on topics and website URLs stored in a Google Sheet. It uses the Lead Magnet Idea Generator AI API to produce relevant, value-driven ideas that marketers can turn into checklists, guides, templates, and more. 🔧 What This Workflow Does Monitors a Google Sheet for new or updated rows using a Drive trigger. Reads all rows and identifies entries where: The Topic column is not empty The Content (idea) column is empty Sends a request to the Lead Magnet Idea Generator AI API: Input: Topic + Website URL Output: AI-generated lead magnet idea Writes the idea back to the same Google Sheet with a timestamp. Repeats the process automatically every minute. 🌐 API Used Name:** Lead Magnet Idea Generator AI API Endpoint:** https://lead-magnet-idea-generator-ai.p.rapidapi.com/index.php Method:** POST Headers:** x-rapidapi-host: lead-magnet-idea-generator-ai.p.rapidapi.com x-rapidapi-key: YOUR_RAPIDAPI_KEY Body Params:** topic website ✅ Benefits | Feature | Value | |----------------------------------|------------------------------------------------------------------| | 🔄 Automated Flow | No manual entry needed — runs every minute | | 🧠 AI-Based Content Ideation | Smart suggestions tailored to your topic and brand | | 📝 Google Sheets Integration | Easy to manage, edit, and view input/output in one place | | 🕒 Timestamp Tracking | Know exactly when each idea was generated | | 🚫 No Duplicate Processing | Only rows missing ideas are sent to the API | | 💼 Scalable for Teams | Plug-and-play for any team managing multiple content ideas | ❌ Challenges This Solves | Old Challenge | New Workflow Solution | |--------------------------------------------|------------------------------------------------------------------| | Manual brainstorming of lead magnet ideas | Fully automated idea generation via API | | Missing or inconsistent content in sheets | Only incomplete rows are updated with valid ideas | | Lack of traceability | Timestamp logs show when each idea was generated | | Wasting time on repetitive tasks | Workflow handles idea generation while you focus on execution | 📌 Requirements ✅ A valid RapidAPI key ✅ Google Sheets & Google Drive credentials set up in n8n ✅ Google Sheet structured with the following columns: | Column Name | Purpose | Required | |------------------|----------------------------------------------------------|----------| | Topic | Main subject for which the idea is generated | ✅ Yes | | Website Url | Optional URL to provide brand context for the API | ❌ No | | Content | Will be filled with the AI-generated lead magnet idea | ✅ Yes | | Generated Date | Timestamp when the idea was created | ✅ Yes | 🧩 Technologies Used n8n** – Automation platform Google Sheets** – For storing topics and generated ideas Google Drive Trigger** – To initiate the workflow Lead Magnet Idea Generator AI API** – For content generation HTTP Request node** – To communicate with the API If / Wait / Split In Batches nodes** – For conditional logic and throttling 🧠 Example Use Cases Content marketing teams planning lead magnets for blog posts Agencies creating assets for multiple clients Email list-building strategists generating downloadable content ideas Business owners who want quick suggestions without manual brainstorming 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!

Drowning in security alerts? Spending hours translating technical logs from Wazuh, your SIEM, or other tools into business-friendly reports for leadership? This n8n workflow is your automated Security Analyst, designed to save you time and bridge the communication gap between technical teams and non-technical executives. Using a powerful two-stage AI process via the NixGuard Security RAG connector, this workflow transforms raw security event data into a concise, actionable daily briefing. How It Works: Stage 1: Intelligent Filtering & Data Structuring: On a daily schedule, the workflow first calls the AI to sift through all recent security events. It intelligently identifies significant alerts and structures them into a clean, machine-readable JSON array, cutting through the noise. Stage 2: Executive Summarization: If critical alerts are found, the workflow feeds this structured JSON into a second AI prompt. It tasks the AI to act as a Senior Security Analyst, generating a high-level summary that focuses on business impact, key threat patterns, and a clear, single recommendation—all in plain English. Automated Delivery: The final Markdown report is automatically converted to HTML and emailed as a professional daily security briefing to your stakeholders. Key Features & Benefits: Slash Reporting Time:** Automate the manual, time-consuming process of daily security analysis and reporting. Bridge the Technical Gap:** Deliver clear, non-technical summaries that executives can understand and act upon instantly. Reduce Alert Fatigue:** Let AI filter out the low-level noise and only escalate what truly matters. Two-Stage AI Processing:** Leverage a sophisticated AI chain for more accurate and relevant results than a single prompt. Highly Customizable:** Easily adapt the prompts, schedule, and data sources (any system compatible with the NixGuard RAG connector) to fit your exact needs. Who is this for? Security Analysts, Engineers, and Managers** who need to automate daily reporting. SecOps and DevOps Teams** looking to integrate security intelligence into their automated workflows. IT Directors and VPs** who need to provide consistent security posture updates to leadership. Anyone responsible for communicating cybersecurity risk to non-technical stakeholders. Stop copying and pasting logs. Download this workflow to automate your security reporting and deliver real business value today! Don't have the main workflow yet? Get it HERE! 🔗 Learn more about NixGuard: thenex.world 🔗 Get started with a free security subscription: thenex.world/security/subscribe Tags / Keywords: AI, Security, Automation, Cybersecurity, Wazuh, SIEM, Reporting, Executive Summary, Daily Briefing, Alert Fatigue, SecOps, Generative AI, LLM, NixGuard, Email, JSON

This workflow is your ultimate solution for reliable image retrieval from any web source, including those heavily protected. It operates with a smart, cost-effective strategy: it first attempts to fetch the image using a Classic Image Getter node (a standard, free HTTP request). In approximately 80% of cases, this method will be sufficient. However, for the remaining instances where you encounter IP blocking, CAPTCHAs, rate limiting, or other advanced anti-bot measures, the workflow seamlessly switches to a robust BrightData Web Unblocker service as a fallback. It leverages BrightData’s Image Unblocker to retrieve these blocked images. This template is indispensable for anyone needing consistent and complete access to web images, ensuring you get the data you need without unnecessary overhead. Why Use This Image Scrapper Workflow? Maximum Success Rate**: Retrieves images even from the most challenging or protected websites. Cost-Optimized Strategy**: Prioritizes free, standard HTTP requests, only incurring costs when advanced unblocking is truly necessary. Automated Resilience**: Intelligently handles failed direct attempts by automatically engaging the BrightData failover via the "Unlock Image" node. Versatile Image Scraping**: Perfect for market research, content aggregation, or data enrichment that demands reliable image access. How It Works When clicking ‘Execute workflow’: The workflow is initiated manually, allowing for easy testing and integration into larger processes. image: A Set node defines the target image URL. This can be easily configured to accept dynamic URLs from preceding nodes. Classic Image Getter: This HTTP Request node performs a direct image download. It's the primary, free, and efficient method for readily accessible images. Unlock Image (BrightData Web Unblocker): Configured as an error handler and failover, this HTTP Request node activates only if the "Classic Image Getter" encounters an error. It then routes the image URL through BrightData's Web Unblocker, designed to bypass advanced protective measures and successfully retrieve the image data. 🔑 Prerequisites To enable the advanced capabilities of this workflow, specifically the BrightData Web Unblocker functionality, you will need a BrightData account and a correctly configured Web Unblocker zone. Setting Up Your BrightData Web Unblocker: BrightData Account: Ensure you have an active account with BrightData. If you don't, you can sign up on their website. Create a Web Unblocker Zone: Log in to your BrightData dashboard. Navigate to the "Proxy & Scraping Infrastructure" section, then "Zones." Click "Add new zone." Select "Web Unblocker" as the product type. Give your zone a clear name (e.g., n8n-image-unlocker). Confirm the creation of the zone. Retrieve API Key: Once your Web Unblocker zone is active, go to its settings. Locate your API Key (often referred to as "password" for proxy access) within the "Access Parameters" or "Credentials" section. Configure in n8n: In the Unlock Image HTTP Request node within this workflow, update the Authorization header. Replace "Bearer yourkey" with "Bearer YOUR_BRIGHTDATA_API_KEY". Important: For production workflows, it's highly recommended to use n8n credentials to store your BrightData API key securely, rather than hardcoding it directly in the node. This template uses a placeholder for demonstration purposes. Crucially, ensure that the zone parameter in the Unlock Image node matches the exact Zone ID you created in your BrightData account. You will need to replace the placeholder web_unlocker with your actual BrightData zone ID. Phil | Inforeole

TikTok Transcript to OpenAI GPT-4 This automation workflow provides a seamless, efficient, and AI-powered solution for extracting, processing, and storing TikTok video subtitles. By combining TikTok Transcript API, OpenAI GPT-4 API, and Google Docs, this workflow transforms the process of transcription and text analysis into a smooth, automated experience. It's perfect for content creators, marketers, and businesses who need to process large volumes of TikTok videos and want to leverage AI for language processing and summarization. How It Works: User Form Submission: The process begins when a user submits a TikTok video URL and specifies the language in which they want the processed content. The data is captured via a simple form that triggers the entire workflow. The form is crucial for collecting the necessary parameters before processing, such as the video link and language preferences. Fetching Subtitles from TikTok: The workflow uses the TikTok Transcript API to retrieve subtitles from the specified TikTok video. This API extracts all textual data associated with the video (including spoken words, captions, etc.) in real-time. The TikTok Transcript API allows you to fetch subtitles efficiently, making it ideal for those who need to process content from TikTok quickly. Advanced Processing with OpenAI GPT-4: Once the TikTok subtitles are fetched, the workflow sends this text to OpenAI’s GPT-4 API. OpenAI's GPT-4 model is renowned for its powerful natural language processing capabilities, making it perfect for handling multi-lingual data. OpenAI GPT-4 API processes the raw transcript in several ways, including: Translation: If the subtitles are in a different language, GPT-4 API can translate them to the desired language. Summarization: GPT-4 API can summarize long TikTok video subtitles into concise points, saving you time and effort. Text Interpretation: You can configure GPT-4 API to generate insights, analyze emotions, or interpret context, which is ideal for detailed content analysis. Storing the Results in Google Docs: After processing the subtitles, the final output (whether it is a translated, summarized, or interpreted version) is automatically saved into a Google Doc. This integration allows the processed text to be stored in an easily editable and shareable format. The document can be accessed by anyone with permission, making it perfect for team collaboration or content management. Workflow Automation: The automation continues with a wait step to ensure that all data is fetched and processed before moving on to storing it in Google Docs. It ensures that the entire process is handled without needing manual intervention, from fetching subtitles to generating results and storing them. Key Features and Benefits: Efficient TikTok Subtitle Extraction: Automatically fetch TikTok video subtitles using the **TikTok Transcript API, eliminating the need for manual transcription. AI-Driven Text Processing: Use the power of **OpenAI GPT-4 API to process the extracted text. GPT-4 API can translate, summarize, or analyze the subtitles for advanced insights, making it far more than just a transcription tool. Seamless Multi-Language Support: **OpenAI GPT-4 API handles multiple languages, translating or summarizing the content based on the user’s input. This makes the workflow versatile for global content creators and marketers. Google Docs Integration: After processing the subtitles, the results are saved directly into **Google Docs for easy access, editing, and sharing. This ensures that all processed data is stored in an organized manner and ready for use in various projects. Time & Effort Savings**: The entire process is automated from start to finish, allowing users to bypass manual transcription and processing tasks. You can focus on creating content while the workflow handles all the repetitive tasks. Advanced Text Insights: By using **OpenAI’s GPT-4 API, you not only get the raw transcript, but you also get insights, summaries, translations, and other interpretations that enhance your content’s value. Challenges Solved: Manual Transcription: This workflow eliminates the need for manual transcription by automatically fetching subtitles from TikTok using the **TikTok Transcript API. Language Barriers: With **OpenAI GPT-4, users can translate TikTok video subtitles into any language, ensuring the content is accessible to a global audience. Content Management: By storing processed content in **Google Docs, this workflow makes it easier to manage and collaborate on transcriptions and analysis, providing a central hub for your data. Automation for Productivity**: This workflow automates every step of the process, from fetching subtitles to analyzing and storing them, freeing up time for higher-value tasks like content creation, strategy planning, or marketing. APIs Integrated: TikTok Transcript API**: Retrieves subtitles directly from TikTok videos, providing the base for further processing. OpenAI GPT-4 API**: Handles advanced text processing, including translation, summarization, and analysis of the TikTok video subtitles. Google Docs API**: Stores processed content into Google Docs, providing a clean, accessible format for viewing and collaboration. Use Cases: Content Creation**: Automatically process and summarize video subtitles for content creation, marketing, or research purposes. Market Research**: Extract and analyze content from TikTok to understand audience sentiment, trending topics, and engagement strategies. Education**: Teachers and educators can use the workflow to analyze educational TikTok videos and save the insights in Google Docs for lesson planning. Conclusion: This TikTok Transcript to OpenAI GPT-4 + Google Docs Automation workflow saves time, enhances content processing with AI, and organizes results into easily accessible documents. By integrating the TikTok Transcript API and OpenAI GPT-4 API, it provides a smart, automated solution for anyone working with TikTok content. Whether you're a content creator, researcher, or marketer, this workflow can help you streamline and optimize your content processing tasks.

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.

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. How it Works: - Accepts a domain from a web form - Generates a list of Google dorks targeting that domain - Scrapes Google search results for each dork - Filters out junk links (Google internal, non-http) - Formats valid results as a markdown report - Emails the report to your inbox For this workflow you will need to configure credentials in n8n as well as create a Parsera.io agent: 1. AI Scraper Account Create an account for: https://app.parsera.io Create an agent named "Google" and use the URL https://google.com Copy/Paste your Parsera.io API key to the 'Scrape with agent' node in the n8n workflow 2. Gmail OAuth2 Go to Google Cloud Console Enable Gmail API Create OAuth2 credentials Copy/Paste the Gmail API key to the Gmail node in the n8n workflow

Perplexity API Module This reusable workflow allows you to interact with the Perplexity API using the sonar or sonar-pro models. It is designed to be triggered from other workflows and accepts dynamic prompts via input parameters. Features 🧱 Modular: Triggered using Execute Workflow from any other workflow 📥 Inputs: SystemPrompt: Set your system-level instruction for the LLM UserPrompt: The main user prompt for the conversation 🧠 Uses Perplexity’s chat/completions endpoint 🔐 Built with API authentication in mind (Bearer token or header auth) 🔁 Easily extendable for any model in the Perplexity suite Models supported sonar sonar-pro See full model list and capabilities Usage Set up your credentials in n8n under HTTP Bearer or Header Auth. Add this workflow as a subworkflow using the “Execute Workflow” node. Pass the desired SystemPrompt and UserPrompt as input variables. Receive the model response in return. Notes This template is inactive by default and safe to import. Includes sticky notes with API references and model info.

This workflow shows a no code approach to creating Salesforce accounts and contacts based on data coming from Google Sheets. To run the workflow: Make sure you have both Google Sheets and Salesforce authenticated with n8n. Have a Google Sheet with contacts and their account names ready, copy the respective sheet ID from the URL: Add the sheet ID to the Google Sheet node of the workflow: Hit Execute Workflow Here is how it works: The workflow first searches for existing Salesforce accounts by name. It then branches out depending on whether the account already exists in Salesforce or not. If an account does not exist yet, it will be created. The data is then normalised before both branches converge again. Finally the contacts are created or updated as needed in Salesforce.

Description This template will help you verify that incoming calls from a Slack webhook actually come from Slack and not some unknown third-party services. It is mainly used to prevent attacks from malicious bots or individuals. This is a Sub-Workflow, so it should be used inside the main workflow that contains the webhook listening for Slack requests. How to Use What to Edit You should set the Slack Signing Secret that you can find on your Slack App dashboard in the general tab. It should be located under the following URL: https://api.slack.com/apps/[SLACK_APP_ID]/general Input The input should be the received Slack request. This workflow should then be placed directly after the Slack Webhook. Outputs Success Output If the signature was verified successfully, we return a key verified_signature set to true along with data from the Slack request itself. Error Output When the signature could not be verified, we raise an error. You can handle this case in your main workflow by using an Error Workflow or by changing your node settings and choosing some actions in case of an error. Changelog Version 1.0.1 (2023-12-11) Changed replace by replaceAll in JS code in case of several arguments. Added some custom replacements that encodeURIComponent does not take into account

This workflow automates the daily backup of all your n8n workflows to a designated folder in Nextcloud. It ensures that you always have the last 7 days of backups available while automatically deleting older ones to save space. 🔧 Features Scheduled Trigger: Runs automatically once per day (can be executed manually as well). Directory Management: Creates the /N8N-Backup directory in Nextcloud if it doesn't already exist. Backup Collection: Retrieves all workflows from the n8n instance. JSON Conversion: Converts each workflow into a JSON file. Upload to Nextcloud: Saves each backup file into the specified backup directory. Retention Control: Keeps only the latest 7 backups and deletes the rest from Nextcloud. 📌 Notes Make sure to manually create the /N8N-Backup directory in your Nextcloud account before using this flow. Update the Backup Path node if you wish to change the upload directory. Ideal for teams using n8n with self-hosted instances and requiring offsite backup via Nextcloud. 🔒 Requirements n8n instance with access to the Nextcloud node. Valid credentials for your Nextcloud account with API access. Update: 08/11/2025 “Backup Flows to Nextcloud” – Import format fixed Summary: The workflow now exports one clean JSON object per workflow (no arrays, no backup/meta fields), so files can be imported 1:1 via the n8n UI. What changed: Switched from “Convert to File” to a Set node that builds the JSON in binary data. Enabled filters.include = "all" on Get many workflows to include nodes, connections, settings, pinData, and tags. Sanitized filenames and removed IDs/metadata that can break UI imports. Fixed Nextcloud path and binary property mapping (data). Verification: Generated multiple backups and imported each via UI (“Import from file”) without errors. Each file begins with { (single object) and loads with full workflow structure. Notes: Keep “Binary Property” set to data in the Nextcloud node. Filenames are sanitized to avoid special-character issues.