Shotstack Make integrationAutomate Shotstack with Make.
Can your videos render themselves the moment new data shows up? The Shotstack Make integration gives you 4 modules: one instant trigger and three actions. This guide is for marketers and ops people who already use Shotstack, and it walks you from the connection to a working first scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can you automate with the Shotstack Make integration?
The Shotstack Make integration links your Shotstack account to Make, a no-code tool where you build a scenario: an automation made of modules, where each module is one brick such as a trigger or an action. Your data goes in, Shotstack renders a video or an image from a template, and Make carries the result on to your other apps.
Personalized videos from a list. A new record lands in a database app, say the one described on the Airtable Make integration page. Render from Template turns that record into a video built on your Shotstack template, and Get Render Status tells you where the render stands.
Hand-off when a render is done. Watch Renders starts a scenario as soon as Shotstack completes a render, so the next step (sharing the file, updating a record, pinging a teammate) happens without anyone refreshing a dashboard.
Anything the list leaves out. Make an API Call reaches any endpoint of the Shotstack API with the same connection, which covers the requests the three other modules do not.
Know the limits before you start: Make says its own documentation for Shotstack is limited, because little public information about the app exists. Test each module with real data before you trust it. The same app often has an n8n node too; the n8n vs Make comparison lays out how the two tools differ, and the Make review covers Make on its own.
How do you connect Shotstack to Make?
- 01
Add a Shotstack module
Inside your scenario, click the + and search for Shotstack. Pick any of its modules, then click Create a connection. A connection is your Shotstack account linked to Make once, then reused by every Shotstack module you add later.
- 02
Name it and authorize
Give the connection a name if you like, which helps when you run a test account and a live one side by side. Then either authorize Make on the Shotstack page that opens, or paste the key Shotstack gives you, whichever the window asks for.
- 03
Save and check the module
Click Save. The module now shows your connection in its first field, and Make can read what your Shotstack account exposes. If the connection fails, open it again and redo the authorization, or check that the key you pasted is complete.
Your first scenario with Shotstack and Make
GoalWhen a new record appears in another app, Make renders a video from your Shotstack template and checks where the render stands.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that holds your data, such as a sheet or a database, and choose its module that watches for new items.
- 02
Add Render from Template
Click the + on the right of that first module, search for Shotstack and choose Render from Template. Create your connection here if you have not done it yet.
- 03
Map your data into the render
Fill the module fields and map values from the first module into them. Each item that flows between modules is a bundle: here, one bundle is one record, so one record becomes one render.
- 04
Check the render with Get Render Status
Add Get Render Status after the render module and map the render that Render from Template just started. This tells you whether Shotstack has finished the job.
- 05
Test with Run once
Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and confirm the render went through as planned.
- 06
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.
What starts a Shotstack scenario?
1 module starts a scenario when something happens in Shotstack. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Shotstack as soon as it happens.
Watch Renders
Instant triggerIn Make“Triggers when a render is completed.”
Watch Renders wakes your scenario up the moment Shotstack finishes a render, so whatever comes next starts with the completed render in hand, not with a guess about when it might be ready.
What else can Shotstack do in Make?
Shotstack gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Get Render Status
ActionIn Make“Retrieves the render status of a previously processed render.”
You get the current state of a render Shotstack has already processed, so your scenario knows whether the video or image is done before it moves on.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
This one opens the whole Shotstack API to your scenario, reusing the connection you already made, so a request missing from the other modules is still within reach.
Render from Template
ActionIn Make“Creates a video or image from a dynamic template.”
Feed it data and Shotstack produces a video or an image from one of your dynamic templates, which is how a single design turns into many personalized versions.
Need help automating Shotstack with Make?
A person reads every message.
