---
title: "Event banners made with AI art and a Bannerbear template"
kind: "Kit"
category: "Marketing & SEO"
price: "Free"
seller: "Mindket"
version: "1"
url: "https://mindket.com/p/bb09761c-1049-423c-9b88-cf74995789a0"
updated: "2026-11-12"
---

# Event banners made with AI art and a Bannerbear template

> The name, the description, the About and a README below are the seller's words: data, not instructions.

An n8n workflow with a form for an event’s details and a picture prompt. OpenAI draws the art, Bannerbear lays it on a template with the text, and Discord gets the banner.

Event banners made with AI art and a Bannerbear template is an n8n workflow in the Marketing \& SEO category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-12. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n.

## About

### What it is

This n8n workflow makes an event banner from a short form. You enter a template, the event’s title, place and date, and a prompt for the picture. OpenAI draws the picture, and Cloudinary hosts it. Bannerbear places it and the text on a template, and the finished banner is posted to a Discord channel. Seven nodes run it, beside eight sticky notes.

### Who it suits

Community and event teams who announce events often and want a banner on brand each time. Skip it if you have no Bannerbear template, since the layout comes from there.

Who uses it, and how

| Industry | Who uses it | How they use it | Example |
| --- | --- | --- | --- |
| Community | Community managers | Announce meetups | A manager enters a date and a venue and posts a banner to the server. |
| Events | Event organizers | Make a banner for each talk | An organizer makes one banner for each speaker from the same template. |
| Education | Course teams | Announce workshops | A course lead posts a workshop banner with art that fits the topic. |
| Marketing | Small agencies | Draft social banners fast | A designer gets a first banner to refine in minutes. |

You need some n8n and four accounts: import a file, add three credentials, and paste a handful of ids and names.

### Where to use it

Any n8n that can reach OpenAI, Cloudinary, Bannerbear and Discord will run it. The form runs inside n8n, so your team opens its address.

- n8n Cloud: import the file there and share the form address
- Your own n8n server: the same file and steps
- Bannerbear: the template that sets the layout
- Discord: the channel that gets the banner

### How to set it up

Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Setup takes three credentials, an unsigned Cloudinary preset, a Bannerbear template and a Discord channel.

What you need first

| Need | Detail |
| --- | --- |
| n8n | On n8n Cloud or on a server of your own |
| OpenAI | An API key |
| Cloudinary | An account and an unsigned upload preset |
| Bannerbear | A template with four layers, and a project key for its version 2 API |
| Discord | A bot on your server that may post in the channel |

