Opens in a new tab
Guide

What Is the Templater Bot and How Does It Work?

Published November 13, 2026

The Templater Bot is a mode of Templater that lets After Effects work like an unattended operator. You switch it on, it sits in the background and watches a data source, and every time a row is marked ready it versions your template and renders the result. Nobody has to click anything for each video. That single idea explains the Bot, and the rest of this page is the detail you need before you trust it with a real batch.

What the Bot is, and who it is for

Templater comes in three roles, and the Bot is the top one. Templater Rig is where an artist prepares an After Effects project, tagging layers as dynamic and mapping them to a data source. Templater Pro adds batches, so one person can sit at a machine, pick a range of rows, and press a button to process them. The Bot takes the next step and removes the person from the loop. Dataclay’s own description is that the Bot makes Templater behave like a robot operating After Effects for you. Our support pages say the same thing a little more plainly: the Bot is a background process that watches for incoming data and renders video.

The edition split matters because the buttons are tied to it. The Enable Bot button exists only in Templater Bot. Dataclay’s FAQ says Render and Replicate are available only in Pro, Enable Bot only in Bot, and none of them in Rig. If you see Render, Replicate or Enable Bot disabled, check which edition your license is for. The free trial includes every feature, Bot included, so a project can work during the trial and then lose those buttons if someone activates a smaller edition. If you need those functions, you can upgrade your license. Our licensing guide covers how keys and activations work.

Edition comparison

Which edition has which buttons

Render button
Templater ProAvailable
Templater BotAvailable
Replicate button
Templater ProAvailable
Templater BotAvailable
Enable Bot button
Templater ProNot available
Templater BotAvailable only here
Who is at the controls
Templater ProPerson presses a button
Templater BotBackground process, no one clicks

The Bot is the edition that lets you fully automate the workflow.

Who benefits from a Bot? Think about the difference between a person and a pipeline. A person decides when to render. A pipeline decides because something else happened: a form was submitted, a sales row was added, a producer typed a name into a sheet. The Bot is built for the second case. Developers can build a web or mobile front end that writes rows into a data source, and the Bot picks those rows up and turns them into video. In a studio, several people can prepare projects with Rig while the Bot machine does the processing. The Bot is the part that makes Templater a back end instead of a desktop tool.

It follows that the Bot is a poor fit for a few kinds of work. If you make five videos a week and every one needs a designer’s eye on it before it goes out, a person pressing Render in Templater Pro is simpler. If your data lives in a spreadsheet application’s native file format, you have an extra step, because Templater does not read that format directly. The FAQ says to export it to a tab-delimited file first. And if you need one data row to be reviewed and approved before it renders, remember that the Bot has no approval step of its own. It renders what is marked ready. Anything that needs a human decision has to happen before the row gets that value.

How one row travels through the Bot

The Bot runs on a column. Your data source needs a column named render-status, and the Bot’s whole life revolves around the word in that column. Here is the sequence, in the order the Bot performs it.

First you prepare the After Effects project. You apply the Templater Settings effect to the layers that should change, set up a data source, and link the source to the project. Then you enable the Bot. From then on, the Bot checks the source at regular intervals, and the first check after enabling may take a moment to arrive, so a short wait at the start is normal.

On each check, the Bot looks for rows whose render-status is ready. It collects them and changes all of them to queued. This is the step that protects you from double work. A row that says queued is no longer ready, so the next check will not pick it up again. Then the Bot walks through the queued rows one at a time. For the row in hand it sets render-status to processing, versions the target composition with that row’s data, outputs the result, and sets render-status to done. When every collected row is done, the Bot goes back to waiting and checking.

If something goes wrong on a row, the Bot does not stop the world. It writes an error code into render-status instead of done. Two examples from Dataclay’s help pages are ERR::MEDIA, which points to a problem with an asset, and ERR::AFXHOST, which points to an After Effects error. The practical value of this design is that the data source itself becomes your log. You can glance down the column and see which rows finished, which are waiting, and which failed, without opening After Effects at all. Our page on monitoring a Bot queue goes further into reading that column during a run.

