# AI videos and images in your n8n workflows

> Run eroq Flows from any n8n workflow, cloud or self-hosted, and get every render back: AI videos, images, voice lines and captions, from one HTTP Request node.

Cloud or self-hosted, one HTTP Request node is enough. Your workflow sends its data to an eroq flow, Clap writes the prompt, the image, the clip or the voice line renders, and every render comes back to a Webhook node for the next one. Nothing to install: a webhook URL and, if you want it, your API key.

**Set up with n8n:** https://eroq.ai/studio/connectors?connect=n8n

```
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

1. In the eroq studio, create a flow that starts « When a webhook is called », or start from the n8n template. Publish it and copy its URL from the trigger.
2. In your workflow, add an HTTP Request node: method POST, the URL, and a JSON body with the fields the flow reads, such as the prompt.
3. End the flow with « Send to a webhook » and the production URL of a Webhook node: your workflow gets every render link and every text.

## What you get

### Cloud or self-hosted

The HTTP Request node is part of every n8n, on n8n Cloud as on your own server. Whatever runs before it can feed the flow: a database, a sheet, a CRM, a schedule, an AI agent.

### 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 Webhook node: 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

- n8n Cloud or a self-hosted n8n
- 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)
- To get results pushed back: a Webhook node reachable over HTTPS from the internet (otherwise, read the run with the API)

## FAQ

### Do I need an eroq community node?

No. The HTTP Request node starts a flow with one POST to its URL, and a Webhook node receives the results. With your API key as a Bearer header, the same node can call any eroq endpoint.

### My n8n runs on a private server. Does it work?

Starting flows does: n8n calls eroq, nothing has to reach your server. To get results pushed back, eroq needs a public HTTPS URL for your Webhook node; without one, read the run with GET /v1/flows/{id}/runs/{run_id}, with a Wait node between two reads.

### How do I keep the files in n8n?

The links a run sends back are signed and expire after a while. Copy the file in the next step (a storage node 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.

## Related

- https://eroq.ai/plugins — All plugins
- https://eroq.ai/tools/ai-workflow-automation — Flows: AI workflow automation
- https://eroq.ai/plugins/zapier — eroq for Zapier
- https://eroq.ai/plugins/make — eroq for Make
- https://eroq.ai/docs/flows — Flows API docs

---

This page as HTML: https://eroq.ai/plugins/n8n · Studio: https://eroq.ai/studio · Docs: https://eroq.ai/docs · Machine index: https://eroq.ai/llms.txt