Inpaint with Flux Fill: Black Forest Labs action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Inpaint with Flux Fill support batch operations?

Yes. Run Inpaint with Flux Fill inside a Loop node to process arrays. Tiny Command handles Black Forest Labs's rate limits automatically so you don't have to throttle manually.

More actions