Workflow Templates

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

No-Code: Convert Multiple Binary Files to Base64 Introduction This template provides a robust, purely no-code solution for a common integration challenge: converting multiple binary files contained within a single n8n item (e.g., after unzipping an archive) into a structured JSON array of Base64 encoded strings. Purpose Many external APIs, especially those handling batch file uploads or complex data structures, require files to be submitted as a single JSON payload. This payload typically needs an array containing two elements for each file: the reconstructed file path/name and the Base64 encoded content. This template automatically handles the file isolation, encoding, path reconstruction, and final JSON aggregation, replacing the need for complex custom JavaScript Code nodes. Configuration Steps Input: Connect your binary data source (e.g., an HTTP Request followed by a Compression node) to the first node in this template. Split Out: This node automatically separates the multiple binary files into individual items. Extract From File: This node uses the dynamic expression {{ $binary.keys()[0] }} to ensure the correct binary file is targeted and converted to Base64. Set: This node uses a conditional expression to reconstruct the full path (including the directory, if present) for each file. Aggregate: The final node merges all individual items into a single, clean JSON item containing a top-level files array, ready for your final API call. For a detailed walkthrough, including the explanation behind the dynamic expressions and why this is superior to the custom code solution, check out the full blog post: The No-Code Evolution: Base64 Encoding Multiple Files in n8n (Part 2).

Outlook to OneDrive This workflow automates the process of saving binary attachments from Outlook emails into newly created folders in OneDrive. It's ideal for users who regularly receive files and need them organized into separate folders without manual intervention. Each folder is automatically named based on the email subject and the current timestamp, allowing all attachments from that email to be stored inside the corresponding folder. This is particularly useful for streamlining document workflows, improving file traceability, and reducing the time spent on repetitive tasks like organizing client submissions, invoices, or internal reports. The configuration and setup of the workflow can be customized to meet the business or personal needs of the user. Its purpose is to automatically process binary attachments from Outlook emails and upload them to dynamically created folders in OneDrive. Overview Microsoft Outlook Trigger – Monitors your inbox for new emails. Filter – Ensures only emails with binary attachments proceed. Get Outlook Message – Retrieves the full email and downloads attachments. Create Folder – Makes a new folder in OneDrive based on the email subject and time. Split Out – Extracts each binary attachment. Merge– Combines folder and file data before upload. Upload File OneDrive – Uploads each binary file into the new folder. Need Help? Have Questions? For consulting and support, or if you have questions, please feel free to connect with me on LinkedIn or via email.

Who it’s for? Anyone who wants a simple, secure way to call a Google Cloud Run endpoint from n8n—without exposing it publicly. People who want a cheap/free-tier way to run custom API logic without hosting n8n or spinning up servers. Example: you’ve got scraping code that needs specific system/python libs—build it into a Dockerfile on Cloud Run, then call it as a secure endpoint from n8n. How it works This is a conjunctive workflow: the main workflow calls Service Auth (sub-workflow) to get a Google ID token, merges that auth with your context, then calls your Cloud Run URL with Authorization: Bearer <id_token>. Works great for single calls or looping over items. How to set up General instructions below—see my detailed guide for more info: Build a Secure Google Cloud Run API, Then Call It from n8n (Free Tier) Setup: Create a Cloud Run service and enable Require authentication (Cloud IAM). Create a Google Service Account and grant Cloud Run Invoker on that service. In n8n, import the workflows and update the Vars node (service_url, optional service_path). Create a JWT (PEM) credential from your service account key, then run. Make sure to read the sticky notes in the workflows—they contain helpful pointers and optional configurations. Requirements Cloud Run service URL (auth required) Google Service Account with Cloud Run Invoker Private key JSON fields downloaded from Service Account | needed to generate JWT credentials How to customize Change the HTTP method/path/body in Cloud Run Request, or drop the Service Auth (sub-workflow) into other workflows to reuse the same auth pattern. More details Full write-up (minimal + modular flows), screenshots, and more: Build a Secure Google Cloud Run API, Then Call It from n8n (Free Tier) — by Marco Cassar

