PiAPI Flux Generate Image: PiAPI 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
Prompt prompt	string	Required	Prompt (required)
Model model	options	Optional	Model. Options: Flux Dev, Flux Schnell, Flux Pro 1.1 Ultra
Width width	string	Optional	Width
Height height	string	Optional	Height

Sample request

{
  "prompt": "{{trigger.prompt}}",
  "model": "{{trigger.model}}",
  "width": "{{trigger.width}}",
  "height": "{{trigger.height}}"
}

Returns

{
  "code": 200,
  "data": {
    "status": "pending",
    "task_id": "task_abc"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about PiAPI Flux Generate Image.

What does the PiAPI Flux Generate Image action do in PiAPI?

Generates images using Flux (dev or pro) via PiAPI's unified gateway. For workflows that bundle multiple AI models behind one API key.

What inputs does PiAPI Flux Generate Image require?

Required: 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 PiAPI 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 PiAPI Flux Generate Image support batch operations?

Yes. Run PiAPI Flux Generate Image inside a Loop node to process arrays. Tiny Command handles PiAPI's rate limits automatically so you don't have to throttle manually.

More actions