A discount on premium plans when you sign upGet your discount
eroq
×

eroq · Zapier automation

AI videos and images, started from any Zap

A new row in a sheet, a form answer, a product in your shop: Zapier already sees it happen. Send it to an eroq flow and the run does the rest. Clap writes the prompt, the image, the clip or the voice line renders, and the result comes back to your Zap for the next step. Nothing to install: a webhook URL and, if you want it, your API key.

Set up with Zapier

Opens Plugins & connectors in the eroq studio

What your Zap sends
POST https://eroq.ai/hooks/flows/<flow id>/<token>
Content-Type: application/json

{ "prompt": "A neon rooftop at night, slow push-in" }

Set it up in three steps

  1. 1In the eroq studio, create a flow that starts « When a webhook is called », or start from the Zapier template. Publish it and copy its URL from the trigger.
  2. 2In your Zap, add Webhooks by Zapier with the POST event: paste the URL, choose JSON and map the fields the flow reads, such as the prompt.
  3. 3End the flow with « Send to a webhook » and the URL of a Catch Hook trigger: the next Zap gets every render link and every text.

What you get

Thousands of apps can start a render

Anything a Zap triggers on can start a flow: Google Sheets, Typeform, Shopify, Airtable, Notion, your calendar. The fields it sends are step #1 of the run, and every step can read them.

Clap writes, eroq renders

The fields your tool sends become step #1 of the run. Clap turns a product name, a headline or a row of a sheet into a director's prompt, then the flow renders the image, the clip or the voice line on the engine you picked.

Every render comes back

End the flow with « Send to a webhook » pointed at a Catch Hook trigger: the next step gets each render's link, each text Clap wrote and the credits spent. Or add ?callback_url= to the flow's URL, and the finished run is posted there once.

Or straight to the API

With an API key as a Bearer header, one HTTP call starts an image or a video render (/v1/images/generations, /v1/videos/generations) or any published flow, with a callback_url. Signed webhook events (image.generation.succeeded, video.generation.succeeded, flow.run.succeeded…) tell your workflow the moment a render is ready.

Same wallet, same prices

Everything bills the credit prices of the studio and the API — nothing new to meter. New accounts start with 50 free credits.

Requirements

  • →A Zapier account that can use Webhooks by Zapier
  • →An eroq account on the Studio plan or higher to run a flow from another tool (every plan can build flows, and call the image and video API with a key)

Frequently asked questions

Do I need to install an eroq app in Zapier?

No. Webhooks by Zapier does it all: one POST to your flow's URL starts a run, and a Catch Hook trigger receives the results. With your API key, the same Webhooks step can call any eroq endpoint.

What can I build with it?

A clip for every new product in your shop, a picture for every row of a content calendar, a voiceover for every new article, a cover for every episode. The flow decides what to render; Zapier decides when.

How do I keep the files in Zapier?

The links a run sends back are signed and expire after a while. Copy the file in the next step (Google Drive, Dropbox or your social scheduler) rather than storing the link; the render also stays in your eroq library.

Is the flow's URL safe to paste into another tool?

The URL is the key: anyone who has it can start the flow, on your workspace's credits. Keep it in your tool's settings, and click « New URL » on the trigger to replace it; the old one stops answering at once.

How much does it cost?

The studio's prices, nothing extra on eroq's side: 10 credits for a Krea 2 image, 75 for a five-second Seedance 2.0 Mini clip, Clap's writing included. Failed renders refund themselves. Running a flow from another tool comes with the Studio plan.

What content is allowed?

Fiction under eroq's written acceptable-use policy — uncensored on eroq's own models. Minors, real people without consent and illegal content are refused by policy on every surface. Inside an assistant, the assistant's own usage policy also applies to what it will ask eroq for.

Keep exploring