Cheap Nano Banana API - AI Image Generator with BananaAPI.com Overview This workflow integrates BananaAPI.com with the Nano Banana image engine to generate or edit AI images from text prompts and optional reference images. Users simply fill out a form with their prompt and preferences, the workflow submits the request to BananaAPI, polls the status until it is complete, and then returns the final image link. Why use it? Super affordable: only $0.025 per image Pay-as-you-go** pricing — no monthly subscription Credits never expire** — use anytime, no pressure Perfect for creators, marketers, and developers looking for a cost-effective AI image generator inside n8n. Prerequisites A BananaAPI.com account + API key (Bearer token). Sign up at BananaAPI.com. An n8n instance (Cloud or self-hosted). Basic knowledge of crafting AI prompts for better quality results. ⚠️ Important: Never expose your API key in public workflows. Use n8n Credentials for production setups. Setup Instructions 1. Obtain API Key Create an account at BananaAPI.com, generate your API key, and keep it safe. 2. Configure the Form The Form Trigger collects the following fields: api_token (required) — Banana API key prompt (required) — image description (e.g., “a neon cyberpunk cat, detailed, 4k”) Output Format [optional] — choose PNG or JPEG Image Size [optional] — 16:9, 9:16, 1:1, 3:4, 4:3 image_url_1 ... image_url_5 [optional] — reference images for editing/transform 3. Workflow Execution User fills the form and submits. Workflow sends a POST request to https://bananaapi.com/api/n8n/generate/. BananaAPI forwards the job to Nano Banana. Workflow waits 5s, then polls status via image-status/{taskId}. If status != completed, loop until ready. Once completed, workflow returns the final image URL. 4. Outputs The workflow returns: image_url — the generated image link task_id — task reference ID status — job status (completed/pending) 💡 Tip: Add a Webhook Response node to return clean JSON for frontend apps. Customization Tips Enhance prompts** with details like style (photorealistic, cartoon, cyberpunk), lighting, or action for better results. Use image_url_1 with a strong prompt to create image editing flows. Adjust wait time (5s → 8–10s) to optimize polling frequency. Add validation to ensure required fields are always filled in. API Reference POST** https://bananaapi.com/api/n8n/generate/ GET** https://bananaapi.com/api/n8n/image-status/{taskId} Docs: BananaAPI Docs ✅ Always include Authorization: Bearer <token> in headers. Pricing Advantages $0.025 per image** — cheaper than most alternatives Pay-as-you-go** — no monthly subscription required Credits never expire** — full flexibility to use anytime This makes BananaAPI + Nano Banana one of the most budget-friendly AI image solutions for automation workflows. Troubleshooting 401/403 Unauthorized** → Check Authorization header (Bearer token). Invalid JSON** → Ensure POST body is valid JSON (double quotes, no trailing commas). No imageUrl returned** → Task still pending; wait longer or verify taskId. Slow performance** → Increase wait interval (8–10s). Security Best Practices Do not hardcode API tokens in public workflows. Use n8n Credentials for storing tokens securely. Hide sensitive fields in forms or use Webhooks for controlled access.

This workflow automates the backup of decrypted n8n credentials from a self-hosted Docker instance to Google Drive. It allows you to export credentials on n8n versions 2.x.x (where old CLI commands may not work) without accessing the server terminal manually. How it works Configuration**: Defines the Docker container name and file paths using a centralized variables node. SSH Execution**: Connects to the host machine via SSH and executes the n8n export:credentials command inside the specified Docker container. File Retrieval**: Reads the newly created decrypted JSON file from the host filesystem. Cloud Upload**: Uploads the JSON file to a specified folder in Google Drive with a timestamped filename. Set up steps Configure Variables**: Open the "Variables" node and enter your Docker Container name (usually n8n or an ID). SSH Connection**: Configure the "Execute a command" (SSH) node with your host machine's IP, username, and SSH key/password. Google Drive Auth**: Authenticate the "Google Drive Upload File" node with your Google credentials. Select Folder**: In the "Google Drive Upload File" node, select the specific folder on your Drive where you want the backups to be saved. Schedule**: (Optional) Adjust the "Schedule Trigger" to your preferred backup frequency (default is set to run periodically).

Who's it for This template is perfect for community managers, business owners, and WhatsApp group administrators who want to create a welcoming experience for new members. Whether you're running a support group, managing a business community, or moderating a hobby group, this automation ensures every new member feels valued from the moment they join. How it works The workflow automatically detects when someone joins your WhatsApp group and sends them a personalized welcome message directly to their private chat. It uses Evolution API to interface with WhatsApp Business and includes a natural delay to make the interaction feel more human. The entire process is hands-off once configured, ensuring consistent engagement with new members 24/7. What it does Monitors group activity - Receives real-time notifications when members join or leave Filters for your specific group - Ensures messages are only sent for your designated group Validates new joins - Confirms the event is a member joining (not leaving) Adds natural timing - Waits a customizable period before sending the message Sends private welcome - Delivers your welcome message directly to the new member's chat Requirements Evolution API instance** (self-hosted or cloud service) WhatsApp Business account** connected to Evolution API Group admin permissions** for the WhatsApp group n8n instance** (self-hosted or cloud) How to set up Import the workflow into your n8n instance Configure the Set Variables node with: Your WhatsApp group ID (format: xxxxxxxxxxxxx@g.us) Evolution API key Instance name from Evolution API Evolution API URL Custom welcome message Delay time in minutes Copy the webhook URL from the Webhook node Configure Evolution API to send group notifications to your webhook URL Test the workflow by having someone join your group Activate the workflow for continuous operation For a detailed video tutorial on setting up this workflow, check out: https://youtu.be/WO2MJoQqLvo How to customize the workflow Welcome message**: Edit the message in the Set Variables node to match your group's tone Timing**: Adjust the wait time to send messages immediately or after several minutes Multiple groups**: Duplicate the workflow and change the group ID for each group Rich media**: Extend the HTTP Request node to send images or documents with the welcome Conditional messages**: Add IF nodes to send different messages based on time of day or member count Follow-up sequence**: Chain additional HTTP Request nodes to create a welcome series

