Workflow Templates

This workflow automatically finds verified and nominative email and all information (with Dropcontact) to prospect properly from a Typeform. Typeform Trigger**: This node triggers the workflow when a new Typeform is submitted. Dropcontact**: This node fetches the new contact information and returns the data of the person and the company associated with the email address, job function, and all legal information. Airtable - List**: This will list all the entries from your table in order to check if the subscriber is new or not. If**: Does the contact exist in your Airtable yet? Set**: Set values on the Airtable values Airtable Update**: This node updates your record with new and up-to-date data Airtable - Create**: This node creates a new record when the subscriber is a new lead Slack**: This node sends an alert when the record is added or updated

How it Works: You can now use the Slack node to create conditional breakpoints! This example shows the loop stop on 4 (of 10) and then you can hit "continue" in Slack when you are ready. You could extend this with a Form node and inject values you type in on the fly. Slack was already the best place to debug log n8n, and now it just got better!

Store a key with a value in a local json file. Multiple keys could be saved in a single file. Related workflow: GetKey Create a subfolder in your n8n homedir: /home/node/.n8n/local-files. In docker look at the data path and create a subfolder local-files. Set the correct access rights chmod 1000.1000 local-files. Put the workflow code in a new workflow named WriteKey. Create another workflow with a function item: return { file: '/4711.json', // 4711 should be your workflow id key: 'MyKey', value: 'MyValue' } Pipe the function item to an Execution Workflow that calls the WriteKey workflow. It would be nice if we could get someday a shiny built-in n8n node that does the job. :)

n8n Template: Store Chat Data in Supabase PostgreSQL for WhatsApp/Slack Integration This n8n template captures chat data (like user ID, name, or address) and saves it to a Supabase PostgreSQL database. It’s built for testing now but designed to work with WhatsApp, Slack, or similar platforms later, where chat inputs aren’t predefined. Guide with images can be found on: https://github.com/JimPresting/Supabase-n8n-Self-Hosted-Integration/ Step 1: Configure Firewall Rules in Your VPC Network To let your n8n instance talk to Supabase, add a firewall rule in your VPC network settings (e.g., Google Cloud, AWS, etc.). Go to VPC Network settings. Add a new firewall rule: Name: allow-postgres-outbound Direction: Egress (outbound traffic) Destination Filter: IPv4 ranges Destination IPv4 Ranges: 0.0.0.0/0 (allows all; restrict to Supabase IPs for security) Source Filter: Pick IPv4 ranges and add the n8n VM’s IP range, or Pick None if any VM can connect Protocols and Ports: Protocol: TCP Port: 5432 (default PostgreSQL port) Save the rule. Step 2: Get the Supabase Connection String Log into your Supabase Dashboard. Go to your project, click the Connect button in the header. Copy the PostgreSQL connection string: postgresql://postgres.fheraruzdahjd:[YOUR-PASSWORD]@aws-0-eu-central-1.pooler.supabase.com:6543/postgres Replace [YOUR-PASSWORD] with your Supabase account password (no brackets) and replace the string before that with your actual unique identifier. Note the port (6543 or 5432)—use what’s in the string. Step 3: Set Up the n8n Workflow This workflow takes chat data, maps it to variables, and stores it in Supabase. It’s built to handle messy chat inputs from platforms like WhatsApp or Slack in production. Workflow Steps Trigger Node: "When clicking 'Test workflow'" (manual trigger). For now, it’s manual. In production, this will be a WhatsApp or Slack message trigger, which won’t have a fixed input format. Set Node: "Set sample input variables (manual)". This node sets variables like id, name, address to mimic chat data. Why? Chat platforms send unstructured data (e.g., a message with a user’s name or address). We map it to variables so we can store it properly. The id will be something unique like a phone number, account ID, or account number. Sample Agent Node: Uses a model (e.g., GeminiFlash2.0 but doesn't matter). This is a placeholder to process data (e.g., clean or validate it) before saving. You can skip or customize it. Supabase PostgreSQL Node: "Supabase PostgreSQL Database". Connects to Supabase using the connection string from Step 2. Saves the variables (id, name, address) to a table. Why store extra fields? The id (like a phone number or account ID) is the key. Extra fields like name or address let us keep all user info in one place for later use (e.g., analytics or replies). Output Node: "Update additional values e.g., name, address". Confirms the data is saved. In production, this could send a reply to the chat platform. Why This Design? Handles Unstructured Chat Data**: WhatsApp or Slack messages don’t have a fixed format. The "Set" node lets us map any incoming data (e.g., id, name) to our database fields. Scales for Production**: Using id as a key (phone number, account ID, etc.) with extra fields like name makes this workflow flexible for many use cases, like user profiles or support logs. Future-Ready**: It’s built to swap the manual trigger for a real chat platform trigger without breaking. Step 4: Configure the Supabase PostgreSQL Node In the n8n workflow, set up the Supabase PostgreSQL node: Host: aws-0-eu-central-1.pooler.supabase.com (from the connection string) Port: 6543 (or what’s in the connection string) Database: postgres User: postgres.fhspudlibstmpgwqmumo (from the connection string) Password: Your Supabase password SSL: Enable (Supabase usually requires it) Set the node to Insert or Update: Map id to a unique column in your Supabase table (e.g., phone number, account ID). Map fields like name, address to their columns. Test the workflow to confirm data saves correctly. Security Tips Limit Firewall Rules**: Don’t use 0.0.0.0/0. Find Supabase’s IP ranges in their docs and use those. Hide Passwords**: Store your Supabase password in n8n’s environment variables. Use SSL**: Enable SSL in the n8n node for secure data transfer.

AI-Powered Workflow for Auto-Responding to Positive Cold Email Replies This workflow is designed for agencies, freelancers, and sales teams who want to turn positive cold email replies into booked meetings automatically—without hiring VAs or spending hours on manual responses. ❓ The Problem Most teams waste time replying manually or pay for virtual assistants, leading to delays and missed opportunities. This template eliminates that bottleneck. ✅ What the Workflow Does Detects positive replies from Instantly.ai campaigns Uses AI to analyze intent and craft natural, human-like responses Adds personalization to keep replies authentic Includes Calendly links, product docs, or FAQs based on the lead’s intent Sends responses instantly—so you never miss a hot lead again No robotic AI text. Just smooth, human-style emails that get booked calls faster. 👥 Who is This For? Agencies** running Instantly.ai or similar outbound tools Founders** handling their own cold email outreach Sales teams** looking to automate follow-up and booking Anyone who gets 5–20 positive replies a week and wants to 2x–4x conversions ✅ Requirements n8n** (Cloud or self-hosted) Instantly.ai account** with API access OpenAI API key** (stored securely in n8n credentials) (Optional) Calendly or booking link, Notion or Google Docs for resources ⚙️ How to Set Up Import the workflow into n8n Add your Instantly.ai API credentials and OpenAI key using n8n’s credential manager Customize the AI prompt for your tone, CTA, and offer Insert your Calendly or booking link in the response template Test with one positive reply to confirm filtering and response quality Activate the workflow to auto-reply in real time 🔧 How to Customize Adjust the filtering logic for different keywords or intent signals Add branching for multiple booking links (e.g., based on region or service type) Push responses to a CRM for tracking Include extra resources like case studies or pricing docs

This N8N template demonstrates how to use our tool to collect key information from any YouTube channel - including title, description, custom URL, stats (views, subscribers, videos), creation date, country, keywords, thumbnails, and channel ID. Everything is fetched and saved directly in a linked Google Sheet. Use cases are many: Whether you're part of an MCN or YouTube channel network, a digital marketing agency, an influencer analyst, or a growth-focused YouTube consultant, this tool helps you instantly access detailed channel data for scouting, benchmarking, and strategic planning. It's perfect for competitive research, brand vetting, or building your next performance dashboard. How It Works The workflow starts when you manually click Test Workflow or Execute Workflow in N8N. It reads through the list of full channel URLs or custom channel URLs from the Channel URLs tab in a connected Google Sheet. Only the URLs marked with the Ready status will be processed. The tool loops through each row and prepares the necessary data for the YouTube API call later. A Switch node detects the URL type of each input (whether it's a full or custom channel URL) and routes it accordingly. Based on the input type, the appropriate YouTube API endpoint is triggered to fetch channel metrics. It checks whether the API call is successful before continuing: If successful, the fetched data is written back to the connected Google Sheet in the same row and the row's status is updated to Finished. If it fails, the row's status is updated to Error. How To Use Download the workflow package. Import the workflow package into your N8N interface. Duplicate the YouTube - Get Channel Information Google Sheet template into your Google Sheets account. Set up Google Cloud Console credentials in the following nodes in N8N, ensuring enabled access and suitable rights to Google Sheets and YouTube services: For Google Sheets access, ensure each node is properly connected to the correct tab in your connected Google Sheet template: Node Google Sheets - Get Channel URLs → connected to Tab Channel URLs; Node Google Sheets - Update Data → connected to Tab Channel URLs; Node Google Sheets - Update Data - Error → connected to Tab Channel URLs. For YouTube access, set up a GET method to connect to YouTube API in the following nodes: Node HTTP Request - Get Comments For Video URLs 1; Node HTTP Request - Get Comments For Video URLs 2. In your connected Google Sheet, enter the full or custom channel URLs that you want to crawl and set the rows' status to Ready. Run the workflow by clicking Execute Workflow or Test Workflow in N8N. View the results in your Google Sheet: Successful fetches will update channel data in the same row in Channel URLs tab and the row's status is updated to Finished; otherwise, the row's status will be changed to Error. Requirements Basic setup in Google Cloud Console (OAuth or API Key method enabled) with enabled access to YouTube and Google Sheets. How To Customize By default, the workflow is manually triggered in N8N. However, you can automate the process by adding a Google Sheets trigger that monitors new entries in your YouTube – Get Channel Information template and starts the workflow automatically. Need Help? Join our community on different platforms for support, inspiration and tips from others. Website: https://www.agentcircle.ai/ Etsy: https://www.etsy.com/shop/AgentCircle Gumroad: http://agentcircle.gumroad.com/ Discord Global: https://discord.gg/d8SkCzKwnP FB Page Global: https://www.facebook.com/agentcircle/ FB Group Global: https://www.facebook.com/groups/aiagentcircle/ X: https://x.com/agent_circle YouTube: https://www.youtube.com/@agentcircle LinkedIn: https://www.linkedin.com/company/agentcircle

This workflow automates the routine check for upgradable packages on your Ubuntu server, ensuring you stay updated with the latest software patches and security improvements. By running a daily script, it efficiently monitors any available package upgrades and promptly notifies you via email, saving you time and enhancing your server’s security. How It Works: Daily Monitoring**: The workflow is configured to execute a script daily that connects to your Ubuntu server and checks for any upgradable packages. Email Notification**: If any upgradable packages are detected during the check, the workflow triggers an alert mechanism that automatically sends you a notification email detailing the available updates. Set Up Steps: SSH Credentials**: Provide the SSH login credentials for your Ubuntu server. This will allow the workflow to securely connect and perform checks for software updates. SMTP Credentials**: Provide SMTP login details for your email account. These credentials are used to configure the email notifications system, enabling it to send alerts about the upgradable packages. Benefits: Timeliness**: Receive prompt updates on critical software upgrades to maintain the optimal performance and security of your server. Automation**: Reduces the need for manual checks, allowing you to focus on other critical tasks with peace of mind. Customizable**: Easily adjust the checking frequency or update the notification settings according to your preferences.

Travel Agent that Auto Response on Mail In this guide, we’ll break down how to set up an AI-powered auto-reply system that works while you sleep. Ready to 10X your efficiency? Let’s dive in! What’s the Goal? AI-driven auto-responses for Email. Instant replies to FAQs, order confirmations, and support queries. 24/7 availability - no more “We’ll get back to you soon” delays. Seamless integration with existing business tools. By the end, you’ll have a self-running communication assistant that never takes a coffee break. Why Does It Matter? Why automate replies? Because time = money and manual typing is so 2010. Here’s why this workflow is a game changer: Zero Human Error: AI doesn’t get tired or make typos. Lightning-Fast Replies: Customers get instant answers, improving satisfaction. 24/7 Availability: No more “Out of Office” replies. Focus on High-Value Work: Free your team from mundane tasks. Think of it as hiring a super efficient virtual assistant - minus the salary. How It Works Here’s the step by step magic behind the automation Step 1: Trigger the Workflow Detect new messages from WhatsApp, Email, or Slack. Use n8n’s webhook or API integration to capture incoming queries. Step 2: Process the Message with AI Send the message to an AI model (like OpenAI GPT-4 or Gemini). Generate a context-aware, human-like response. Step 3: Send the Automated Reply Route the AI-generated response back to the original platform. Ensure personalization (e.g., “Hi [Name], thanks for reaching out!”). Step 4: Log & Optimize Store interactions in a database (Airtable, Google Sheets). Continuously improve AI responses based on past data. How to use the workflow? Importing a workflow in n8n is a straightforward process that allows you to use pre-built or shared workflows to save time. Below is a step-by-step guide to importing a workflow in n8n, based on the official documentation and community resources. Steps to Import a Workflow in n8n 1. Obtain the Workflow JSON Source the Workflow:** Workflows are typically shared as JSON files or code snippets. You might receive them from: The n8n community (e.g., n8n.io workflows page). A colleague or tutorial (e.g., a .json file or copied JSON code). Exported from another n8n instance (see export instructions below if needed). Format:** Ensure you have the workflow in JSON format, either as a file (e.g., workflow.json) or as text copied to your clipboard. 2. Access the n8n Workflow Editor Log in to n8n:** Open your n8n instance (via n8n Cloud or your self-hosted instance). Navigate to the Workflows tab in the n8n dashboard. Open a New Workflow:** Click Add Workflow to create a blank workflow, or open an existing workflow if you want to merge the imported workflow. 3. Import the Workflow Option 1: Import via JSON Code (Clipboard): In the n8n editor, click the three dots (⋯) in the top-right corner to open the menu. Select Import from Clipboard. Paste the JSON code of the workflow into the provided text box. Click Import to load the workflow into the editor. Option 2: Import via JSON File: In the n8n editor, click the three dots (⋯) in the top-right corner. Select Import from File. Choose the .json file from your computer. Click Open to import the workflow.

This workflow is designed for dynamic and intelligent conversational capabilities. It incorporates OpenAI's GPT-4o model for natural language understanding and generation. Additional tools include SerpAPI and Wikipedia for enriched, data-driven responses. The workflow is triggered manually, and utilizes a 'Window Buffer Memory' to maintain the context of the last 20 interactions for better conversational continuity. All these components are orchestrated through n8n nodes, ensuring seamless interconnectivity. To use this template, you need to be on n8n version 1.50.0 or later.

What this workflow does? This workflow primarily uses the GPT-4o API from PiAPI and automatically creates front/side/top views of 3D models from commands. Who is this for？ 3D Designers： Quickly generate standardized orthographic views for design review E-commerce Operators： Create multi-angle product display images 3D Modeling Beginners： Instantly produce basic reference views Step-by-step Instruction Fill in X-API-Key of your PiAPI account and the image prompt based on your inspiration. Click Test workflow. Get the image url in the final node. OutPut

This workflow allows users to generate beautifully stylized 3D-rendered food emoji icons based on a simple text prompt. It combines user input, structured visual design generation, and image rendering using OpenAI’s GPT models. ✨ What It Does Collects user input via a form: e.g. "green apple" Generates a structured JSON specification describing the emoji’s form, lighting, texture, and color scheme Uses AI to render an image based on that spec—styled like a high-quality emoji icon with a transparent background 🧠 Use Case This template is ideal for: Designers or creators needing icon ideas or drafts for food items Developers building emoji packs or digital stickers Inspiration for AI-assisted product illustration or branding 💡 Why It's Useful Instead of prompting a model directly with vague terms, this flow creates a structured visual spec tailored to food items. The final emoji-style icon is polished, modern, and downloadable. ✅ Requirements To get started with this workflow, follow these steps: 🔑 Configure Credentials: Set up your API credentials for OpenAI and Google Drive 💳 Add OpoenAI Credit: Make sure to add credit to your OpenAI account, verify your organization (required for generating images) 📊 Connect Google Drive: Authenticate your Google Drive account ⚙️ (Optional) Customize Prompts: Adjust the prompts within the workflow to better suit your specific needs Note: Each image generation will cost you about $0.17

📌 Validate Seatable Webhooks with HMAC SHA256 Authentication This mini workflow is designed to securely validate incoming Seatable webhooks using HMAC SHA256 signature verification. 🔐 What it does: Listens for incoming Seatable webhook requests. Calculates a SHA256 HMAC hash of the raw request body using your shared secret. Compares the computed hash with the x-seatable-signature header (after removing the sha256= prefix). If the hashes match: responds with 200 OK and forwards the request to subsequent nodes. If the hashes don’t match: responds with 403 Forbidden. ⚠️ Important Notes: This workflow is provided as a template and is not intended to work standalone. Please duplicate it and integrate it with your custom logic at the "Add nodes for processing" node. Configuration steps: Set your secret key in the “Calculate sha256” crypto node (replace the placeholder). Adjust the webhook path to suit your environment (or set it to "manual" for testing). Connect your actual logic after the verification step.