Resources · n8n integration

Bannerbear n8n integrationAutomate Bannerbear with n8n.

One image per row, per lead, per upload, without opening a design tool. The Bannerbear n8n integration exposes 4 operations across 2 resources: render a template into an image, fetch it back, read one template or list them all. No Bannerbear trigger exists, so another node starts the run.

Try the Bannerbear integration on n8nSee the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What the Bannerbear n8n integration actually does

Bannerbear turns a template into a finished image from an API call. The n8n node wraps that API in 4 operations split over 2 resources, Image and Template, so a workflow can pick a template, replace the layers that change, and hand the render to whatever comes next.

The credential is a project API key stored once in n8n, and the node appears in the same canvas as every other step, so the image never travels through a human.

Take a weekly promo list in Google Sheets, one row per product, one column for the price and one for the headline. The workflow reads the rows, calls Create an image on the promo template with two modifications, and drops each render into a Slack channel where the marketing lead approves it before anything goes live.

Second pattern: publishing. A new episode row triggers a render on a thumbnail template, the text layer takes the episode title, the image layer takes the guest photo, and the image object travels on to the YouTube upload or to a post on X (Formerly Twitter). Same template every week, different text, no manual export.

Third pattern is about the templates themselves. Get many templates lists what the connected project holds, which is how a workflow stops hard-coding an identifier that changed last month. Get a template reads one of them by ID before a render, and Get an image fetches a render back later when the workflow did not wait for it.

The node ships with 4 operations. Anything else in the Bannerbear API goes through the HTTP Request node, which calls any endpoint of the service while reusing the same credential through predefined authentication. That is the standard escape hatch in n8n, and it means a missing operation never blocks a workflow.

One thing to plan for: Bannerbear has no trigger node in n8n. A workflow around it starts somewhere else, with a Schedule Trigger on a fixed interval, with the n8n Webhook node, a URL that n8n exposes and that another service calls, or with the trigger of another tool in the chain. The n8n review covers how those starting points behave in practice.

Connect

How do you connect Bannerbear to n8n?

  1. 01

    Generate the project API key

    Create a Bannerbear account, then create a project inside it. The key belongs to that project, so generate it in the one that holds the templates the workflow will render. Open Settings > API Key to view the Project API Key, and copy it. Bannerbear documents the same path in its API authentication page.

  2. 02

    Store the credential in n8n

    In n8n, open the Credentials menu and create a Bannerbear credential, the only authentication method the node supports being an API key. Paste the Project API Key and save. A credential is created once and reused by every workflow on the instance, on n8n Cloud or on a self-hosted install, so this step happens a single time per project.

  3. 03

    Wire the node into a workflow

    Add the Bannerbear node to the canvas and pick the credential from its dropdown. Choose the resource, Image or Template, then the operation. Since there is no Bannerbear trigger, put a Schedule Trigger or an n8n Webhook node in front of it, or chain it after the node that produces the data you want printed on the image.

Actions

What the Bannerbear node can do

The Bannerbear node exposes 4 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet Many
Image✓✓
Template✓✓

Image

2 operations
01

Create an image

image.create

What you see in n8n

Notes & use cases

Create an image renders one Bannerbear template and returns the image object, identifier included.

Key parameters

  • Template Name or ID: pick the template in the dropdown, or pass an ID with an expression such as {{ $json.templateId }} when a previous node chose it.
  • Modifications: one Add Modification entry per layer, where Name or ID targets the layer and Text, Image URL (must be publicly viewable), Color or Background replace what it shows.
  • Wait for Image: on, the node waits for the render and throws an error after three tries, unless Wait Max Tries raises that count.
Use cases
a product launch sheet feeds one banner per row, a different headline on each render.
02

Get an image

image.get

What you see in n8n

Notes & use cases

Get an image reads a render back from Bannerbear by its identifier. It does not create anything, it retrieves what a previous Create an image produced.

Key parameters

  • Image ID: the unique identifier of the image, typed for a one-off check or passed as an expression when it comes from the item flowing in.
Use cases
a workflow that left Wait for Image off stores the identifier, does other work, then comes back to this operation before attaching the render to a message.

Template

2 operations
03

Get a template

template.get

What you see in n8n

Notes & use cases

Get a template reads one template of the connected project by its identifier, so a workflow can look at the template it is about to render instead of assuming what it contains.

Key parameters

  • Template ID: the unique identifier of the template, the same value the Create an image dropdown resolves to.
Use cases
a nightly check reads the template a campaign relies on and stops the run when the identifier no longer resolves, rather than shipping a batch of failed renders.
04

Get many templates

template.getAll

What you see in n8n

Notes & use cases

Get many templates returns the templates of the project the credential belongs to, in one call and with no field to fill in.

Use cases
a small internal tool calls this operation to build the list a colleague picks from, then feeds the chosen template into Create an image. It also answers the question every team asks twice a year, which template is still in use and which one nobody has touched since the last rebrand. Run it once after connecting the credential and the output confirms which project the key opened.
Need help

Need help automating Bannerbear with n8n?

A person reads every message.

FAQ

Bannerbear and n8n, common questions

01Is the Bannerbear n8n integration free?
Yes on the n8n side. The Bannerbear node ships with n8n, so there is nothing to install and no extra cost to use it, on n8n Cloud as on a self-hosted instance running the Community Edition under the Sustainable Use license. A workflow behaves the same way in both places, and the credential you store is reused by every workflow without paying per connection. What a Bannerbear account itself costs is a separate question, handled on Bannerbear's side, and this page does not cover it.
02What credentials do you need for the Bannerbear node?
An API key, which is the only authentication method the node supports. You need a Bannerbear account, a project inside it, and the Project API Key found under Settings and then API Key in that project. Create the credential once in the n8n Credentials menu, paste the key, and every Bannerbear node on the instance offers it in its dropdown. Since the key is scoped to a project, generate it from the project that holds the templates the workflow renders, otherwise the node authenticates against the wrong set of templates.
03What are the limits of the Bannerbear node in n8n?
The node covers 4 operations over 2 resources: Image, with Create an image and Get an image, and Template, with Get a template and Get many templates. Whatever falls outside that catalog goes through the HTTP Request node, which calls any endpoint of the Bannerbear API and reuses the same credential through predefined authentication. Worth knowing on renders: with Wait for Image enabled, the node throws an error after three tries if the image is not ready, and Wait Max Tries is the field that raises that number.
04Does Bannerbear have a trigger node in n8n?
No. Bannerbear has no trigger node, so a workflow around it always starts with something else: a Schedule Trigger running on a fixed interval, the n8n Webhook node called by another service, or the trigger of another tool already in the chain. Create an image also exposes a Webhook URL field, a URL that receives a POST with the image object once rendering is complete, and an n8n Webhook node can be that URL when a second workflow should pick the render up. Between the two, most teams start from the data source.
05n8n or Make for Bannerbear?
It depends on where the workflow lives and how you want to pay for it. Make is hosted by Make, with no self-hosting option, and bills per operation, which is predictable when volume is low and less so when a batch renders hundreds of images. n8n runs on n8n Cloud or on your own server, so the data and the render requests stay on infrastructure you pick, which matters when the images carry customer information. Both build visually. Try the node on one template before committing either way.
Same platform

Other docs you might need on this stack.

Browse all integrations