ActionBannerbearUpdated September 2026
What Bannerbear templates exist in this workspace?
Short answer: You can list templates in Bannerbear by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Bannerbear List Templates action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Sample request
{}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Templates.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Templates.
What does the List Templates action do in Bannerbear?
Returns every image/video template in the connected Bannerbear project with name, preview URL, and configured layer set. The lookup for populating template-pickers in workflow setup or for inventorying template catalog.
What inputs does List Templates require?
List Templates has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Bannerbear returns an error?
The run history shows the failed step with its input and the error message Bannerbear returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Templates support batch operations?
Run List Templates inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Bannerbear's rate limits.
More actions