Premium n8n Workflow: DataForSEO + Airtable Keyword Research This premium n8n workflow harnesses the power of DataForSEO's API combined with Airtable's relational database capabilities to transform your keyword research process, providing deeper insights for content creation without the hefty price tag of traditional SEO tools. 🚀 Features 🔍 Comprehensive Data Extracts related keywords, search volume 📈, keyword difficulty 📊, search intent 🤔, and more directly from DataForSEO's powerful API 🚀. 💰 Cost-Effective Leverages DataForSEO's pay-as-you-go model 💸, making it budget-friendly. 🏗️ Airtable Integration Organizes your data in a powerful relational database for advanced filtering, sorting, and visualization capabilities. 🔄 Cross-Reference Capabilities Create relationships between keyword sets to identify content opportunities traditional tools miss. 🤖 Fully Automated Set up once and run keyword research with a single click. ⚙️ Efficient & Scalable Handles large keyword lists with Airtable's robust data management system. 👥 This Workflow is Perfect For: Content creators 📝 Bloggers 💻 YouTubers 🎥 Small business owners 💼 Digital marketers 📊 SEO professionals 🔍 Entrepreneurs 🚀 E-Commerce website owners 💻 Stop overspending on expensive SEO tools and start generating actionable keyword insights with a professional-grade database. 📝 What's Included? ⚙️ n8n Workflow Template Ready-to-use workflow with pre-configured DataForSEO API endpoints for comprehensive keyword data collection. 📊 Airtable Database Structure Pre-built tables and fields specifically designed for SEO keyword analysis. 🔌 DataForSEO Integration Complete setup for pulling multiple data types (related keywords, suggestions, people also ask, subtopics) from DataForSEO's API. 🔄 Automated Data Processing Logic to clean, format, and structure raw API data into usable insights. 📋 Documentation Step-by-step instructions for connecting your DataForSEO account and configuring the workflow. 🏆 Why Choose the Airtable Version? 📱 Access Anywhere: Review your keyword research on any device through Airtable's apps. 🤝 Team Collaboration: Share your keyword database for collaborative planning. 🔄 Data Relationships: Connect keywords, content ideas, and publishing schedules in one place. 🔌 Extensibility: Integrate with other tools via Airtable's ecosystem. 🎯 Content Planning: Use Airtable as a complete content management system, from research to publication tracking. 🛠️ How It Works 1️⃣ Import the provided n8n workflow into your n8n instance 📥. 2️⃣ Configure your DataForSEO API credentials and Airtable connections ⚙️. 3️⃣ Input your target keywords and desired parameters 📝. 4️⃣ Trigger the workflow — n8n automatically gathers and organizes your keyword research in Airtable 🤖. 5️⃣ Use Airtable’s interface to analyze relationships, identify opportunities, and plan your strategy 📊. Additional detailed instructions are provided in the workflow. 🏁 What You Need to Get Started 🔹 Access to n8n (self-hosted or cloud) ☁️ 🔹 A DataForSEO account with API credentials 🔑 🔹 An Airtable account (free tier works, Pro recommended for advanced features) 📊 🔹 Basic understanding of API usage and n8n workflows 🧠 💡 You can also connect this workflow with my SEO-Based Keyword Categorization & Clustering Strategy Workflow with Airtable and my Multi-Agent SEO Optimized Blog Writing System with Hyperlinks for E-Commerce, both available on my profile, to build a fully automated, end-to-end SEO content machine.

