Skip to content
Integration

CAMB.AI integrations and automation

Describe what should happen in CAMB.AI, and when, in plain words. Whenever builds the workflow and runs it on a schedule, on a webhook, or when another app sends an event.

Connection requirements, provider permissions and optional AI usage apply. Read the runtime limits.

Start for freeNo credit card requiredAI building has weekly usage limits.

CAMB.AI on Whenever

About CAMB.AI

CAMB.AI provides hosted APIs for multilingual dubbing, speech synthesis, transcription, translation, voice cloning, and audio generation.

How Whenever connects

Through its API, using the credentials and permissions required by the provider.

Build it from your AI client

Connect Claude, Cursor or Codex to the Whenever MCP server and your coding agent can build and deploy the CAMB.AI workflow. It runs on Whenever afterwards, on its schedule or webhook, with the chat closed.

Set up the Whenever MCP server

Plan your CAMB.AI workflow

CAMB.AI is used to localise audio and video: dubbing a video into other languages, turning text into speech in a chosen voice, translating text, and transcribing speech. The appeal for automation is volume. A training team publishing a new video each week, or a podcast that wants a Spanish version of every episode, can start the job when the source is ready rather than uploading files by hand.

Almost every CAMB.AI endpoint follows the same asynchronous pattern, and briefs need to account for it. You create a task, for example an end-to-end dubbing task with a video URL, a source language and one or more target languages, and receive a task_id. You then check that task’s status, which moves from PENDING to SUCCESS or ERROR (failures can also show TIMEOUT or PAYMENT_REQUIRED); on success it gives you a run_id. The matching result endpoint, such as Get Dubbing Result, takes the run_id and returns the output, and a separate endpoint returns the dubbing transcript. A workflow that expects the dubbed file in the first response will not find it.

Requests authenticate with an API key in an x-api-key header, created in CAMB.AI Studio. Languages are given as locale tags such as en-us and es-es, checked against the source-languages and target-languages endpoints; older numeric ids still work but are deprecated. The video_url can be a YouTube link, a publicly shared Google Drive file, or any direct media link that needs no sign-in.

CAMB.AI also offers audio separation and transcription endpoints, and the dubbing request accepts an optional source transcript as SRT. Generated speech and translation can vary between runs, so treat the output as a draft for a native speaker to review before it is published, and fetch the transcript for that review.

CAMB.AI workflow examples

Authored starter briefs to configure with your accounts, not preconfigured workflows.

Spanish dub for each new training video

Handles the task, status and run-result steps explicitly.

Build this workflow

Narrate the weekly announcement

Text-to-speech from a fixed voice, stored for a reviewer.

Build this workflow

Translate product release notes

Uses the translation task for short text, with a person approving before publishing.

Build this workflow

Related apps for your workflows

All integrations

CAMB.AI FAQs

Why doesn’t the CAMB.AI API return the dubbed video immediately?

Most CAMB.AI APIs are asynchronous. Creating a task returns a task_id; once its status is SUCCESS you get a run_id, and the result endpoint for that run returns the output.

How do I specify languages in CAMB.AI requests?

Use locale tags such as en-us or es-es, checked against the source-languages and target-languages endpoints. Numeric ids still work but are deprecated.

How is the CAMB.AI API authenticated?

With an API key from CAMB.AI Studio sent in the x-api-key header on each request.

Can CAMB.AI dub a video stored in my private drive?

Only if the file is publicly accessible. The video_url can be a YouTube URL, a public Google Drive link, or a direct media link that needs no authentication.

Is the dubbed output ready to publish?

Treat it as a draft. Generated voices and translations can vary between runs, so have a fluent reviewer check it against the transcript before release.

Agents should build your automations, not be them

Describe your first workflow in plain words. One stays live for free, no credit card.

No credit card required