Templater does not talk to Zapier directly. QUE does, and QUE feeds Templater. That one sentence is the whole architecture of this setup, and once you see it, everything else is a matter of deciding which event in which app should trigger a video.
This page is for the person who already has a tool where events happen, such as a form that gets filled in, a sheet that gets a new row, or a CRM that changes a status, and who wants a finished video to come out the other side without writing code. We will explain what the connection is, how to think about a first automation, what we do not claim, and when you should skip Zapier for something plainer.
The route from an app to a video
Start with the pieces, because the names matter. Templater is the After Effects plugin that takes a rigged composition and a data source and produces videos. QUE is our JSON-based data source and API, built to work with Templater. Zapier is a separate service that connects web apps to each other.
QUE has a built-in Zapier integration. Our QUE page describes it this way: use the built-in Zapier integration to connect to more than 5,000 apps with no coding necessary. So the route is app, then Zapier, then QUE, then a computer running After Effects and Templater, then a video. Zapier is the part that connects your other apps. QUE is the part that holds the data Templater reads.
Where each piece sits
In QUE, four components make up a video project. An Autograf is a video composition template with layers rigged to accept dynamic data. A Job is the JSON object that holds the data for one video based on that Autograf. A Campaign is a collection of jobs. A Satellite is a computer running After Effects and Templater that processes jobs and produces the output.
The goal is for something that happens in another app to end up in QUE as a Job. A Satellite then picks the job up and renders it. The guide named below covers how Zapier does the first part. You do not need to know JSON to use QUE at all, because information can also be entered by hand in the QUE Dash.
Why QUE sits in the middle
You might wonder why the route is not simply Zapier to Templater. The reason is what each one is good at. Templater reads a data source when it runs on a machine with After Effects. It needs something durable to read from. QUE is that thing, hosted in the cloud, built to receive data from anywhere through exposed API endpoints, whether the source is a mobile app, a web app, or a voice app. Zapier is a very good way to push data to such an endpoint without a developer.
QUE is also where you can see what is happening. Its dashboard shows each job’s status and the utilization of rendering machines, so you are not guessing whether the thing you triggered has finished.
Thinking through your first automation
Our own documentation on this subject lives in a guide titled “Using the QUE API with Zapier,” and our blog has a post called Zapier connects QUE to all the software you love. Use those for the click-by-click setup, because the screens inside Zapier change and we would rather you read the current steps. What follows is the thinking you do before you open either of them. It is general practice for this kind of connection, not a list of specific Zapier features.
Name the event and the video
Write one sentence in this shape. When this happens in that app, make this video. For instance, when a new row is added to a signup sheet, make a welcome video with the person’s name and the program they chose. Or when a deal closes, make a thank-you video for that customer. If you cannot finish the sentence, the automation is not ready to build.
Then list the pieces of information the video needs. Each one will map to a rigged layer in the template, and each one must exist in the event that Zapier sees. If the template wants a first name and a photo link and the form only collects an email, you have found the problem before spending any time. Our post on Jotform and QUE Meter is a good example of a form feeding on-demand videos.
Prepare the template for unknown data
Automation changes who sees the data first. In a manual batch, you look at the sheet and preview the worst row. In an automated flow, nobody looks at row four hundred before it renders. So the template has to be defensive. Use layout rules so text blocks adjust when a name is long. Use Time Sculpting so footage of different durations still fits. Decide what shows up when a field is empty. Then test with strange input on purpose, a very long name, a name with an apostrophe, and a missing photo, before you switch the automation on.
Templater reads text exactly as it appears, so commas, quotes, apostrophes, and new lines are accepted, and characters from any language work if the fonts have the glyphs. That helps, because forms let people type anything.
Check the rendering machine
Something has to render. A Satellite is a computer running Adobe After Effects and Templater, and it has to be on and ready when a job arrives. Any fonts, plugins, and assets the template needs must exist on it. QUE does not load balance jobs between satellites, so if you run more than one, you assign jobs to specific satellites yourself and verify each has what it needs. Templater Bot is the edition built for this kind of unattended work. It operates After Effects for you and starts renders when new data arrives.
If you plan to run in the cloud, you can run Templater on Windows Server machines in an environment such as AWS with no special Dataclay license. After Effects has to be installed and running there, and Adobe’s standard license agreement does not allow it on a server, so you must arrange the right license with Adobe.
Decide where the finished video goes
A render is not a delivery. If the video is for a customer, something has to get it to them. Templater can run scripts hooked into its events, and the scripts we describe in our FAQ include uploading to a streaming provider, returning the video’s URL to the data source, and sending an email or SMS when an upload succeeds. If you prefer not to write scripts, our custom development team can build them. Projector is the other route. It automates distribution to supported platforms and can write metadata from the platform back to your data source.
A worked example: a signup form that sends a welcome video
Here is the thought experiment, with no numbers on purpose. A training company has a signup form. When someone registers for a course, the company wants a short welcome video that shows the person’s first name, the course title, and the start date. A motion designer has already built the composition and rigged it with Templater, so those three fields are dynamic.
The sentence is simple. When a person submits the form, make a welcome video. The three fields on the form map to the three rigged layers. Zapier watches the form and passes the answers to QUE. QUE holds them as a job. A Satellite, which is a machine running After Effects and Templater with the template and its fonts installed, picks the job up and renders. A script hooked into a Templater event then uploads the finished file and writes its address back, and the company’s email tool reads that address and sends the message.
Nobody on the production team touches any step after the setup. That is the appeal. It is also why every step needs a test, because a failure at any link produces a silence, not a loud error. The person simply never receives a video.
What tends to go wrong
These points are general practice, drawn from how any chained automation behaves, and not a list of known Zapier problems.
The first is a field that arrives empty. A required field on the form and a required layer in the template do not always line up. Decide in advance what the video should show when a value is missing, and design the template to handle it, because Templater will insert exactly what it receives.
The second is a render machine that is off, asleep, or missing a font. The job sits there. Our FAQ lists the symptoms for missing dependencies, and After Effects reports render queue items as “Failed at N/A” when it cannot find an asset, footage file, or font where the project expects it. Put the fonts and assets in a fixed place and keep the project presets that store the data source, footage folder, and output folder.
The third is a quiet change somewhere upstream. Someone renames a field on the form, the mapping in the connection no longer matches, and the videos come out with the wrong words or none. Keep a short note of which form field feeds which template field, and re-run a test event after any change to the form.
The fourth is volume. A form that suddenly receives a rush of responses will put many jobs into QUE at once. Templater queues large workloads into manageable batches so a machine is not overloaded, and you can add machines running Bot to share the work, but plan the capacity before the rush, not during it. Two machines take half the time of one, and three take a third.
Who owns the automation
Give it one owner. The person who owns it knows which form feeds which template, which machine renders, and where the finished files go. When something fails at two in the morning, there should be a name attached. A chain of connected tools is only as reliable as the person who checks it, and the simplest check is a calendar reminder to run one test event every so often and watch it all the way through to the inbox.
Test small, then widen
Use one real event, watch it travel, and check the output. Then ten. The QUE free version is limited to 50 jobs by default, which makes it a reasonable place to prove the whole chain before committing. Look at the job in the QUE Dash, confirm which Satellite picked it up, open the finished video, and only then let real traffic in.
What we do not claim, and when to use something else
We want to be exact about what this page can and cannot tell you.
We do not publish here a list of the triggers and actions Zapier offers for QUE. Our product page gives the headline, the built-in integration and the number of apps it can reach, and the guide named above gives the steps. If you need a specific trigger from a specific app, check the current documentation before you plan around it. We also do not state how fast an automated video arrives, because it depends on the template, the output, and the render machine, and any number we gave you would be a guess. The pre-flight advice from our FAQ applies. Render one video that resembles the others on a machine like your production machine to see how long one takes.
Cases where Zapier is the wrong tool
If your data already lives in one Google Sheet and a person starts a batch a few times a week, you do not need Zapier. Connect the sheet straight to Templater, as in our Google Sheets walkthrough, and press Render or let Bot watch it. Adding an automation service to that is extra moving parts for no gain.
If you are a developer building your own app, the QUE API may be the better fit than Zapier. Our post on the QUE API describes it as a way to build apps that produce dynamic video, such as one where a customer controls the final video based on information they enter. You do not have to be a developer to use the API, but if you are one, calling it directly gives you control that a no-code connector does not.
If you need to use a Google Sheet and QUE at the same time, that is supported. Set QUE as the Templater data source and integrate the sheet either directly through the QUE API or through QUE’s built-in Zapier integration. That is a legitimate use of Zapier, particularly when people want to keep editing in a sheet while production runs from QUE.
Cost and licensing, without numbers
Zapier is a separate service with its own plans, which we do not control or describe. For QUE, we offer a free version to try and subscriptions to scale up. QUE Meter is a credit-based entry option, and our post introducing QUE Meter explains it. One practical difference is that when Templater runs on QUE Meter, the computer must always be connected to the internet to track credit use. Traditional Pro and Bot subscriptions do not need that constant connection. For pricing, see our pricing page or the licensing guide.
The bottom line
Use Zapier when an event in another app should produce a video and nobody on your team wants to write code. Remember the route. Zapier feeds QUE, QUE holds the jobs, Templater on a Satellite renders them. Build the sentence first, prepare the template for the worst input, prove the chain with a handful of real jobs, and keep a person looking at the first batch. If your process is simpler than that, skip the extra layer and connect the sheet.
Frequently Asked Questions
Here is what people ask us when they are deciding whether to connect their apps to video.
Does Templater connect to Zapier directly?
No. QUE has the built-in Zapier integration, and QUE is a data source for Templater. The route runs from your app through Zapier into QUE, and a machine running After Effects and Templater renders the job. Our documentation includes a guide titled Using the QUE API with Zapier that covers the setup.
Do I need to know how to code to use Zapier with QUE?
No. Our QUE page says the built-in Zapier integration connects to more than 5,000 apps with no coding necessary, and that you do not have to know JSON to use QUE. You do need a template that has been rigged in After Effects with Templater, either one you build or an Autograf we provide.
What edition of Templater do I need for an automated flow?
Templater Bot is built for unattended work. It checks for new data and starts renders on its own, and it can take data pushed in by command line. Pro suits a person who starts each batch. Rig prepares and previews projects but cannot batch output, so it is not enough for an automated flow.
Can I use Google Sheets and QUE at the same time?
Yes. Set QUE as the Templater data source, then connect the Google Sheet to QUE through the QUE API or through QUE’s built-in Zapier integration. People can keep working in the sheet while QUE manages the jobs, the dashboard, and the satellites.
How do I send the finished video to someone?
Rendering and delivery are separate steps. Templater event scripts can upload the finished video to a streaming provider, return its URL to your data source, or send an email or SMS when the upload succeeds. Projector can also automate distribution to supported platforms and write platform metadata back to your data source.
Is there a free way to test this?
Yes. Templater has a 30-day free trial with all features, and QUE has a free version, limited to 50 jobs by default. Use them to prove one complete event-to-video chain with real data before you rely on it.