LINE x Google Account Linking Workflow This workflow automates the process of linking a new user on your LINE Official Account to their Google Account. When a user adds your LINE account as a friend, this workflow automatically sends them a message with a unique authentication link. After the user approves the connection, their Google profile information is fetched, and a confirmation message is sent, completing the loop. Prerequisites Before you begin, ensure you have the following: An n8n instance:** Either on n8n.cloud or a self-hosted environment. A LINE Developers Account:** A Messaging API channel. Your Channel Access Token (long-lived). A Google Cloud Platform (GCP) Account:** A configured OAuth consent screen. An OAuth 2.0 Client ID and Client Secret. Setup Instructions Follow these steps to configure the workflow. Step 1: Configure LINE Developers Console Log in to the LINE Developers Console. Navigate to your provider and select your Messaging API channel. Go to the Messaging API tab. Issue a Channel access token (long-lived) and copy the value. In the Webhook URL field, paste the Test URL from the LINE Webhook node in your n8n workflow. Enable Use webhook. Step 2: Configure Google Cloud Platform (GCP) Log in to the Google Cloud Console and select your project. Navigate to APIs & Services > OAuth consent screen. Configure it if you haven't already, ensuring you add your own Google account as a test user. Go to APIs & Services > Credentials. Click + CREATE CREDENTIALS and select OAuth 2.0 Client ID. For Application type, choose Web application. Under Authorized redirect URIs, click + ADD URI and paste the Test URL from the Google Auth Callback node in your n8n workflow. Click Create. Copy your Client ID and Client Secret. Step 3: Configure the n8n Workflow Import the workflow JSON into your n8n canvas and follow these steps to set it up. 1. Configure n8n Credentials First, set up the credentials that the HTTP Request nodes will use. For the LINE Messaging API:** In n8n, go to Credentials > Add credential. Search for and select Header Auth. Set Name to Authorization. Set Value to Bearer YOUR_LINE_CHANNEL_ACCESS_TOKEN (replace with the token from Step 1). Save the credential with a memorable name like "LINE Messaging API Auth". For the Google API (Dynamic Token):** Create another Header Auth credential. Set Name to Authorization. For Value, enter a placeholder like Bearer dummy_token. This will be replaced dynamically by the workflow. Save the credential with a name like "Google API Dynamic Token". 2. Update Node Parameters Now, update the parameters in the following nodes: Create Google Auth URL node:** In the value field, replace YOUR_N8N_WEBHOOK_URL_FOR_GOOGLE with the webhook URL of the Google Auth Callback node. Replace YOUR_GOOGLE_CLIENT_ID with the Client ID from GCP (Step 2). Get Google Access Token node:** In the jsonBody field, replace YOUR_GOOGLE_CLIENT_ID, YOUR_GOOGLE_CLIENT_SECRET, and YOUR_N8N_WEBHOOK_URL_FOR_GOOGLE with your actual GCP credentials and callback URL. Get Google User Info node:** For Authentication, select Header Auth. For Credential for Header Auth, choose the "Google API Dynamic Token" credential you created. Important: Click Add Option > Header To Append. Set the Name to Authorization and the Value to the following expression to use the token from the previous step: Bearer {{ $node["Get Google Access Token"].json["access_token"] }}. Send Auth Link to LINE & Send Completion Message to LINE nodes:** For Credential for Header Auth, choose the "LINE Messaging API Auth" credential. Redirect to LINE OA node:** In the redirectURL parameter, replace YOUR_LINE_OFFICIAL_ACCOUNT_ID with your LINE OA's ID (e.g., @123abcde). Step 4: Activate and Test Save the workflow by clicking the Save button. Activate the workflow using the toggle in the top-right corner. On your phone, add your LINE Official Account as a friend. You should receive a message with a link. Follow the link to authorize with your Google account. After successful authorization, you should receive a completion message in LINE and be redirected. > Note: When you are ready for production, remember to replace the "Test" webhook URLs in the LINE and GCP consoles with the "Production" URLs from the n8n webhook nodes.

Compare AI Models with Nvidia API: Qwen, DeepSeek, Seed-OSS & Nemotron Overview Queries four AI models simultaneously via Nvidia's API in 2-3 seconds—4x faster than sequential processing. Perfect for ensemble intelligence, model comparison, or redundancy. How It Works Webhook Trigger receives queries AI Router distributes to four parallel branches: Qwen2, SyncGenInstruct, DeepSeek-v3.1, and Nvidia Nemotron Merge Node aggregates responses (continues with partial results on timeout) Format Response structures output Webhook Response returns JSON with all model outputs Prerequisites Nvidia API key from build.nvidia.com (free tier available) n8n v1.0.0+ with HTTP access Model access in Nvidia dashboard Setup Import workflow JSON Configure HTTP nodes: Authentication → Header Auth → Authorization: Bearer YOUR_API_KEY Activate workflow and test Customization Adjust temperature/max_tokens in HTTP nodes, add/remove models by duplicating nodes, change primary response selection in Format node, or add Redis caching for frequent queries. Use Cases Multi-model chatbots, A/B testing, code review, research assistance, and production systems with AI fallback.