PiAPI Fetch Task: 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
Task ID task_id	string	Required	Task ID (required)

Sample request

{
  "task_id": "{{trigger.task_id}}"
}

Returns

{
  "code": 200,
  "data": {
    "output": {
      "image_url": "https://example.com/i.png",
      "image_urls": []
    },
    "status": "completed",
    "task_id": "task_abc"
  }
}

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

FAQ

Questions about PiAPI Fetch Task.

What does the PiAPI Fetch Task action do in PiAPI?

Polls any PiAPI generation task (Midjourney, Flux, Kling, Suno, etc.) until complete. Result URL appears in output.image_url/video_url/audio_url depending on type.

What inputs does PiAPI Fetch Task require?

Required: Task ID. 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 Fetch Task support batch operations?

Yes. Run PiAPI Fetch Task 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