ActionBlack Forest LabsUpdated September 2026
How do I inpaint with Flux Fill?
Short answer: You can inpaint with flux fill in Black Forest Labs by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Black Forest Labs Inpaint with Flux Fill action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Image (base64 or URL) image | string | Required | Image (base64 or URL) (required) |
Mask (base64 or URL) mask | string | Required | PNG mask — white = fill, black = preserve |
Prompt prompt | string | Required | Prompt (required) |
Sample request
{"image": "{{trigger.image}}","mask": "{{trigger.mask}}","prompt": "{{trigger.prompt}}"}
Returns
{"id": "task_abc"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Inpaint with Flux Fill.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Inpaint with Flux Fill.
What does the Inpaint with Flux Fill action do in Black Forest Labs?
Mask-driven inpainting — pass an input image, a black-and-white mask (white = regenerate, black = preserve), and a prompt describing what should fill the white area. Flux Fill regenerates only the masked region while preserving everything else. The standard tool for removing unwanted objects or replacing specific areas.
What inputs does Inpaint with Flux Fill require?
Required: Image (base64 or URL), Mask (base64 or URL), Prompt. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Black Forest Labs returns an error?
The run history shows the failed step with its input and the error message Black Forest Labs returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Inpaint with Flux Fill support batch operations?
Run Inpaint with Flux Fill inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Black Forest Labs's rate limits.
More actions
Other Black Forest Labs actions.
Action
Edit Image with Kontext
Takes a source image plus a text instruction ("make the sky stormy", "remove the person on the left"). Flux Kontext preserves the unchanged parts and applies the requested edit. Better at "keep this thing, change that thing" than re-generating from scratch with a reference image.
ActionGenerate Image with Flux
Text-to-image generation across Flux variants (Schnell for fastest/cheapest, Dev for open-weights, Pro for highest quality, Ultra for strongest text rendering). Returns a task ID; poll Get Result for the finished image URL.
ActionGet Generation Result
Polls a task ID for status; returns the image URL in result.sample once status is Ready. For production, configure BFL's webhook on the generation request to skip polling and get a push notification when ready.