Consider a hypothetical example, labeled as one because it is a sketch and not a customer story. A small events team keeps a Google Sheet with one row per speaker. Each row has a name, a title, a photo path and a render-status. A coordinator adds forty rows on Monday morning and types ready into each status cell. The Bot machine, running Templater Bot, notices on its next check, marks rows as queued up to its queue limit, and works through them. By the time the coordinator comes back from a meeting, some cells read done and one reads ERR::MEDIA because a photo path was mistyped. She fixes the path, retypes ready, and the Bot picks up just that row on its next pass. Nobody opened After Effects. That is the loop the Bot exists to run.

There is one behavior worth knowing about formulas. When the Bot updates the render-status column, as of Templater 2.9.5, any formula in a render-status cell is replaced with the formula’s result. Earlier versions overwrote formulas in all the cells of a processed row. If you drive your status cells with a formula, expect it to be flattened to a value once the Bot touches the cell.

What it needs, and the limits you should plan around

Before you enable the Bot, three conditions have to be true. The data source must have a render-status column. At least some of its cells must read ready, or the Bot will have nothing to do. And you should be ready to empty the After Effects disk cache by hand after each job, unless you have already optimized disk caching for Templater. The menu path is Edit, Preferences, Media and Disk Cache, then Empty Cache in the Disk Cache section. If that button is grayed out, the cache is already empty. We have a separate page on optimizing After Effects for the Bot if you want to avoid doing it by hand.

Enabling is one click. Dataclay describes it as putting Templater into a server mode, where it checks your data source at regular intervals until you turn it off. In the Templater panel you press Enable Bot, and the button label changes to Disable Bot. Disabling is the same click in reverse, and it is how you take Templater out of that server mode when you want to use the machine for something else. From that point the Templater interface is frozen except for that button. This is worth planning around. A machine running the Bot is a machine dedicated to the Bot. You cannot use that After Effects session to edit while it runs, so the Bot belongs on its own workstation or server and not on the laptop where you also design. When you press Disable Bot, Templater runs the On Disable shell script registered under Bot Settings in Preferences, if you set one.

Several settings in Preferences, under Bot, govern its behavior. You choose whether the Bot renders, replicates or spot checks, and you may tick more than one. You set how often it checks for new data. The default is half a minute, the floor for Google Sheets is 0.3 minutes, about 18 seconds, and the floor for a JSON source is 0.2 minutes, about 12 seconds. Dataclay warns that setting the interval too low may make After Effects behave unexpectedly, and for Google Sheets there is a second reason, which is that Templater reads and writes through the Google Sheets API and has to respect its rate limits.

You also set how many rows may be queued at once. The default and the maximum are both 20. This cap is a feature, not a flaw. Dataclay’s example is a source with ten thousand rows all marked ready. With the cap at 20, the Bot takes them in batches of twenty, which reduces the memory Templater needs to hold the whole job. If you ever see the message that the Bot can queue a maximum of 20 jobs at once, the FAQ explains that it can follow an upgrade and that resetting After Effects preferences clears it.

Data source support is broad but not unlimited. As of Templater 3.0, the Bot works with Dataclay QUE, Google Sheets, URL feeds, and local JSON and TSV files. A URL feed has one real catch. The Bot cannot update render-status there, because the data source is specific to your own system. If you use a feed, you must register a custom script on the right events to change the status values yourself. Otherwise ready rows may be rendered again. Our page on URL feeds and JSON sources covers the details.

Data source support

What the Bot can and cannot do per source

Data source Supported as of Key limitation
Dataclay QUE Templater 3.0 None noted
Google Sheets Templater 3.0 Must respect API rate limits; floor is 0.3 minutes
URL feeds Templater 3.0 Bot cannot write render-status back; custom scripts required
Local JSON and TSV files Templater 3.0 Floor interval is 0.2 minutes for JSON
Excel files are not read directly; export to a tab-delimited file first.

Before you start

Have these ready before enabling the Bot

  • Add a render-status column to your data source
  • Mark at least some cells ready so the Bot has rows to process
  • Prepare to empty the After Effects disk cache manually after each job
  • Dedicate a separate machine or workstation to the Bot
  • Register a custom script to update status values if you use a URL feed
From the point you press Enable Bot, the Templater interface is frozen except for that button.

