Get Generation Result: 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
Task ID task_id	string	Required	Task ID (required)

Sample request

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

Returns

{
  "id": "task-abc123",
  "result": {
    "sample": "https://example.com/img.jpg"
  },
  "status": "Ready"
}

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

FAQ

Questions about Get Generation Result.

What does the Get Generation Result action do in Black Forest Labs?

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.

What inputs does Get Generation Result 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 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 Get Generation Result support batch operations?

Yes. Run Get Generation Result 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