Nodaro with Zapier

Zapier can start any Nodaro workflow from a Zap and receive the finished image, video or audio in a second Zap. Nodaro does the generation. Zapier 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.

Before you start

The steps on this page use Webhooks by Zapier. Zapier lists it as a premium app, available on paid plans and during a free trial. Check your Zapier plan before you build.

How the two connect

1. In the first Zap, a Webhooks by Zapier POST action sends 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 a Catch Hook trigger, which starts a second Zap with the result.

Step 1: Catch the result in Zapier

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

1. Create a Zap with the trigger Webhooks by Zapier › Catch Hook.
2. Click Continue. In the Test tab, Zapier shows your webhook URL. Click Copy.
3. Leave the test open. You send the first result to it in step 2.

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 Zapier webhook URL into Webhook URL. Under Input Parameters, add image_url of type Image URL, and connect the image to it.
4. Save the workflow and click Run once. The result arrives at the Catch Hook, and in Zapier you click Test trigger to see it.
5. 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.

Add the actions that use the result to the second Zap, and publish it.

Step 3: Start the run from Zapier

1. In the Zap that should start the run, add the action Webhooks by Zapier › POST.
2. Paste the Nodaro address into URL and set Payload Type to json.
3. Under Data, add the key prompt on the left, and map its value from an earlier step on the right.
4. Test the step, then publish the Zap.

Zapier sends this body to Nodaro:

{ "prompt": "A red kite over a green hill, morning light" }

What comes back

Nodaro answers the POST 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 the Catch Hook. 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" }

The second Zap maps image_url like any other field.

Why not poll with an API token

Zapier keeps the headers of a webhook step in plain text, where anyone with access to the Zap can read them. A personal API token in a header is exposed the same way. The Webhook Output method needs no token, so prefer it in Zapier. To poll from your own code instead, see Run a workflow with new input values.

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. Zapier counts its own tasks on its side.

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