Two more facts matter once volume grows. You can run more than one Bot against the same spreadsheet, on machines that sit in different places, because a Google Sheets document lives in the cloud. When you do, you give each Bot a name and add a bot column to the data so each knows which rows are its own. A single Bot on a single source needs neither. Our walkthrough of one Bot or many is the place to go for that setup. And the Bot has a command line interface, so you can launch and control it from scripts. Dataclay provides open-source launcher tools to get you started, and the command line is available in the free trial as well. The related error to remember is “Unable to find a Window Constructor,” which appears when After Effects is not running in the foreground, and the fix is a ui argument at launch.

The Bot also assumes your project is ready. It does not rescue a badly built template. A problem with an asset, for example, shows up as an ERR::MEDIA row, not a video. That is why spot checks before a big run are worth the time. A quick pass through preview and spot check modes shows you how the data lands on a handful of rows before the Bot spends hours on thousands.

So is the Bot the right choice? If your videos are triggered by data and not by a person, yes. Dataclay describes the Bot as the edition that lets you fully automate the workflow. If your volume is small and every video needs review, Templater Pro with a human at the keyboard is simpler. If you need jobs managed as campaigns across machines, look at Que, which works alongside Templater and organizes jobs into campaigns with satellite machines. Our comparison of how Que and Templater work together lays out where one ends and the other begins.

The bottom line is short. The Bot is a loop that reads a status column, renders what is ready, and writes the result back. Give it a clean template, a dedicated machine, a render-status column you trust, and a plan for the URL feed catch if you use one. Do that and it will keep working while you are away from the desk, which is the point of it.

Here are the questions worth answering before you enable the Bot for the first time.

Frequently Asked Questions

What does the Templater Bot actually do?

The Bot is a background process in Templater Bot that checks a data source for rows with a render-status of ready. It changes them to queued, then to processing, versions your target composition with each row’s data, outputs the video, and sets the status to done. If a row fails, it writes an error code such as ERR::MEDIA or ERR::AFXHOST instead. After the batch, it keeps checking for new rows.

Which data sources can the Bot read?

As of Templater 3.0, the Bot supports Dataclay QUE, Google Sheets, URL feeds, and local JSON and TSV files. Excel files are not read directly, so you export them to a tab-delimited file first. With a URL feed, the Bot cannot write render-status back, so you need to register custom scripts that update the status values at the right events, or ready rows may render again.

How often does the Bot check for new data?

You set the interval in Preferences under Bot. The default is 0.5 minutes, or 30 seconds. For Google Sheets the shortest allowed interval is 0.3 minutes, about 18 seconds, because Templater has to respect the Google Sheets API rate limits. For JSON sources the shortest is 0.2 minutes, about 12 seconds. Dataclay warns that setting the value too low may make After Effects behave unexpectedly.

Can more than one Bot read the same spreadsheet?

Yes. Several machines can read new rows from one Google Sheet, including machines in different places, because the document is stored in the cloud. Give each Bot a name in Preferences and add a bot column to the data so each Bot knows which rows belong to it. If you only use one Bot per data source, you do not need a name or a bot column.

Why are the Enable Bot, Render and Replicate buttons disabled?

Render and Replicate are available in Templater Pro, and Enable Bot is available in Templater Bot. None of them are available in Templater Rig. The free trial includes all features, so the buttons can disappear if you activate a smaller edition after the trial ends. If you need those functions, you can upgrade your license to the edition that includes them.

Do I need to do anything to the After Effects disk cache?

Dataclay says to be prepared to empty the disk cache manually after each job unless you have optimized After Effects disk caching for Templater. In After Effects, go to Edit, Preferences, Media and Disk Cache, then click Empty Cache in the Disk Cache section. If the button is disabled, the cache is already empty.

Does the Bot have a command line interface?

Yes. The Bot provides a command line interface for controlling Templater as it works with After Effects, and Dataclay provides open-source tools to help you start. The command line is available in the free trial. If you see the error “Unable to find a Window Constructor” while monitoring a data source, After Effects is not running in the foreground, and adding a ui argument when you launch the Bot is the fix.

Leave the first comment

Sign up

Stay up to date with Datclay's newsletter. We won't spam your inbox.

Newsletter Signup
Name
Name
First
Last

By submitting your email, you agree to our Terms and Privacy Policy. You can opt out at any time.