PiAPI Midjourney Imagine: 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)
Aspect Ratio aspect_ratio	options	Optional	Aspect Ratio. Options: 1:1, 16:9, 9:16 …
Process Mode process_mode	options	Optional	Process Mode. Options: Relax, Fast, Turbo

Sample request

{
  "prompt": "{{trigger.prompt}}",
  "aspect_ratio": "{{trigger.aspect_ratio}}",
  "process_mode": "{{trigger.process_mode}}"
}

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 Midjourney Imagine.

What does the PiAPI Midjourney Imagine action do in PiAPI?

The no-Discord path to Midjourney. PiAPI handles the Discord-bot interaction; you get a clean HTTP API. Returns task ID; poll for the finished image.

What inputs does PiAPI Midjourney Imagine 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 Midjourney Imagine support batch operations?

Yes. Run PiAPI Midjourney Imagine 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