Automate Vidova with no code

Triggers use webhook subscriptions: signed generation.succeeded / generation.failed events for every generation you make — in the app or through the API. You can see and remove active subscriptions under Integrations in the app.

Integrations sign in with an API key (the Studio plan includes API access). Open Developers, create a key and copy it — it starts with vk_live_ and is shown only once. A key can spend your credits: store it only in the automation platform's credential store.

1. In n8n open Settings → Community Nodes → Install and enter n8n-nodes-vidova.
2. Add a Vidova node, create a Vidova API credential and paste your key.
3. Choose Generation → Generate, pick a model, write the prompt and put other parameters in Input (JSON), e.g. {"aspect_ratio":"16:9","duration":"8"}. Keep Wait for Completion on to get the finished media in the same run.
4. To react to finished generations, start a workflow with Vidova Trigger and activate it. n8n registers the subscription for you and removes it when the workflow is deactivated.

# n8n → Settings → Community Nodes → Install
n8n-nodes-vidova

Self-hosted n8n must be reachable over https from the internet for the trigger (set WEBHOOK_URL). The trigger verifies the Vidova-Signature of every delivery.

1. In a Zap, search for Vidova and connect your account with the API key.
2. Trigger: Generation Completed — choose succeeded, failed or both, optionally one model. Fires instantly.
3. Action: Generate Media — model, prompt, optional image URL and extra parameters (e.g. aspect_ratio = 9:16). It returns the queued generation right away.
4. Use the result with a second Zap triggered by Generation Completed, or look it up with Find Generation. Map Output URL into Google Drive, Slack, YouTube and more.

Zapier actions time out after about 30 seconds, while video can take minutes — that is why generation and delivery are two steps. Add an Idempotency Key (e.g. the triggering row's ID) so a replayed Zap never pays twice.

Make works with the built-in HTTP and Webhooks apps — nothing to install.

Generate

Module:   HTTP → Make a request
URL:      https://vidova.m7ts.tech/api/v1/generations
Method:   POST
Headers:  Authorization = Bearer vk_live_…
          Content-Type  = application/json
Body type: Raw · Content type: JSON (application/json)
Request content:
{
  "model": "veo-3.1-fast",
  "input": { "prompt": "{{1.prompt}}", "aspect_ratio": "9:16" }
}
Parse response: Yes

Receive the result (recommended)

1. Create a scenario that starts with Webhooks → Custom webhook and copy its URL.
2. Subscribe it once (from an HTTP module you run once, or curl). Keep the returned secret if you want to verify Vidova-Signature.
3. Run the scenario once with a test generation so Make learns the data structure, then map data.outputs[].url.

curl -X POST https://vidova.m7ts.tech/api/v1/webhooks \
  -H "Authorization: Bearer $VIDOVA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://hook.eu1.make.com/abc123","events":["generation.succeeded"],"description":"Make: publish videos"}'

…or poll

Repeater (repeats: 60)
 └ Tools → Sleep (10 s)
 └ HTTP → Make a request: GET https://vidova.m7ts.tech/api/v1/generations/{{2.data.generation.id}}
 └ Filter: status = succeeded OR status = failed → continue, else keep repeating

Remove a subscription with DELETE /api/v1/webhooks/{id} or under Integrations in the app.

Claude, ChatGPT, Cursor and other MCP clients can list models, quote prices and generate through the Vidova MCP server. Setup for each client is in the API reference.

• 401 unauthorized — the key was revoked or mistyped. 403 plan_required — the account is not on Studio.
• 402 insufficient_credits — top up in Plans; nothing was charged.
• No trigger events — the receiving URL must be public https. Check the subscription's last delivery status under Integrations; after 50 failed deliveries in a row it is disabled (re-activate the workflow / Zap to subscribe again).
• Workspace (team) generations are not delivered — webhooks cover your personal space, like the API.