OpenRuna
Sign in
← Workflows

FLUX-fill standalone

18 nodes · respondToWebhook, wait, httpRequest, webhook, html

Engine
n8n
Nodes
18
Trigger
scheduled/triggered
Source file
2042_Wait_Webhook_Automation_Webhook.json

Workflow flow

IntegrationsRespondToWebhookWaitHTTPWebhookHtmlMergeIFSetNoOp
100%
TRIGGER

Webhook

Webhook

Mockups

Set

NO OP

NoOp

Merge

Merge

FLUX Fill

HTTP

Editor page

Html

Respond to Webhook

RespondToWebhook

Wait 3 sec

Wait

Get Fill Image

HTTP

Check FLUX status

HTTP

Show the image to user

RespondToWebhook

Is Ready?

IF

12 steps · flows top to bottom, branches left to right

Browse by integration

respondToWebhookwaithttpRequestwebhookhtml
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

FLUX-fill standalone (18-node n8n automation, respondToWebhook, wait, httpRequest, webhook, html) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

This n8n workflow, "FLUX-fill standalone", wires together respondToWebhook, wait, httpRequest, webhook, html in 18 nodes. 18 nodes · respondToWebhook, wait, httpRequest, webhook, html Execution begins at the scheduled/triggered trigger and flows through the 18 configured nodes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Import "FLUX-fill standalone" into n8n, reconnect credentials for respondToWebhook, wait, httpRequest, webhook, html, and run the same automation in your own workspace.
  • Use it as a starting template when wiring respondToWebhook, wait, httpRequest, webhook, html — adjust node parameters to your accounts and record IDs.
  • Study how data moves from respondToWebhook to wait before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the respondToWebhook stack.

Example output

Imported into n8n, "FLUX-fill standalone" exposes 18 configured nodes. Trigger type: scheduled/triggered. Integrations: respondToWebhook, wait, httpRequest, webhook, html. Reconnect the respondToWebhook credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "FLUX-fill standalone" JSON into a plain-English runbook, node by node. It can flag where respondToWebhook rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for respondToWebhook, wait, httpRequest, webhook, html. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "FLUX-fill standalone" — extract respondToWebhook IDs and secrets into environment variables without changing the 18-node structure.

Frequently asked questions

How do I import "FLUX-fill standalone" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "FLUX-fill standalone" use?
It uses: respondToWebhook, wait, httpRequest, webhook, html. The flow diagram above shows how each service connects across the 18 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own respondToWebhook and wait credentials in n8n after import.
What trigger type does "FLUX-fill standalone" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "FLUX-fill standalone" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for respondToWebhook, wait, httpRequest, webhook, html.

Related resources