Skip to main content
Bannerify turns a template and a set of values into an image or a PDF. The integrations on this page send those values for you. A workflow tool passes a template and some data to Bannerify, and Bannerify returns the link of the finished file.

Choose an integration

No-code tools

Zapier

Create Image and Create PDF actions for your Zaps

n8n

A community node that renders an image or a PDF

Pipedream

Render Image, Render PDF, and List Templates actions

Notion

Render a template when a page in a database changes

Developer tools

SDKs

JavaScript, Python, PHP, and Go

Signed URLs

Render an image when someone opens a link

CLI

Render a template from the terminal

MCP server

Create files from an AI assistant

Embedded editor

Put the editor in your app on the Scale and Enterprise plans

Storage

Your own S3 bucket

Save files to S3, R2, or another S3-compatible service on the Scale and Enterprise plans

Before you start

  1. Design a template and name each layer that you want to change. See Template editor and Modifications.
  2. Create an API key on the API Keys page. Zapier, n8n, and Pipedream need it, and Authenticate requests shows how. Notion connects through your Notion account and needs no key.
  3. Connect the tool and choose the template.
Zapier, n8n, Pipedream, and Notion list your templates, so you do not need the template id. A workflow that calls the API through an HTTP step does. To copy the id, open the menu on a template card and choose Copy Template ID.

What the actions return

The image actions call createStoredImage and the PDF actions call createStoredPdf. Each call returns an object with the link of the file:
Bannerify saves the file on its CDN, and the link is public. Pass the link to the next step of your workflow, for example to put it in an email or to save it in a spreadsheet. Notion saves its files the same way and writes the link to a property of the page. To save files in your own bucket, see Save files to your own S3 bucket.

Send values to a template

The Zapier, n8n, and Pipedream actions have a Modifications JSON field. It takes an object where each key is a layer name:
It also takes the array that the API uses:
In the object form, a string sets the text of the layer, and an object sets the fields that you list, such as src for an image. Modifications lists the fields that each layer type reads.

Limits

Each file counts as one generation, and the API limits apply to every tool on this page. Quota and limits lists them.

Get help

Write to an@bannerify.co or ask on Discord.