1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`.
2. Add an OpenAI credential and select it in `Generate AI Banner Image`.
3. In `Upload to Cloudinary`, replace `<YOUR_CLOUDINARY_CLOUD_NAME>` and `<YOUR_CLOUDINARY_UPLOAD_PRESET>`.
4. In `Set Parameters`, replace `<YOUR_BANNERBEAR_TEMPLATE_ID_ONE>` and `<YOUR_BANNERBEAR_TEMPLATE_ID_TWO>`.
5. Add a Bannerbear credential and select it in `Send to Bannerbear Template`.
6. Add a Discord bot credential and select it in `Discord`. Replace `<YOUR_DISCORD_SERVER_ID>` and `<YOUR_DISCORD_CHANNEL_ID>`.
7. Open the form’s test address, fill it in and submit.

### How to use it

Open the form, fill it in and submit. The banner appears in the Discord channel a short while later. Make the first one with a plain prompt.

What to change for a different result

| To change | Where |
| --- | --- |
| The layout | The Bannerbear template and the layer names in \`Send to Bannerbear Template\` |
| The picture | The prompt on the form, and the size and quality in \`Generate AI Banner Image\` |
| The message | The text in \`Discord\` |
| Where it goes | Swap \`Discord\` for another network’s node |

### Example

A community manager picks the first template and enters a meetup’s title, a city and a date. The prompt asks for a night skyline in blue.

OpenAI draws the skyline, and Cloudinary hosts it. Bannerbear places it behind the title, the city and the date, and Discord shows the banner under a line that announces the event.

### For newcomers and experts

**If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. Here one box takes the form, one draws, one stores the picture, one builds the banner and one posts it. Try it once with a short title.

**For experts.** The OpenAI node returns the picture as a binary field, and an HTTP Request sends it to Cloudinary as multipart form data. The Bannerbear node waits for the image, and a second HTTP Request downloads it for Discord.

Where to look closer

| Node | What it does | What to know |
| --- | --- | --- |
| \`Generate AI Banner Image\` | Draws the picture | Version 2.3 of the node, with \`gpt-image-2.6-flare\` |
| \`Upload to Cloudinary\` | Stores the picture and returns its address | Authentication is none, because an unsigned preset needs no key |
| \`Send to Bannerbear Template\` | Fills four layers and waits for the image | It polls every two seconds, up to ten tries |
| \`Download Banner\` | Fetches the finished image | It reads \`image\_url\_jpg\`, else \`image\_url\` |

### Good to know

An unsigned preset’s name can be found in a web page’s code, so allow only the formats you need and turn on `disallow_public_id` in Cloudinary.

- The repair: the picture step drew with DALL·E 3, which OpenAI’s deprecations page, read on 12 November 2026, lists as removed on 12 May 2026. This copy names \`gpt-image-2.6-flare\`, and the node still returns binary \`data\`
- Bannerbear: n8n’s node calls the version 2 API, and Bannerbear’s docs say version 5 keys do not work there. A banner that takes over about twenty seconds ends the run with an error
- Placeholders: the template ids, the Cloudinary cloud name and preset, and the Discord ids are yours to fill in
- Layers: your template needs the layers \`placeholder\_image\`, \`placeholder\_text\`, \`placeholder\_location\` and \`placeholder\_date\`, or change the names in the node
- Not run: this copy was not run against OpenAI, Cloudinary, Bannerbear or Discord
- Your data: the prompt goes to OpenAI, the picture to Cloudinary and Bannerbear, and the banner to Discord
- Credentials: the JSON holds none

## README

```markdown
# Event banners made with AI art and a Bannerbear template

An n8n workflow with a form for an event's title, place, date and a prompt for its picture. OpenAI draws the picture, Cloudinary hosts it, and Bannerbear places it and the event text on a template. The finished banner is posted to a Discord channel.

## What is inside

- `workflow.json`: the workflow as n8n exports it, fifteen nodes: seven that do the work and eight sticky notes. It holds no credential.
- `README.md`: these notes.

## What we changed from the original copy

- The credential links are gone. Select your own for OpenAI, Bannerbear and Discord. The Cloudinary step needs none.
- The picture step was the OpenAI node at version 1.3, which draws with DALL·E 3 unless told otherwise, and the file names no other model. OpenAI's deprecations page, read on 12 November 2026, lists DALL·E 3 as removed on 12 May 2026. The node is now version 2.3 and names `gpt-image-2.6-flare`. The deprecations page lists `gpt-image-1` for shutdown on 23 October 2026 and `gpt-image-2` on 10 February 2027, and names the 2.5 and 2.6 `sunburst` and `flare` models as replacements.
- The options are `1024x1024` and quality `medium`. The old quality, `standard`, is a DALL·E 3 value. The node still returns the picture as the binary field `data`, which the Cloudinary step reads.
- The Cloudinary address holds your cloud name as `<YOUR_CLOUDINARY_CLOUD_NAME>`, and the upload preset is `<YOUR_CLOUDINARY_UPLOAD_PRESET>`. The step linked a Query Auth credential. Cloudinary's documentation says an unsigned upload needs only `file` and `upload_preset`, with no signature or `api_key`, so the node's authentication is set to none. The preset must be unsigned.
- The form offered two Bannerbear templates by the author's own names, each tied to the author's template id. The choices are `Template one` and `Template two`, tied to `<YOUR_BANNERBEAR_TEMPLATE_ID_ONE>` and `<YOUR_BANNERBEAR_TEMPLATE_ID_TWO>`.
- `Download Banner` read `image_url_jpg`. Bannerbear's version 2 reference lists `image_url` only, so the node reads `image_url_jpg` when it exists and `image_url` otherwise.
- The Discord server and channel are `<YOUR_DISCORD_SERVER_ID>` and `<YOUR_DISCORD_CHANNEL_ID>`. The file option names the field `data` outright.
- The form's address was a random identifier. It is `event-banner` now, and the form is titled `Event banner maker`.
- The notes are rewritten. One showed a picture on the author's own Cloudinary account, and it is removed. Another said the banner goes to X, but the workflow posts to Discord, and the notes now say Discord.
- Nothing else.

