Node-RED

Use Node-RED’s built-in nodes to create an image, recover it by project ID, and save the completed PNG. This flow was verified with Node-RED 5.0.9. No community node, SDK, or additional package is required. The example requests one 640px square image with flux-2-klein and saves the first download. The verified output format was PNG.

​

Import and configure

1. Download the flow JSON.
2. In the Node-RED editor, select Menu → Import, choose the JSON file, and import it.
3. Open Magic Hour API — set bearer credential. Select Use authentication, set Type to bearer authentication, and paste your Magic Hour API key into Token. Enter the raw key, without a Bearer prefix.
4. Configure the output directory, then click Deploy.

Node-RED adds the Bearer prefix and stores the token as a password credential. Keep it out of node properties, HTTP headers, Debug output, screenshots, and exported JSON. The separate Download image — NO authentication node must not receive an API key.

​

Choose the output directory

By default, Prepare NO-AUTH media GET sets msg.filename to /data/magic-hour-<project-id>.png. In Docker, this is inside the container: look in the host directory mounted at /data to find the saved file. For a local installation or another container mount, edit the filename rule in Prepare NO-AUTH media GET to use an existing absolute directory writable by Node-RED. Keep the project-ID filename expression. The file node does not create missing directories.

​

Create once

1. Open Create once (billable) to review its image prompt and generation options.
2. Click Deploy if you changed them.
3. Click that node’s inject button once. This sends a paid creation request.
4. Copy and save the returned id from ID / status / credits only in the Debug sidebar.

The flow never starts automatically, schedules a creation, polls, or retries a request. Clicking Create once (billable) again submits another paid creation.

​

Recover and save the image

1. Open Recover existing image (GET only).
2. Replace YOUR_EXISTING_IMAGE_PROJECT_ID in project_id with the saved image project ID.
3. Click Done, then Deploy.
4. Click that node’s inject button to retrieve the existing project.

Recovery sends a GET request and does not create another generation. If the project is still running, check again later using the same recovery button and ID. Once the project is complete and has an HTTPS download URL, the flow fetches the image with a separate unauthenticated GET. It writes only an HTTP 200 response to the configured PNG path. Saved file path only appears in the Debug sidebar after the file node finishes writing.

​

Read results and errors

ID / status / credits only shows the project ID, status, HTTP status, and any returned credits_charged and credits_refunded values, including zero. Provider status and a saved file are separate results: complete alone does not prove a successful download or write. Keep Debug nodes limited to their configured summary or file path. Full-message Debug can expose credentials, response metadata, and temporary signed download URLs. A provider failure does not trigger a replacement generation.

​

Verified behavior

An actual Node-RED editor run imported and deployed this flow, then created one image for 5 Magic Hour credits. A separate recovery GET retrieved the same accepted project ID, downloaded the completed image without authentication, and saved the 640×640 PNG through the native file node. The saved PNG passed a full image decode. The tested runtime stored the API token as an encrypted native credential. Its editor export omitted credentials and signed download URLs; all 16 operational nodes matched the downloadable flow. No chat model or custom Node-RED package was used.