← All N8N workflows
Automation & utilitiesHtmlHTTP RequestIfMergeNo Op

FLUX-fill standalone

Configured with Html, HTTP Request, Respond To Webhook, Wait, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TransformMergeMergeWeb / APIRespond to WebhookRespond To WebhookWaitWait 3 secWaitRoutingIs Ready?IfWeb / APIFLUX FillHTTP RequestWeb / APICheck FLUX statusHTTP RequestWeb / APIGet Fill ImageHTTP RequestWeb / APIShow the image to userRespond To WebhookTransformMockupsEdit FieldsTriggerWebhookWebhookTransformEditor pageHtmlRoutingNO OPNo Op

Node categories in this workflow

  • Transform
  • Web / API
  • Wait
  • Routing
  • Trigger

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
MergeTransformMergeSee node parameters
Respond to WebhookWeb / APIRespond To WebhookSee node parameters
Wait 3 secWaitWaitSee node parameters
Is Ready?RoutingIfSee node parameters
FLUX FillWeb / APIHTTP RequestPOST
Check FLUX statusWeb / APIHTTP RequestSee node parameters
Get Fill ImageWeb / APIHTTP RequestSee node parameters
Show the image to userWeb / APIRespond To WebhookSee node parameters
MockupsTransformEdit FieldsSee node parameters
WebhookTriggerWebhookSee node parameters
Editor pageTransformHtmlSee node parameters
NO OPRoutingNo OpSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • httpHeaderAuth

Workflow notes

Image array

Image array

  • Load from PC
  • Select one of the default images

Change this node to

get image URLs from your data source

HTML code of the editor

HTML code of the editor

  • Konva.js
  • img-comparison-slider to compare edits vs original file
  • Additional css + js files for the editor logic
Call FLUX-Fill Tool

Call FLUX-Fill Tool

Pass the following data:

  • original image
  • alpha mask from the editor
  • text prompt
  • additional settings
FLUX-fill standalone

FLUX-fill standalone

Purpose and structure

This folder contains the FLUX-fill standalone workflow. Its executable nodes use html, httpRequest, if, merge, noOp, respondToWebhook, set, wait, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Webhook

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/1589_Wait_Webhook_Automation_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

  • Deliver the editor with links to the images
  • Image processing part
  • Send back edited image

More in Automation & utilities