Nodaro with n8n

n8n can start any Nodaro workflow with one HTTP request and receive the finished image, video or audio on an n8n Webhook node. Nodaro does the generation. n8n decides when it runs and where the result goes next. Neither direction needs a Nodaro API key, because the workflow's own webhook address starts the run.

How the two connect

1. An n8n HTTP Request node posts a JSON body, for example a prompt, to the webhook address of a Nodaro workflow.
2. The Nodaro workflow starts with a Webhook Trigger, runs its nodes, and ends with a Webhook Output.
3. The Webhook Output posts the result to an n8n Webhook node, and the rest of your n8n workflow continues from there.

Step 1: Receive the result in n8n

Create the receiving end first, because the Nodaro workflow needs its address.

1. In n8n, add a Webhook node.
2. Set HTTP Method to POST, and give the node a Path, for example nodaro-result.
3. Keep Respond on Immediately, so n8n answers Nodaro at once.
4. Copy the Production URL.

n8n registers the Production URL when you publish the n8n workflow. The Test URL listens for only 120 seconds after you select Listen for test event, so use it only while you build.

Step 2: Build the Nodaro workflow

1. Add a Webhook Trigger node. Under Output Parameters, add a parameter named prompt of type Text.
2. Connect the prompt output to the prompt input of a Generate Image node, or any other node that makes a result.
3. Add a Webhook Output node. Paste the n8n Production URL into Webhook URL. Under Input Parameters, add image_url of type Image URL, and connect the image to it.
4. Save the workflow. Select the Webhook Trigger and copy its address under Webhook URL.

The address has the form https://app.nodaro.ai/v1/webhooks/<token>. The token works like a password: anyone who has the address can start the workflow.

Step 3: Start the run from n8n

1. In n8n, add an HTTP Request node where the run should start.
2. Set Method to POST and paste the Nodaro address into URL.
3. Turn on Send Body, set Body Content Type to JSON, and choose Using JSON under Specify Body.
4. Type the body. The keys are the names of your Output Parameters:

{ "prompt": "{{ $json.prompt }}" }

A faster way: select Import cURL in the HTTP Request node and paste this command with your token:

curl -X POST "https://app.nodaro.ai/v1/webhooks/<token>" \
  -H "Content-Type: application/json" \
  -d '{"prompt": "A red kite over a green hill, morning light"}'

What comes back

Nodaro answers the HTTP Request node at once, before anything is generated. The answer is 202 with the id of the run:

{ "executionId": "3f9e2b1a-7c6d-4e5f-8a9b-0c1d2e3f4a5b", "status": "pending" }

When the run finishes, the Webhook Output posts the result to your n8n Webhook node. The body has one key per Input Parameter, and media values are addresses of files on Nodaro:

{ "image_url": "https://cdn.nodaro.ai/images/2538b658-d2e1-42ee-890a-72ce06089feb.png" }

In n8n, the incoming body sits under body, so the next node reads the address as {{ $json.body.image_url }}.

Poll instead of a webhook

When n8n cannot receive a request from the internet, poll for the result with a personal API token. Polling works for workflows in your personal projects.

1. Keep the HTTP Request node from step 3. It returns the executionId.
2. Add a Wait node with Resume set to After Time Interval, for example 10 seconds.
3. Add an HTTP Request node with Method GET and the URL https://app.nodaro.ai/v1/api/status/{{ $json.executionId }}. Send the header Authorization with the value Bearer <your API token>, stored as an n8n credential.
4. Add an If node. While status is pending or running, connect its branch back to the Wait node.
5. When the status is completed, call https://app.nodaro.ai/v1/api/result/<executionId> the same way. The answer lists the run's outputs with their addresses.

Run a workflow with new input values describes the status and result answers.

Limits to plan for

What it costs

The Webhook Trigger and the Webhook Output cost nothing. You pay the credits of the nodes between them, at the same prices as in the editor. In the example above, each run costs the price of one Nano Banana 2 image, 22 credits. Credits reserved for a node that fails come back automatically.

The same pattern works in Make and Zapier. Automations covers schedules and the other ways to start a workflow.