Make integration
Auto captions in Make
Burn styled, animated captions into a video from a Make scenario with one HTTP module: send the video link, get back the captioned MP4 plus SRT and VTT. No FFmpeg, no custom app. 5 credits (about $0.05) per minute of video.
The scenario
- Trigger (video link)→
- HTTP: caption the video→
- HTTP: download a file→
- Drive, S3, YouTube…
The API holds the request open until the captions are burned (up to 50 seconds), so short clips need no loop. Longer videos use a Make webhook instead; see step 5. Failed jobs are refunded.
HTTP > Make a request
Fill the module like this (HTTP app Version 4; labels checked November 13, 2026). The key lives in a Make keychain, so it stays out of headers and shared blueprints.
- URL
https://api.awesomevideoeditor.com/v1/captions?via=make- Method
POST- Authentication type
API key- Credentials
Key: Bearer av_live_... API key placement: In the header API key parameter name: Authorization Allowed service origins: https://api.awesomevideoeditor.com- Body content type
application/JSON- Body input method
JSON string- Body content
{ "sourceUrl": "{{1.videoUrl}}", "preset": "builtin:karaoke", "platform": "tiktok", "maxCredits": 50, "waitSeconds": 50 }- Parse response
Yes- Timeout
60- Return error if HTTP request fails
Yes (optional: stops the scenario on a 4xx/5xx, such as 402 when the balance is short)- HTTP v3 (legacy)
Same request: header Authorization: Bearer av_live_..., Body type Raw, Content type JSON (application/json), Request content = the JSON above.
Set it up
1. Get an API key
Create a key at awesomevideoeditor.com/account, or from a terminal with no sign-up. While the trial runs, a new self-serve key can claim a few free welcome credits (see /facts). A short balance answers 402 with a checkout link and nothing is charged.
curl -X POST https://api.awesomevideoeditor.com/v1/keys/anonymous -H "Content-Type: application/json" -d '{"name":"make"}'2. Add an HTTP > Make a request module
After your trigger (Google Drive Watch files, a form, a Google Sheets row, or Tools > Set variable for a first test), add HTTP > Make a request (Version 4) and fill it as below. Put the key in a keychain under Credentials, not in Headers. waitSeconds: 50 makes the API answer with the finished job, so one module is enough for short clips; Timeout 60 gives it room. Replace {{1.videoUrl}} with the link from your trigger.
3. Run it once
Click Run once. The module returns 200 with status succeeded, result.url (the captioned MP4), the SRT and VTT text in result.files, the language and creditsCharged. Running it once also lets Make learn the response, so the fields become mappable.
4. Save the video
Add HTTP > Download a file (Authentication type: No authentication; in HTTP v3 it is Get a file) with URL {{2.data.result.url}}, then Google Drive Upload a file, Dropbox, S3, YouTube or Slack. Result links are signed and expire after 24 hours, so download them in the same run. For the SRT text: {{first(map(2.data.result.files; "text"; "name"; "srt"))}}.
URL: {{2.data.result.url}}5. Long videos: let the API call a Make webhook
If status is still queued or running when the 50 s window ends (longer videos), don't poll in a loop. Make a second scenario that starts with Webhooks > Custom webhook, copy its URL, and send it as webhookUrl instead of waitSeconds. The first scenario returns at once with 202 and the job id; when the job ends, AwesomeVideo POSTs it to the webhook. In the second scenario, read the id from {{1.job.id}} and fetch GET /v1/jobs/{id} with your key before using the result, so a forged call can't inject a link.
{ "sourceUrl": "{{1.videoUrl}}", "preset": "builtin:karaoke", "platform": "tiktok", "maxCredits": 50, "webhookUrl": "https://hook.eu1.make.com/your-webhook-id" }
What the module sends and gets back
The exact request from the module settings above and the real responses for the 8-second CC0 sample (trimmed; run on November 12, 2026).
POST https://api.awesomevideoeditor.com/v1/captions?via=make
Authorization: Bearer av_live_...
Content-Type: application/json
{
"sourceUrl": "https://awesomevideoeditor.com/samples/cc0-interview-es.mp4",
"preset": "builtin:karaoke",
"platform": "tiktok",
"maxCredits": 50,
"waitSeconds": 50
}200 (answered after 27 s)
{
"id": "e12b7158-...",
"kind": "caption",
"status": "succeeded",
"step": "done",
"progress": 100,
"audioSeconds": 8,
"creditsCharged": 2,
"result": {
"url": "https://api.awesomevideoeditor.com/v1/jobs/e12b7158-.../result?...",
"language": "es",
"platform": "tiktok",
"files": [
{ "name": "mp4", "contentType": "video/mp4", "url": "..." },
{ "name": "srt", "text": "1\n00:00:00,000 --> 00:00:02,380\nen la escuela es súper diferente al mundo\n..." },
{ "name": "vtt", "text": "WEBVTT\n\n00:00:00.000 --> 00:00:02.380\n..." },
{ "name": "json", "text": "{ \"language\": \"es\", \"cues\": [...] }" }
]
}
}Webhook version
202 (with "webhookUrl" instead of "waitSeconds")
{
"id": "ef5962ad-...",
"status": "queued",
"steps": ["transcribe", "burn", "finalize"],
"eta_seconds": 17,
"notify": { "webhookUrl": "https://hook.eu1.make.com/...", "delivery": null }
}POST https://hook.eu1.make.com/... (when the job ends)
{
"id": "evt_ef5962ad-..._succeeded",
"type": "job.succeeded",
"created": 1794515133,
"job": { "id": "ef5962ad-...", "status": "succeeded", "result": { "url": "...", "files": [...] } }
}Every job view also has step, progress (0-100), eta_seconds and pollAfterSeconds. Webhook posts carry webhook-id, webhook-timestamp and webhook-signature. Full schema: OpenAPI.
Questions
- Do I need FFmpeg, a custom app or a paid Make plan?
- No. The recipe uses Make's built-in HTTP module (and Webhooks for long videos). Transcription and the burn run on the AwesomeVideo server, so there is nothing to install and no FFmpeg in the scenario.
- How much does it cost per video?
- 5 credits per minute of audio (1 to transcribe, 4 to burn), 7 with translateTo. 1 credit is 1 US cent, so about $0.05 per minute, billed per second with each step rounded up to the next cent. The 8-second sample costs 2 credits. Failed jobs are refunded. Make counts its own operations separately.
- Which video links work?
- Any public https link to the file: a direct MP4 or MOV URL, or a Google Drive, Dropbox or OneDrive share link. YouTube, TikTok and Instagram page links are refused with charged: false; download the file first and upload it with POST /v1/uploads/url.
- What if the video is longer than the wait window?
- With waitSeconds the API answers within 50 seconds. If the job is still running you get status running and the id. Use the webhook version instead: send webhookUrl (a Make custom webhook) and the finished job is POSTed to it, signed with webhook-signature. Polling GET /v1/jobs/{id} with Repeater and Sleep also works, but costs more operations.
- Is there a version for n8n or Zapier?
- n8n has an importable workflow at awesomevideoeditor.com/integrations/n8n. In Zapier the same two calls work with Webhooks by Zapier (a premium Zapier app): POST /v1/captions, then GET /v1/jobs/{id}.
More
- n8n workflow (importable)awesomevideoeditor.com/integrations/n8n
- Caption styles with demosawesomevideoeditor.com/styles
- Caption API (curl, prices)awesomevideoeditor.com/api/captions
- Recipes: curl, MCP, Pythonawesomevideoeditor.com/agents
- Docs for LLMs (llms.txt)api.awesomevideoeditor.com/llms.txt
- Pricingawesomevideoeditor.com/pricing
Make is a trademark of Celonis; this is an independent integration, not an official Make app. Sample clip: “Entrevista Maricarmen Canales - TECMTY” by NachoCHOCO, CC0, via Wikimedia Commons.