Workflow Templates

Who For? Gamers who don't like bad and slow preformance playing games and want to find a good preformance based server near them. Setup? None! Modes Available Auto - Optimized (Recommended & Default) Ping - Finds the lowest ping Latency - Lowest ping & highest FPS

Overview This workflow extracts text from Instagram images by combining HikerAPI and OCR.Space. You can use it to collect text data from single posts or carousels, analyze visual content, or repurpose insights without manual copying. The process is fully automated inside N8N and helps marketers, researchers, and teams gather Instagram text quickly. How it works Takes an Instagram post URL, either a single post or a carousel Retrieves media data using the HikerAPI Get Media endpoint Detects the post type, whether single feed, carousel, or reel For single posts, sends the image to OCR.Space for text extraction For carousels, loops through each slide and extracts text from every image Merges all parsed results into one raw text output Use cases Collecting text data from Instagram images for research Extracting visual insights for marketing analysis Repurposing creator content without manual transcription Helping marketers, agencies, and researchers identify message patterns in visual posts Prerequisites HikerAPI account with access to the Instagram media endpoint OCR.Space API key for image text extraction A valid Instagram post URL N8N instance capable of running HTTP requests and looping through items Set up steps Prepare your API keys for HikerAPI and OCR.Space Insert both API keys into their respective HTTP Request nodes Paste the Instagram post URL into the IGPost URL node Run the workflow to generate raw text extracted from Instagram images Check the sticky notes inside the workflow for additional guidance Made by @fataelislami https://pake.ai

This n8n template demonstrates how to generate subtitle overlays for YouTube videos and save the final files to Google Drive. It is useful when you want accessible video outputs without manually editing captions in a video editor. Who’s it for Content creators publishing educational or social content Teams improving accessibility and watch-time performance Agencies preparing client-ready subtitled assets Good to know Subtitle quality depends on audio clarity and speaker overlap. Make sure your VideoDB account has enough balance before running this workflow. Track usage rates at console.videodb.io/dashboard/usage. How it works A form trigger receives a YouTube URL. n8n uploads the source video to VideoDB. VideoDB indexes speech and creates timestamped transcript data. A subtitle node renders subtitle overlays into the video output. n8n downloads and stores the subtitled file in Google Drive. How to use Add VideoDB and Google Drive credentials. Set your destination Drive folder in the upload node. Run one sample video to verify subtitle timing and style. Activate the workflow for regular use. Requirements VideoDB API key (Get one here) Google Drive account with API access n8n instance (cloud or self-hosted) Customising this workflow Change subtitle language and rendering settings in the subtitle node. Duplicate branches for multilingual subtitle variants. Add a review step before final storage. Replace Google Drive with S3 or another media destination. Disclaimer: This workflow uses VideoDB’s Verified Community Node and will only work on self-hosted n8n instances.

How it works This workflow provides a complete, automated backup solution for your n8n instance, running on a daily schedule to ensure your automations are always safe. Automatic cleanup:** It first connects to your Google Drive to find and delete old backup folders, keeping your storage clean and organized based on a retention number you set. Daily folder creation:** It then creates a new, neatly dated folder to store the current day's backup. Fetches & saves workflows:** Finally, it uses the n8n API to get a list of all your workflows, converts each one to a .json file, and uploads them to the newly created folder in Google Drive. Set up steps Setup time: ~3 minutes This template is designed to be as plug-and-play as possible. All configurations are grouped in a single node for quick setup. Connect your accounts:** Authenticate the Google Drive and n8n API nodes with your credentials. Configure main settings:* Open the Set node named *"CONFIG - Set your variables here"** and: Paste the ID of your main Google Drive folder where backups will be stored. Adjust the number of recent backups you want to keep. Activate workflow:** Turn on the workflow. Your automated backup system is now active. For more detailed instructions, including how to find your Google Drive folder ID, please refer to the sticky notes inside the workflow.

How it works Stripe fires a checkout.session.completed webhook when a payment succeeds Customer name, phone, email, and payment amount are extracted If the customer has a phone number, a WhatsApp receipt is sent via MoltFlow Payments without phone numbers are logged and skipped Set up steps (~5 min) Create a MoltFlow account at molt.waiflow.app and connect your WhatsApp Generate an API key in MoltFlow (Sessions page > API Keys tab) Activate this workflow and copy the webhook URL In Stripe Dashboard > Developers > Webhooks, add the n8n URL for checkout.session.completed Set YOUR_SESSION_ID in the Format Receipt code node Add your MoltFlow API Key as Header Auth credential (header name: X-API-Key) Prerequisites MoltFlow account with active WhatsApp session Stripe account with webhook access Customer phone numbers collected during checkout (Stripe customer_details.phone)

