ActionBlack Forest LabsUpdated September 2026

How do I retrieve a Flux generation result?

Short answer: You can get generation result in Black Forest Labs by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Black Forest Labs Get Generation Result action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Generation Result in Black Forest Labs — start free All 4 Black Forest Labs actions

Get Generation Result in Black Forest Labs — start free

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.

Triggered by

Apps that pair well as the trigger for Get Generation Result.

Any of these apps can fire this action as part of a workflow.

Gmail → Black Forest Labs

1 Gmail triggers

Slack → Black Forest Labs

13 Slack triggers

Google Sheets → Black Forest Labs

2 Google Sheets triggers

HubSpot → Black Forest Labs

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Black Forest Labs returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Generation Result support batch operations?

Run Get Generation Result inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Black Forest Labs's rate limits.

More actions

Other Black Forest Labs actions.

Action

Edit Image with Kontext

Takes a source image plus a text instruction ("make the sky stormy", "remove the person on the left"). Flux Kontext preserves the unchanged parts and applies the requested edit. Better at "keep this thing, change that thing" than re-generating from scratch with a reference image.

Action

Inpaint with Flux Fill

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.

Action

Generate Image with Flux

Text-to-image generation across Flux variants (Schnell for fastest/cheapest, Dev for open-weights, Pro for highest quality, Ultra for strongest text rendering). Returns a task ID; poll Get Result for the finished image URL.

Get Generation Result in Black Forest Labs — start free