How it works
- Notion tells Bannerify that a page was created or that one of its properties changed.
- Bannerify reads the page and puts the properties that you mapped into the layers of the template.
- Bannerify renders the template and saves the file on its CDN, at a link that starts with
https://images.bannerify.co/files/. - Bannerify writes the link to the property that you chose on the same page.
Prerequisites
- A template with named layers. The mapping lists only the layers that have a name.
- A Notion database with a URL or Text property for the link, such as
Rendered URL. Add it before you create the automation. - A Notion workspace where you can add connections and share databases.
Connect a Notion workspace
- Open Integrations in the dashboard sidebar.
- Click Connect Notion.
- On the Notion screen, choose the pages and databases to share with Bannerify, then confirm.

A connected workspace with one automation.
Create an automation
- Click New automation.
- Enter a Name. If you leave it empty, Bannerify uses the name of the database.
- Choose the Notion database, the Template, and the Format: PNG image or PDF.
- Under Run when, choose A page is created, A page is updated, or both.
- Under Map Notion fields to layers, choose a property for each layer that you want to fill. A layer set to Not mapped keeps the value from the template.
- In Write the render URL to, choose a URL or Text property.
- Click Create automation.
What Bannerify sends to the template
Bannerify turns every mapped property into text and sends it to the layer:
An image must be a PNG, JPEG, WebP, or SVG file. Notion-hosted file links expire after a short time, and Bannerify fetches the link as soon as it renders.
How properties become text
A blank property gives an empty string. A property of any other type also gives an empty string.
Limits and skipped runs
A run over the render limit fails with the message
Rate limited: more than 60 renders in a minute.
Notion combines quick edits to a page into one event, and the event usually arrives within a minute.
Bannerify skips a run when the values that go into the image are the same as at the last successful run. That covers a second event for the same edit, and the event that follows when Bannerify writes the link back to the page. A skipped run does not render and does not count as a generation.