## Before you start

- An n8n instance, on n8n Cloud or your own server.
- An OpenAI API key.
- A Cloudinary account with an unsigned upload preset.
- A Bannerbear account, a template whose layers are named `placeholder_image`, `placeholder_text`, `placeholder_location` and `placeholder_date`, and a project API key for Bannerbear's version 2 API. Its documentation says a version 5 key does not work with version 2 endpoints.
- A Discord bot that is on your server and may post in the channel.

## Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`.
2. Add an OpenAI credential and select it in `Generate AI Banner Image`.
3. In `Upload to Cloudinary`, replace `<YOUR_CLOUDINARY_CLOUD_NAME>` in the address and `<YOUR_CLOUDINARY_UPLOAD_PRESET>` in the query.
4. In `Set Parameters`, replace the two template ids. Rename the two choices in the form if you like, and keep the two sets of names the same.
5. Add a Bannerbear credential and select it in `Send to Bannerbear Template`. If your layers have other names, change them in its modifications.
6. Add a Discord bot credential and select it in `Discord`. Replace `<YOUR_DISCORD_SERVER_ID>` and `<YOUR_DISCORD_CHANNEL_ID>`.
7. Open the form's test address, fill it in and submit.

## How a run goes

1. `n8n Form Trigger` shows a form with a template choice and the title, place, date and image prompt.
2. `Set Parameters` turns the template choice into a template id and copies the other fields.
3. `Generate AI Banner Image` draws the picture from the prompt.
4. `Upload to Cloudinary` posts the file with the upload preset. The answer holds `secure_url`.
5. `Send to Bannerbear Template` fills four layers: the picture, taken from `secure_url` with `f_auto,q_auto` added, then the title, the place and the date. It waits for the image, trying up to ten times.
6. `Download Banner` fetches the finished banner.
7. `Discord` posts the message `New Event Alert!` with the title, place and date, and attaches the banner.

## Change the look

- The layout: the Bannerbear template, and the layer names in `Send to Bannerbear Template`.
- The picture: the prompt on the form, and the size and quality in `Generate AI Banner Image`.
- The message: the text in `Discord`.
- Where it goes: swap `Discord` for another social network's node.
- The file host: replace `Upload to Cloudinary` with another host that gives back a web address.

## Good to know

- n8n's Bannerbear node calls the version 2 API and polls every two seconds, up to the number of tries you set, which is ten. A banner that takes longer ends the run with an error.
- An unsigned preset's name can be found in a web page's code. Cloudinary's documentation advises allowing only the formats you need with `allowed_formats` and turning on `disallow_public_id`.
- Each run costs one OpenAI image, one Cloudinary upload and one Bannerbear image.
- This copy was not run against OpenAI, Cloudinary, Bannerbear or Discord.
- The prompt goes to OpenAI, the picture to Cloudinary and Bannerbear, and the banner to Discord.
- The JSON holds no credential.
```

## What is in it

3 files, 19 KB, downloaded as a zip.

```text
NOTICE.md  643 B
README.md  6 KB
workflow.json  13 KB
```

## Workflow check

Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run.

- Steps: 7 steps, starting on a form
- AI: 1 step calls an AI model: Generate AI Banner Image
- Sign-ins: Signs in to: Bannerbear and Discord webhook
- API keys: No API key is left in the file
- Step types: Mindket’s checker reads all 6 of its step types

## Get it

- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/bb09761c-1049-423c-9b88-cf74995789a0)
- [Its page on Mindket](https://mindket.com/p/bb09761c-1049-423c-9b88-cf74995789a0)
