Event scripts are scripts that listen for events that Templater broadcasts. These scripts, or any command for that matter, "hook" into Templater's processes allowing you to extend its automation capability. Dataclay's code repository on GitHub contains sample scripts intended to be executed when Templater broadcasts specific events.
Frequently Asked Questions about Event Scripts
Why use Event Scripts?
Event scripts are useful when you want to seamlessly integrate Templater into your existing application. For example, in a production scenario, you can merge, transcode, or compress Templater's output—all of which can be accomplished calling a command line application like ffmpeg within a script. You can also automate publishing output to a specific destination like an FTP site, or your YouTube, Vimeo, or JWPlatform account. You could also script notifications for when a batch of renders completes—email, text message, etc. Ultimately, you gain a great deal of flexibility with Templater by having the ability to hook into its processes.
When should I use event scripts?
You should use them when you need to do something with Templater's output or have Templater's functions integrate with an existing automated workflow.
What information from Templater can my scripts make use of?
You can pass information from Templater and After Effects to event scripts. To access the information, use command line argument variables throughout your code. Learn more about this in Passing Job Details to Event Scripts.
What languages can I write event scripts in?
You can write event scripts in any language available in your system's environment.
Do event scripts write to log files?
Event scripts do not log to a file by default, but from within the event script, you can write code to redirect the standard output (stdout) and standard error (stderr) to a log file.