HumationHuman + Automation
Back to Catalog

🎨 Interactive image editor with FLUX.1 fill tool for inpainting

EduardEduard
17536 views
2/3/2026
UncategorizedPlaceholderCustomTemplateAutomation
Official Page

> Like this template? Connect with Eduard via LinkedIn.

This workflow is a prototype of an AI-powered image editing interface, similar to Photoshop's Generative Fill feature, but running entirely in the browser. It provides a web-based editor that allows users to:

  • Select areas in images using an adjustable brush tool
  • Input text prompts to guide the AI generation
  • Compare original and generated images side by side
  • Iterate on edits with different prompts and settings
  • Save or reuse generated images

> 🎨 Perfect for product catalog management, seasonal content updates, and creative image editing tasks!

📋 Requirements

🔧 Key Components

  1. Simple Editor Interface

    • HTML page with an editor is served on the Webhook call
    • Adjustable brush selection tool
    • Provides several mock examples and allows uploading custom images
    • Basic prompt and FLUX model parameter controls

  2. Image Processing Pipeline

    • Handles image and mask separately
    • Processes FLUX Fill API requests
    • Delivers results back to the editor

  3. Result Viewer

    • Split-screen comparison of original and generated images
    • Interactive slider for before/after comparison
    • Options to save or continue editing
    • Support for multiple iteration cycles

🎯 Use Cases

This prototype is particularly useful for:

  • Testing AI-powered image editing concepts
  • Quick product visualization experiments
  • Exploring creative image variations
  • Demonstrating inpainting capabilities

> 💡 Pro Tip: Save masks for frequently edited areas to quickly generate variations with different prompts!

The workflow can be extended to integrate with various data sources and can be customized for specific business needs.

n8n Workflow: Interactive Image Editor with Flux1 Fill Tool for Inpainting

This n8n workflow provides a framework for an interactive image editor, specifically designed to integrate a "Flux1 Fill Tool" for inpainting. It acts as a backend API endpoint, receiving image editing requests, processing them, and returning a response. The workflow includes conditional logic to handle different types of requests, a waiting mechanism, and HTML rendering capabilities.

What it does

This workflow orchestrates the following steps:

  1. Receives Webhook Request: It starts by listening for incoming HTTP POST requests to a defined webhook URL, acting as the main entry point for image editing commands.
  2. Conditional Processing: It uses an "If" node to evaluate the incoming request. Based on predefined conditions, it routes the request to different processing paths.
  3. No Operation (Placeholder): If the "If" condition evaluates to false, the workflow proceeds through a "No Operation" node, which acts as a placeholder for future logic or simply passes the data through without modification.
  4. Edit Fields (Set): If the "If" condition evaluates to true, the workflow uses an "Edit Fields (Set)" node to modify or add data to the incoming item. This could be used to prepare data for the inpainting tool or other image manipulations.
  5. Wait for Processing: After the conditional logic, the workflow introduces a "Wait" node, pausing execution for a specified duration. This could simulate the time required for an image processing task, or allow an external service to complete its work.
  6. HTML Rendering: The workflow includes an "HTML" node, suggesting that it might generate or process HTML content as part of its output, possibly for displaying results or an interactive interface.
  7. HTTP Request (External API Call): It makes an HTTP request to an external API. This is likely where the "Flux1 Fill Tool" for inpainting or other image processing services would be invoked.
  8. Merge Results: A "Merge" node is used to combine data from different paths in the workflow, ensuring all relevant information is collected before the final response.
  9. Respond to Webhook: Finally, the workflow sends a response back to the original webhook caller, delivering the results of the image editing operation.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance to host and execute the workflow.
  • External Image Processing API: An external API endpoint that provides the "Flux1 Fill Tool" or other image editing functionalities. This API will be called by the "HTTP Request" node.
  • Webhook Client: An application or service capable of sending HTTP POST requests to the n8n webhook URL and receiving responses.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure the Webhook Trigger:
    • Activate the "Webhook" node (Node ID: 47).
    • Copy the test or production webhook URL. This URL will be the endpoint your external application sends image editing requests to.
  3. Configure the "If" Node:
    • Edit the "If" node (Node ID: 20) to define the conditions for routing requests. For example, you might check for a specific parameter in the incoming webhook data to determine which image editing operation to perform.
  4. Configure the "Edit Fields (Set)" Node:
    • If your "If" condition routes to this node (Node ID: 38), configure it to set or modify any necessary data for the subsequent image processing steps.
  5. Configure the "Wait" Node:
    • Adjust the duration in the "Wait" node (Node ID: 514) if you need to simulate a longer or shorter processing time.
  6. Configure the "HTTP Request" Node:
    • Edit the "HTTP Request" node (Node ID: 19).
    • Set the URL to your external image processing API endpoint (e.g., the "Flux1 Fill Tool" API).
    • Configure the Method (e.g., POST) and Body to send the necessary image data and parameters to the external API. This might involve sending base64 encoded images, URLs, or other relevant data from the incoming webhook.
    • Add any required Headers (e.g., API keys, content-type).
  7. Configure the "HTML" Node:
    • If you intend to generate or process HTML, configure the "HTML" node (Node ID: 842) accordingly.
  8. Activate the Workflow: Save and activate the workflow in n8n.
  9. Send Requests: Send HTTP POST requests to the webhook URL configured in step 2. The body of your request should contain the data needed for the image editing operation, which the "If" node will then evaluate.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942