Bubble + ReelSDK $0.03 per output minute, first $0.50 free

Video editing in Bubble apps

Bubble workflows stop after 300 seconds, slow API calls get retried after 30 s, and no action can run ffmpeg. ReelSDK burns in captions for $0.03 per output minute, so an 11-second clip costs about half a cent and comes back in about 13 seconds, from one API Connector call that keeps your key on Bubble's server.

  • Private key in header, never in the page
  • Captions burned in, plus SRT, VTT and ASS files
  • Bubble's 30 s retry gets the first job, not a second charge
What a render call from a Bubble workflow runs into

Workflows that take more than 300 seconds (5 minutes) will time out.

If an API call takes longer than 30 seconds to complete, Bubble will automatically retry this call.

400 INVALID_REQUEST "video_url: must be an http(s) URL" (a Bubble file URL that starts with //)

Sources: Bubble hard limits, Bubble: the API Connector

The same job as one call to ReelSDK

curl "https://api.reelsdk.com/v1/captions?wait=25" \
  -H "Authorization: Bearer $REELSDK_KEY" \
  --json '{
    "video_url": "https://api.reelsdk.com/f/lib/demo/clip.mp4",
    "style": "bold",
    "prompt": "Seville, Plaza de España, Giralda, flamenco, tapas"
  }'
200 in about 13 seconds: the 1080x1920 clip with bold captions, plus a transcript and SRT, VTT and ASS filesTry it

Why ffmpeg breaks here

No binaries, 300 seconds, a retry at 30 s

A Bubble app is workflows and plugins, and neither gives you a shell. Server-side plugin actions run JavaScript on Bubble's servers, but Bubble documents no way to ship or start a program there, and every workflow stops after 300 seconds. The API Connector is the part that fits: its calls go out from Bubble's server, and a collection set to Private key in header keeps the key out of every page.

Two Bubble details shape the call. A call that takes more than 30 s gets retried, so ask for ?wait=25 and send an Idempotency-Key: a retry with the same key and body gets the first job back instead of a second render on your bill. And Bubble file URLs start with //, which ReelSDK turns away with a 400, so put https: in front of the file's URL.

Captions cost $0.03 per output minute, so an 11-second clip costs about half a cent. Failed jobs are free, there's no subscription and pricing lists the other job types. Here is a captioned clip.

Bubble next to ReelSDK

Bubble next to ReelSDK
TopicBubbleReelSDK
Running ffmpegNo documented way to start a programffmpeg 8.1 behind /v1/captions and /v1/ffmpeg
Time300 s per workflowJobs up to 10 min, ?wait= up to 300 s
Slow callsRetried after 30 sAn Idempotency-Key returns the first job
Responses50 MB per API Connector responseJSON with links, the video stays on ReelSDK
KeysPrivate key in header on the collectionAuthorization: Bearer with that key

Bubble limits from Bubble hard limits, checked November 2026.

Set it up

One collection, two calls, two backend workflows

You need a Bubble app with the API Connector plugin and a ReelSDK key. The key goes in the collection's private field, so no page ever loads it, and the calls run from backend workflows.

  1. Add a ReelSDK collection to the API Connector

    Add an API named ReelSDK and set Authentication to Private key in header. Bubble's docs warn that with None or self-handled, values marked Private are exposed to anyone, so the key goes here and nowhere else.

    API Connector: ReelSDK
    Authentication
    Private key in header
    Key name
    Authorization
    Private key
    Bearer rsdk_live_...
    Shared header
    Content-Type: application/json
  2. Add the Add captions and Get job calls

    Add captions: Use as Action, POST https://api.reelsdk.com/v1/captions?wait=25, a header Idempotency-Key with a dynamic value, and the body below. Untick Private on video_url and prompt so workflows can fill them. Get job: Use as Action, GET https://api.reelsdk.com/v1/jobs/[id]?wait=25. Initialize both with the hosted demo clip so Bubble learns the response shape.

    Add captions body (JSON)
    {
      "video_url": "<video_url>",
      "style": "bold",
      "prompt": "<prompt>"
    }
    
  3. Render from a backend workflow

    Make a backend workflow render_captions with a Render parameter. It runs Add captions with video_url set to https: plus the file's URL and Idempotency-Key set to the Render's unique id, then saves the job's id, status and outputs video. Start it from the page with Schedule API workflow, after a check on how many renders the user started today: anything a page can trigger, a user can trigger in a loop, and every run bills your key.

  4. Collect slow renders

    If the status is still queued or running, schedule check_render 30 seconds later. It runs Get job, saves the result when the status is succeeded and schedules itself again while it is queued or running. A failed render answers 422 or 500, which Bubble treats as an error: tick Include errors in response and allow workflow actions to continue on both calls, initialize them again, and mark the Render failed when a call returned an error. Output links last 7 days, so copy the mp4 into your own storage if you keep it.

FAQ

Video on Bubble, answered

Can Bubble run ffmpeg?

Not inside your app. No workflow action starts a program, and server-side plugin actions run JavaScript on Bubble's servers with no documented way to ship a binary. Send the work to ReelSDK from the API Connector instead: captions, slideshows and raw ffmpeg run on a fresh machine per job.

Why wait 25 seconds and not longer?

Bubble retries an API call that takes more than 30 seconds. With ?wait=25 the call returns first, with the finished video or with status running, and the Idempotency-Key makes a retry return the same job instead of starting a second one.

Is the API key safe in the API Connector?

Yes, in a collection set to Private key in header: the call goes out from Bubble's server and the key never reaches the browser. Don't paste it into a call's header or body, and keep the render in a backend workflow so users can't fire it at will.

Why does ReelSDK say video_url must be an http(s) URL?

Bubble file URLs start with //, without the scheme. Put https: in front of the file's URL when you fill the parameter and the same file works.

What does it cost?

Captions and slideshows are $0.03 per output minute, raw ffmpeg $0.02 per compute minute, and the first $0.50 is free. Failed jobs are free, and each key runs 3 jobs at once and 500 a day.

All integrations

Ready to build?

Ship video from your app today

Your first $0.50 is free, and one key covers every endpoint.

Moonlit lake with a lit cabin under the mountains