ActionBannerbearUpdated May 2026

How do I fetch a Bannerbear template definition?

Short answer: Drop the "Bannerbear → Get Template" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 Bannerbear actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
ID id	string	Required	ID

Sample request

{
  "id": "{{trigger.id}}"
}

Returns

{}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Template.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Bannerbear

2 Google Sheets triggers

HubSpot → Bannerbear

18 HubSpot triggers

FAQ

Questions about Get Template.

What does the Get Template action do in Bannerbear?

Returns the template's configuration including all modifiable layers (text, image, colour) with their default values. Useful for resolving layer names at workflow-build time before generating images.

What inputs does Get Template require?

Required: ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Template support batch operations?

Yes. Run Get Template inside a Loop node to process arrays. Tiny Command handles Bannerbear's rate limits automatically so you don't have to throttle manually.

More actions