How it works Slack sends an outgoing webhook when a message is posted in a channel The message text, sender, and channel name are extracted A formatted message is forwarded to your WhatsApp number via MoltFlow Empty messages and Slack URL verification challenges are handled automatically Set up steps (~5 min) Create a MoltFlow account at molt.waiflow.app and connect your WhatsApp Activate this workflow and copy the webhook URL In Slack, configure an outgoing webhook or Event Subscription pointing to the n8n URL Set YOUR_SESSION_ID and YOUR_PHONE in the Format Message code node Add your MoltFlow API Key as Header Auth credential (header name: X-API-Key) Prerequisites MoltFlow account with active WhatsApp session Slack workspace with webhook or Events API access Tip: filter by channel or keywords in the code node to limit forwarding

What this template does Sends instant WhatsApp order confirmation messages to customers when they place an order on your Shopify store, powered by MoltFlow (https://molt.waiflow.app). How it works Shopify webhook fires on new order creation Parse order data — extracts customer name, phone, order number, items, and total Check phone — skips orders without a phone number Send WhatsApp confirmation — delivers a personalized message via MoltFlow API Log result — records success or skip for tracking Set up steps Create a MoltFlow account (https://molt.waiflow.app) and connect your WhatsApp number Generate an API key in MoltFlow (Sessions page, API Keys tab) Activate this workflow in n8n and copy the webhook URL In Shopify Admin, go to Settings, Notifications, Webhooks and add the n8n URL for Order creation Set YOUR_SESSION_ID in the Format Order Message code node Add your MoltFlow API key as an HTTP Header Auth credential (Header Name: X-API-Key) Prerequisites MoltFlow account with an active WhatsApp session Shopify store with webhook access Customer phone numbers must include country code

Overview This workflow provides a reliable and secure system for uploading and managing documents. It accepts files via form or webhook, validates file size and type, generates unique metadata, detects duplicates using file hashing, and stores records in Postgres. It ensures clean, consistent, and duplicate-free document intake. How It Works Document Upload Users upload files through a form or webhook endpoint. Configuration Defines: Maximum file size Allowed file types Storage settings File Validation The workflow checks: File size against limits MIME type against allowed formats Invalid files are rejected with a clear error response. Metadata Generation Generates: Unique document ID (UUID) File hash (SHA-256) File name, size, and type Upload timestamp and source Duplicate Detection Uses the file hash to check if the document already exists in the database. Conditional Processing Duplicate found → returns existing document reference New document → proceeds to storage Database Storage Stores document metadata in Postgres with a received status. Response Handling Success → returns document ID Duplicate → returns existing document ID Error → returns validation details Setup Instructions Configure form trigger or webhook endpoint Set max file size and allowed MIME types in config node Connect Postgres credentials Create a documents table with required fields Update configuration values as needed Test with sample document uploads Activate the workflow Use Cases Secure document upload systems Preventing duplicate file storage Building document intake APIs Managing tax or financial documents Creating audit-ready upload pipelines Requirements n8n instance with form/webhook support Postgres database File upload handling enabled Notes SHA-256 hashing ensures accurate duplicate detection. You can extend storage to cloud services like S3 or Google Cloud Storage. Add authentication to webhook endpoints for production use. Customize validation rules based on your business requirements.

Automatically create branded social media graphics, certificates, thumbnails, or marketing visuals using Bannerbear's template-based image generation API. Bannerbear's API is primarily asynchronous by default: this workflow shows you how to use both asynchronous (webhook-based) and synchronous modes depending on your needs. What it does This workflow connects to Bannerbear's API to generate custom images based on your pre-designed templates. You can modify text, colors, and other elements programmatically. By default, Bannerbear works asynchronously: you submit a request, receive an immediate 202 Accepted response, and get the final image via webhook or polling. This workflow demonstrates both the standard asynchronous approach and an alternative synchronous method where you wait for the image to be generated before proceeding. How it works Set parameters - Configure your Bannerbear API key, template ID, and content (title, subtitle) Choose mode - Select synchronous (wait for immediate response) or asynchronous (standard webhook delivery) Generate image - The workflow calls Bannerbear's API with your modifications Receive result - Get the image URL, dimensions, and metadata in PNG or JPG format Async mode (recommended): The workflow receives a pending status immediately, then a webhook delivers the completed image when ready. Sync mode: The workflow waits for the image generation to complete before proceeding. Setup requirements A Bannerbear account (free tier available) A Bannerbear template created in your dashboard Your API key and template ID from Bannerbear For async mode: ability to receive webhooks (production n8n instance) How to set up Get Bannerbear credentials: Sign up at bannerbear.com Create a project and design a template Copy your API key from Settings > API Key Copy your template ID from the API Console Configure the workflow: Open the "SetParameters" node Replace the API key and template ID with yours Customize the title and subtitle text Set call_mode to "sync" or "async" For async mode (recommended): Activate the "Webhook_OnImageCreated" node Copy the production webhook URL Add it to Bannerbear via Settings > Webhooks > Create a Webhook Set event type to "image_created" Customize the workflow Modify the template parameters to match your Bannerbear template fields Add additional modification objects for more dynamic elements (colors, backgrounds, images) Connect to databases, CRMs, or other tools to pull content automatically Chain multiple image generations for batch processing Store generated images in Google Drive, S3, or your preferred storage Use async mode for high-volume generation without blocking your workflow

🎬 Extract YouTube auto-generated transcripts and save them for AI processing Direct YouTube API - Auto-Generated Only Extracts the auto-generated transcript from any YouTube video automatically. 🔄 How It Works (5 Steps) 📥 Input: youtubeVideoUrl only 🌐 Fetch: GET YouTube page HTML to extract INNERTUBE_API_KEY 🔑 Extract: Parse API key and video ID 🎥 Metadata: GET caption metadata 🤖 Auto-Detect: Find auto-generated transcript (kind: asr) 📝 Fetch & Parse: Download and clean transcript 🔄 Setup steps Import the workflow to your n8n instance Activate the workflow Provide the YouTube video URL via webhook or manual trigger The workflow will automatically extract the auto-generated transcript Access the results in the specified output format 🎯 Use Cases Extract auto-generated transcripts automatically No language selection needed Perfect for bulk transcript collection AI processing, summarization, analysis Content accessibility ✅ Output Format { "fullTranscript": "Auto-generated transcript text...", "wordCount": 1234, "transcript": [...timestamps...] } `

Regional Prospecting for registered Companies in Germany Find and qualify registered companies in specific regions using Implisense Search API (Handelsregister). This API provides all officially registered companies in Germany (about 2,5 million). Input Parameters: query: Search terms (e.g., "software OR it") regionCode: ZIP/postal code region (e.g., "de-10") industryCode: NACE industry code (e.g., "J62") pageSize: Max results (1-1000) Quality Levels: High:** Score ≥15 (active, website, full address) Medium:** Score <15 How it works Phase 1: Init Phase 2: Search Phase 3: Vetting Setup steps 1. Configure Credentials: Set up RapidAPI API credentials Create an account on RapidAPI (free tier available) Insert your RapidAPI x-rapidapi-key as password 2. Configure Search Parameters see above. 3. Connect CRM/Database After "Merge & Log Results" node, add: HTTP Request node for REST API Database node for direct insertion Or CRM-specific integration node

Internet Search Chat with Firecrawl How it works A user sends a query via the chat widget and the Chat Trigger captures the message. The chat flow posts the query to the backend webhook (HTTP Request) which forwards it to the search service. The webhook calls Firecrawl to run the web search and returns raw results. A formatter converts the raw results into concise Markdown blocks and separators. The chat node sends the formatted search summary back to the user. Optional: an admin can manually trigger a credits check to review Firecrawl usage. Setup [ ] Add Firecrawl API credentials in n8n. [ ] Update the webhook URL in the "Define constants" node to your n8n instance URL. [ ] Configure and enable the Chat Trigger (make it public and set initial messages). [ ] Ensure the webhook node path matches the constant and is reachable from the chat node. [ ] Test the chat by sending a sample query and verify the formatted search results. [ ] (Optional) Run the manual "Check credits" trigger to monitor Firecrawl account usage.