by AppUnits AI
Generate Invoices for Customers with Jotform and QuickBooks This workflow automates the entire process of receiving a product/service order, checking or creating a customer in QuickBooks Online (QBO), generating an invoice, and emailing it — all triggered by a form submission (via Jotform). How It Works Receive Submission Triggered when a user submits a form. Collects data like customer details, selected product/service, etc. Check If Customer Exists Searches QBO to determine if the customer already exists. If Customer Exists:* *Update** customer details (e.g., billing address). If Customer Doesn’t Exist:* *Create** a new customer in QBO. Get The Item Retrieves the selected product or service from QBO. Create The Invoice Generates a new invoice for the customer using the item selected. Send The Invoice Automatically sends the invoice via email to the customer. Who Can Benefit from This Workflow? Freelancers** Service Providers** Consultants & Coaches** Small Businesses** E-commerce or Custom Product Sellers** Requirements Jotform webhook setup, more info here QuickBooks Online credentials, more info here
by Aditya Malur
This n8n template demonstrates how to automatically download an Instagram Reel, analyze its content using AI video understanding, and regenerate a similar video using AI video generation models. The workflow creates AI-powered variations of existing video content while maintaining visual consistency and style from the original source material. Use cases are many: Content creators can produce multiple variations of trending reels, social media managers can recreate viral content with brand-specific modifications, or marketers can generate similar videos without copyright concerns while maintaining the original's visual appeal and storytelling structure. Good to know Video generation typically takes 2-5 minutes per video. The workflow includes automatic polling to check completion status. Minimax Video-01 generates videos up to 6 seconds long at 720p resolution and 25fps with cinematic camera movements. Gemini 2.0 Flash processes video at 1 frame per second (approximately 300 tokens per second of video), making it ideal for detailed video analysis. The workflow includes retry logic for failed API requests to ensure reliability. Ensure you have sufficient API credits in your Replicate account before running high-volume workflows. How it works The workflow begins when a user submits an Instagram Reel URL through the chat trigger interface. The RapidAPI Instagram Reels Downloader fetches the video metadata and download URL from Instagram. Downloaded video data is formatted and validated to ensure successful retrieval before proceeding. The video file is uploaded to Google's Gemini 2.0 Flash model via their File API for processing. Gemini 2.0 Flash analyzes the video frame-by-frame, generating a comprehensive description covering visuals, audio, movements, lighting, camera angles, and transitions. The AI-generated description is formatted as a continuous text prompt (lowercase, no punctuation) optimized for video generation models. This detailed prompt is sent to Replicate's Minimax Video-01 model to generate a new video based on the analysis. The workflow polls the Replicate API every 2 minutes to check generation status, automatically looping until completion. Once generation succeeds, the final AI-generated video is downloaded and ready for use or further processing. How to use The chat trigger node accepts Instagram Reel URLs as input, but you can replace this with webhooks, forms, or scheduled triggers depending on your automation needs. Replace all placeholder API keys in the workflow before activation (RapidAPI, Google AI Studio, and Replicate). Test with short Instagram Reels first (under 30 seconds) to optimize processing time and token usage. The workflow automatically handles null checks and retries if the initial download fails, ensuring robust execution. Requirements RapidAPI account for Instagram Reels Downloader API (handles video extraction from Instagram) Google AI Studio API key with Gemini 2.0 Flash access enabled (for advanced video analysis) Replicate API account with sufficient credits for Minimax Video-01 model access (for AI video generation) Active n8n instance (self-hosted or cloud) to run the workflow automation Customising this workflow This AI video recreation workflow can be adapted for numerous creative and business applications. Try extending it to generate multiple style variations from one input video, add branding overlays or watermarks before final output, or integrate with cloud storage (Google Drive, Dropbox) for automated archiving. You can also chain this workflow with content scheduling tools to automatically post generated videos to social media platforms, or combine it with analytics nodes to track which AI-generated variations perform best with your audience.
by Oneclick AI Squad
This automated n8n workflow provides real-time currency conversion by capturing GET requests via a webhook, parsing exchange rate data from Google Search, and returning a formatted response. The system handles query parameter validation and error cases to ensure reliable conversions. What is Real-Time Currency Conversion? Real-time currency conversion involves fetching the latest exchange rates from Google Search via HTTP requests, processing the data, and delivering a user-friendly conversion result based on a provided query parameter. Good to Know The workflow requires a valid query parameter (q) for conversion requests Google Search parsing depends on the availability and structure of search results Error handling is included for missing query parameters Responses are formatted for easy integration How It Works Webhook* - Captures GET requests with query parameter *q** Check Query Parameter** - Validates that the required query parameter exists Fetch Exchange Rate** - Makes HTTP request to Google search for exchange rates Error Response** - Handles missing query parameter errors Extract Conversion Data** - Processes HTML response to extract conversion data Format Currency Response** - Formats the result into a user-friendly response Send Conversion Response** - Returns the formatted response How to Use Import the workflow into n8n Configure the webhook to receive GET requests with a query parameter (q) Test the workflow with sample conversion queries (e.g., "1 USD to INR") Monitor for error responses and adjust query handling if needed Requirements Webhook configuration Internet access for Google Search requests Customizing This Workflow Adjust the query parameter validation in the Check Query Parameter node to support additional formats Modify the Format Currency Response node to change the output format based on user needs
by R4wd0G
Who’s it for Operators and makers who capture tasks from custom forms, bots, or automations and want them to appear as time-boxed events in Google Calendar with minimal setup. How it works A Webhook receives a payload containing the task title and a due date (as Unix seconds). The workflow formats the date, checks the most recently updated events in your calendar to avoid duplicates, and creates a new 30-minute event (configurable). After creation, it optionally deletes the original task, keeping your Task list clean and your Calendar up to date. How to set up Select your Google Tasks and Google Calendar credentials. Open the Configuration node and set tasklistId, calendarId (use primary or a specific calendar), defaultMinutes, and eventColor. Send a sample POST to the Webhook with { TaskName, DueDateTimeSeconds }. Run once in manual mode and, if all looks good, activate. Requirements Google accounts for Tasks and Calendar. Appropriate scopes/permissions in the selected credentials. How to customize the workflow Change the event duration/color in Configuration. Adjust duplicate detection by modifying the Calendar search window and query. Map additional fields (e.g., description, attendees) on the Calendar node’s optional fields. Tags Google Calendar, Google Tasks, Webhook, Automation, Productivity Categories Productivity, Google, Calendar
by Arjan ter Heegde
n8n Placeholdarr for Plex (BETA) This flow creates dummy files for every item added in your *Arrs (Radarr/Sonarr) with the tag unprocessed-dummy. It’s useful for maintaining a large Plex library without needing the actual movies or shows to be present on your Debrid provider. How It Works When a dummy file is played, the corresponding item is automatically monitored in *Arr and added to the download queue. This ensures that the content becomes available within ~3 minutes for playback. If the content finishes downloading while the dummy is still being played, Tautulli triggers a webhook that stops the stream and notifies the user. Requirements Each n8n node must have the correct URL and authorization headers configured. The SSH host (used to create dummy files) must have FFmpeg installed. A Trakt.TV API key is required if you're using Trakt collections. Warning > ⚠️ This flow is currently in BETA and under active development. > It is not recommended for users without technical experience. > Keep an eye on the GitHub repository for updates. https://github.com/arjanterheegde/n8n-workflows-for-plex
by The Growth Bolt
This n8n template uses AI to generate product mockups by composing a product image onto a model or template image. This workflow provides a powerful solution for creating dynamic marketing assets and e-commerce visuals. Use cases are many: Instantly create virtual try-on images for apparel, place your product into different scenes for advertisements, or generate custom marketing material without needing a physical photoshoot. Good to know This workflow uses the OpenRouter API to access Google's Gemini model. You will need an OpenRouter account. The model used is google/gemini-2.5-flash-image-preview:free. While this specific model may be free, costs can vary depending on the model you choose and your usage on OpenRouter. Always check their latest pricing. The workflow is triggered by a form. To use it, you must activate the workflow and use its Production URL. How it works A user submits a product image, a template/model image, and a text prompt via the n8n form trigger. The images are then converted to Base64 strings so they can be used in an API request. A multimodal payload is sent to the OpenRouter API. Gemini's image generation model is used, which takes all 3 inputs (the two images and the prompt) to understand how to compose the final image. Gemini generates a new image based on the instructions and returns it as a Base64 string. The workflow extracts this output string and uses a "Convert to file" node to convert the data back into a binary image file, ready for use. How to use First, set up your OpenRouter API credential in n8n. Activate the workflow. Open the Production URL for the form trigger. Upload your product image, your template image, and write a descriptive prompt. Submit the form to execute the workflow and generate your image. Requirements An active n8n instance. An OpenRouter account and API key. Customising this workflow You can easily change the AI model by editing the JSON body in the HTTP Request node. OpenRouter provides access to a wide variety of models from different providers. Add a final step to automatically save the generated image. You can connect nodes for services like Google Drive, AWS S3, or Dropbox after the "Convert to File" node. Replace the Form Trigger with a Webhook Trigger to run this workflow programmatically from another application or service.
by WeblineIndia
📝 Compliance Report Collector (Google Form → Drive + MySQL) This n8n workflow automates the collection and archival of compliance reports submitted via Google Forms. Uploaded documents (PDF, DOCX, etc.) are archived into Google Drive and submission metadata is logged into a MySQL database. It ensures compliance documentation is properly stored, searchable and auditable without manual effort. ⚡ Quick Implementation Steps Import the JSON file into n8n. Set up a Google Form to POST file + metadata (reporter, category, etc.) to the /submit-report webhook. Update the Set Config node with your: MySQL connection details Google Drive folder ID Deploy and test a form submission with a file upload. Each report is stored in Drive and logged to your DB. 🎯 Who’s It For Compliance officers handling environmental or safety reports. Admins managing documentation for inspections. Renewable energy companies required to maintain audit-ready records. Any org needing structured report archival & metadata logging. 🛠 Requirements | Tool | Purpose | |------|---------| | n8n Instance | Workflow automation | | Google Drive | To archive uploaded reports | | MySQL Database | To log submission metadata | | Google Forms / HTML Form | Report submission source | 🧠 What It Does Listens for incoming POST requests with a file and metadata. Uploads the file to a specified Google Drive folder. Extracts metadata like: Reporter name Category/type Timestamp File name, MIME type Logs that metadata into a MySQL table for auditing or reporting. 🧾 Sample MySQL Table Schema CREATE TABLE report_logs ( id INT AUTO_INCREMENT PRIMARY KEY, reporter VARCHAR(100), category VARCHAR(100), timestamp DATETIME, file_name VARCHAR(255), mime_type VARCHAR(50), folder_id VARCHAR(100) ); 🔧 How To Set Up – Step-by-Step Import the JSON into n8n. Configure the following in the Set Config node: MySQL: dbHost, dbUser, dbPassword, dbName, dbTable Google Drive: driveFolderId Update the webhook URL in your Google Form (via Apps Script or middleware). Test submission with a file upload. Confirm: File lands in your Drive folder Log entry appears in your database ✨ How To Customize | Customization | How | |---------------|-----| | Add more form fields | Extend the metadata mapping in the Function node | | Rename files before upload | Modify filename in Google Drive node | | Add email confirmation | Add an Email Send node after DB insert | | Filter file types | Add IF node before upload to validate MIME type | ➕ Add‑ons (Optional Extensions) | Add-on | Description | |--------|-------------| | 📤 Email Acknowledgment | Email sender a confirmation with Drive link | | 🧾 PDF Parser | Auto-parse content using PDF.co or OpenAI | | 📊 Admin Dashboard | Display logs in Supabase or Metabase | | 🗃 File Backup | Copy files to Dropbox or S3 after Drive upload | 📈 Use Case Examples Collect monthly safety audits from plant staff into a Drive archive. Accept vendor compliance declarations via Google Form and auto-log to DB. Capture field inspection reports and tag by category for audit. Store weekly environmental reports for long-term access. 🧯 Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|----------| | File not uploaded | Drive ID is invalid | Check permissions and folder ID | | DB not logging | Connection or table issue | Verify DB credentials and schema | | Webhook not triggered | Form not integrated correctly | Ensure form POSTs file to n8n webhook | | Wrong file type | MIME mismatch | Validate acceptable types via Function/IF node | 📞 Need Help? Want to integrate this with audit dashboards or add Google Sheet exports? 👉 Contact WeblineIndia — Experts in compliance automation and renewable energy workflows.
by Zil Money
Create Digital Checks with OnlineCheckWriter using Forms This workflow automates the process of creating and sending digital checks through OnlineCheckWriter's API using user-friendly forms. Perfect for businesses that need to process one-off payments or integrate check payments into their automation workflows. Prerequisites Before using this template, ensure you have: OnlineCheckWriter Account: Sign up at onlinecheckwriter.com API Key: Generate from your OCW dashboard under Settings > API Verified Bank Account: Add and verify at least one bank account in OCW Bank Account ID: Found in your OCW dashboard under Bank Accounts How It Works This workflow uses a two-step form process: API Configuration Form: One-time setup to store your OCW credentials Check Details Form: Collects recipient and payment information for each check The workflow then automatically: Validates all required fields Sends the check request to OnlineCheckWriter's API Returns a confirmation with the check ID and tracking information Setup Instructions Step 1: Import the Workflow Copy this workflow template to your n8n instance Activate the workflow Step 2: Configure API Credentials Access the first form at: [your-n8n-url]/webhook/e4f29ca4-5982-42ae-950c-e4d1d7b10a93 Enter your API Key from OnlineCheckWriter Enter your Bank Account ID Provide a friendly Account Name for reference Step 3: Create Checks Access the check form at: [your-n8n-url]/webhook/72ea8a5d-4655-4ad3-bde2-024dd3dadd9f Fill in recipient details: Payee Name (required) Company Name (optional) Complete Address (required) Contact Information (phone & email required) Enter payment details: Amount (in USD) Memo (appears on check) Internal Note (for your records) Reference ID (optional tracking) Issue Date Submit to create and send the check Customization Options Switch to Production By default, this workflow uses the OCW test environment. To switch to production: Edit the Send Check via OCW API node Change URL from https://test.onlinecheckwriter.com/api/v3/quickpay/check to https://app.onlinecheckwriter.com/api/v3/quickpay/check Add Custom Fields You can extend the forms with additional fields: Invoice numbers Department codes Project references Custom metadata Integrate with Other Systems Connect this workflow to: Google Sheets: Track payments in a spreadsheet Slack: Send notifications when checks are created Email: Send confirmations to recipients Accounting Software: Update your books automatically Error Handling To add error notifications: Add an Error Trigger node Connect to email or Slack for alerts Log failed attempts to a database Workflow Components OCW API Configuration Form Collects and stores API credentials securely One-time setup per account Validates connection to OnlineCheckWriter Check Details Form User-friendly interface for payment entry Field validation ensures data accuracy Optional fields for flexibility Send Check via OCW API Handles API authentication Formats data according to OCW specifications Includes error handling with 30-second timeout Success Response Confirms check creation Provides check ID for tracking Returns status information Security Considerations API Keys: Store securely and never share Test Mode: Always test in OCW's sandbox environment first Access Control: Restrict form URLs to authorized users Data Validation: All inputs are validated before API submission Troubleshooting Common Issues: 401 Error: Invalid API key - verify in OCW dashboard 400 Error: Missing required fields - check form data 404 Error: Invalid bank account ID - verify in OCW Timeout: Network issues - check connectivity Support OnlineCheckWriter API Docs: developer.onlinecheckwriter.com n8n Community: community.n8n.io Template Issues: Contact via n8n template comments Use Cases This workflow is ideal for: Freelancers: Send client payments Small Businesses: Process vendor payments Property Management: Issue rent refunds Non-Profits: Distribute grants or donations HR Departments: Process reimbursements Version History v1.1: Added sticky notes, improved node naming, enhanced error handling v1.0: Initial release
by curseduca.com
📘 Curseduca – User Creation & Access Group Assignment How it works This workflow automates the process of creating a new user in Curseduca and granting them access to a specific access group. It works in two main steps: Webhook – Captures user details (name, email, and group information). HTTP Request – Sends the data to the Curseduca API, creating the user, assigning them to the correct access group, and sending an email notification. Setup steps Deploy the workflow Copy the webhook URL generated by n8n. Send a POST request with the required fields: name email groupId Configure API access Add your API Key and Bearer token in the HTTP Request node headers (replaCurseducace placeholders). Replace <GroupId> in the body with the correct group ID. Notifications By default, the workflow will trigger an email notification to the user once their account is created. Example use cases Landing pages**: Automatically register leads who sign up on a product landing page and grant them immediate access to a course, training, or bundle. Product bundles**: Offer multiple products or services together and instantly give access to the correct group after purchase. Chatbot integration: Connect tools like **Manychat to capture name and email via chatbot conversations and create the user directly in Curseduca. 📘 Curseduca – Criação de Usuário e Liberação de Grupo de Acesso Como funciona Este fluxo de trabalho automatiza o processo de criação de um novo usuário no Curseduca e a liberação de acesso a um grupo específico. Ele funciona em duas etapas principais: Webhook – Captura os dados do usuário (nome, e-mail e informações de grupo). HTTP Request – Envia os dados para a API do Curseduca, criando o usuário, atribuindo-o ao grupo correto e disparando uma notificação por e-mail. Passos de configuração Publicar o workflow Copie a URL do webhook gerada pelo n8n. Envie uma requisição POST com os campos obrigatórios: name email groupId Configurar o acesso à API Adicione sua API Key e Bearer token nos headers do nó HTTP Request (substitua os placeholders). Substitua <GroupId> no corpo da requisição pelo ID correto do grupo. Notificações Por padrão, o fluxo dispara uma notificação por e-mail para o usuário assim que a conta é criada. Casos de uso Landing pages**: Registre automaticamente leads que se inscrevem em uma landing page de produto e libere acesso imediato a um curso, treinamento ou pacote. Pacotes de produtos**: Ofereça múltiplos produtos ou serviços em conjunto e conceda acesso instantâneo ao grupo correto após a compra. Integração com chatbots: Conecte ferramentas como o **Manychat para capturar nome e e-mail em conversas e criar o usuário diretamente no Curseduca.
by Ruslan Elishev
🤖 Telegram Bot with Dynamic Menus & Rating System What It Does This n8n workflow creates an interactive Telegram bot with: Dynamic inline keyboards that respond to user clicks 5-star rating system for collecting feedback Personalized responses using the user's actual name Multi-level menu navigation (Main → Settings → Profile, etc.) Real-time message updates when buttons are clicked How It Works Receives messages via Telegram webhook trigger node Extracts user data (name, ID, message type) Builds dynamic menus based on user actions Sends/updates messages with inline keyboards Handles button clicks without page refresh 🚀 Setup Instructions Get Your Bot Credentials Configure Workflow Open "Set Bot Token" node Replace token with yours Save and activate workflow (Active) Test Your Bot Message your bot on Telegram Click the buttons to navigate menus Try the rating system on Feature 1 🎨 Customization Guide Add New Menu Items In the "Prepare Response" Function node, add new cases: case 'your_feature': responseText = 'Your feature description'; keyboard = [ [{ text: '🎯 Button 1', callback_data: 'action1' }], [{ text: '🔙 Back', callback_data: 'main' }] ]; break; Modify Rating Options Change star buttons to numbers or emojis: // Current: ⭐⭐⭐ // Alternative: 1️⃣ 2️⃣ 3️⃣ or 👎 👍 Change Bot Responses Edit responseText for message content Modify keyboard arrays for button layout Add HTML formatting: bold, italic 💡 ++Key Features Demonstrated++ HTTP Request workaround for dynamic keyboards (n8n Telegram node limitation) Callback query handling to prevent loading animations Message editing vs sending new messages User data extraction from Telegram API Switch-case menu routing for scalable navigation ⚠️ ++Important Notes++ Limitation: n8n's native Telegram node doesn't support dynamic inline keyboards, this is why need to use HTTP nodes. Solution demonstrated: Use HTTP Request node with Telegram Bot API directly
by Dominic Spatz
🔄 Purpose of the Workflow: The Update-N8N workflow is designed to automatically trigger a (Portainer) webhook to update an N8N container, but only if a new version of N8N is available. ⚙️ Detailed Workflow Steps: 🕒 Scheduled Trigger The workflow runs every 16 hours at minute 8 using a schedule trigger node. 🌐 Fetch Latest N8N Version It sends an HTTP GET request to https://registry.npmjs.org/n8n/latest to retrieve the latest published N8N version from the npm registry. 📈 Get Currently Running Local Version Another HTTP GET request is sent to https://127.0.0.1/metrics (likely the Prometheus metrics endpoint of the local N8N instance) to extract the currently installed N8N version. 🧠 Version Comparison The workflow compares the local version (parsed from metrics) with the latest available version. 📬 Trigger Portainer Webhook If the versions do not match (i.e., an update is available), a POST request is sent to a webhook URL, which might be a Portainer webhook that redeploys or updates the N8N container/stack. ✅ Key Benefits: No manual checks or updates needed. Triggers only when a new version is available. Integrates seamlessly with Portainer via webhook. Secure configuration, e.g., disallowing unauthorized TLS certs for external requests.
by Gegenfeld
This workflow automatically removes backgrounds from images using the APImage API. Simply provide an image URL, and the workflow will process it through AI-powered background removal, then download the processed image for use in your projects. Who's it for This template is perfect for: E-commerce businesses needing clean product images Content creators who need transparent background images Marketing teams processing large batches of images Developers building image processing applications Anyone who regularly needs background-free images How it works The workflow uses APImage's AI-powered background removal service to automatically detect and remove backgrounds from images. You provide an image URL through a form interface, the API processes the image using advanced AI algorithms, and returns a clean image with the background removed. The processed image is then downloaded and ready for use. How to set up Get your APImage API key: Sign in to the APImage Dashboard 🡥 (or create a new APImage account) Copy your API key from the dashboard Configure the API connection: Double-click the APImage Integration node Replace YOUR_API_KEY with your actual API key (keep the Bearer prefix) Test the workflow: Click the Remove Background form trigger Enter an image URL in the form Submit to process the image Set up output destination (optional): Add nodes after the Download node to save images to your preferred storage Options include Google Drive, Dropbox, databases, or cloud storage Requirements n8n instance (cloud or self-hosted) APImage 🡥 account and valid API key Images accessible via public URLs for processing How to customize the workflow Replace Input Source: Swap the Form Trigger with data from other sources like: Database queries (MySQL, PostgreSQL, SQLite) Cloud storage (Google Drive, Dropbox, S3) Other APIs or webhooks Airtable, Notion, or other productivity tools Add Output Destinations: Connect additional nodes after the Download step to save processed images to: Cloud storage services (Google Drive, Dropbox, S3) Databases for organized storage Content management systems Social media platforms Email attachments Batch Processing: Modify the workflow to process multiple images by connecting it to data sources that provide arrays of image URLs. Add Image Validation: Include nodes to validate image URLs or file formats before processing to avoid API errors. Workflow Structure Form Trigger → APImage Integration → Download → [Your Output Destination] The Form Trigger collects image URLs, APImage Integration processes the background removal via API, Download retrieves the processed image, and you can add any output destination for the final images. API Details The workflow sends a POST request to https://apimage.org/api/ai-remove-background with: Authorization header:** Your API key image_url:** The URL of the image to process async:** Set to false for immediate processing The processed image is returned with a transparent background and downloaded automatically.