Trigger video generation from Zapier: from form submission to finished Seedance clip

To trigger Seedance video generation from Zapier, connect a form submission trigger to a Webhooks by Zapier action that sends a POST request to https://relaydance.com/v1/video/generations with your model, prompt, and seconds. Add an Authorization: Bearer YOUR_API_KEY header, then poll GET /v1/video/generations/{task_id} or set metadata.callback_url for a webhook. Because RelayDance is OpenAI-compatible, no BytePlus enterprise account or KYC is required.

How the Zapier flow maps to the RelayDance API

The flow moves from a form trigger to a POST request that submits a Seedance task. In Zapier, a form app (such as Google Forms or Typeform) captures the prompt text, then a Webhooks by Zapier action posts to /v1/video/generations. According to the official relaydance.com/docs guidance, 「Set base_url to https://relaydance.com/v1 and keep your OpenAI SDK」, which means the same base URL works whether you call from Zapier or an SDK. The request body carries model, prompt, and seconds, plus optional metadata (ratio, resolution, generate_audio, callback_url). See relaydance.com/docs for the full field reference.

Numbered steps to build the Zap

Building the Zap takes five configuration steps inside Zapier.

1. Create an API key at https://relaydance.com/console and store it in Zapier as a secret.
2. Add your form app as the trigger and map the submitted prompt field.
3. Add a Webhooks by Zapier POST action to https://relaydance.com/v1/video/generations with the header Authorization: Bearer YOUR_API_KEY.
4. In the JSON body, set model, prompt, and seconds; clips can run up to 15 seconds, and you may include reference media in metadata.content[] cited as @image1 to @imageN.
5. Either poll GET /v1/video/generations/{task_id} until status is succeeded or failed, or set metadata.callback_url so the final state is POSTed to your server.

Model pricing to plan your Zap budget

Per-second rates determine the cost of each clip your Zap produces. The table below lists current Seedance rates from relaydance.com/models; billing is pay-as-you-go per generated video.

For image steps, gpt-image-2 output is free and only input is billed, with image-to-image from about CNY 0.035.

Error handling and billing safety in automated Zaps

Automated Zaps are protected from charges on failed tasks. When a request errors out, RelayDance does not bill it: according to the official relaydance.com docs, 「Failed or errored requests are never billed」. This matters for Zapier, where retries can fire on transient issues. Configure your Zap to check the polled status field and branch on succeeded or failed before downstream actions run. The result payload contains the video url when the status is succeeded. Payments are handled through USDT and Stripe card, and billing remains pay-as-you-go per generated video, so idle Zaps do not accrue cost.

FAQ

Which endpoint does the Zap post to? The Webhooks by Zapier action posts to https://relaydance.com/v1/video/generations with model, prompt, and seconds.

Am I charged if a generation fails inside the Zap? No. Failed or errored requests are never billed, per relaydance.com.

How do I get the finished clip back into Zapier? Poll GET /v1/video/generations/{task_id} until status is succeeded and read the video url, or set metadata.callback_url to receive the final state by webhook.