n8n

The bannx community node renders your templates from n8n workflows. Data from any earlier node fills the template's variables, and the result is an image, a PDF or a video URL you can send on. A trigger node starts a workflow each time a render finishes.

What you can do

Node	Operation	What it does
Bannx	Template → Render	Renders a template with your data to PNG, WebP, SVG, PDF, MP4, WebM or GIF and returns the file URL.
Bannx	Template → Get Many	Lists the templates in your space, with search.
Bannx	Render → Get Many	Gets the latest finished renders.
Bannx Trigger	Render Completed	Starts the workflow when a template finishes rendering, from the editor, the API or another workflow.

The Bannx node also works as a tool for n8n's AI Agent, so an agent can pick a template and render it.

Install the node

On a self-hosted n8n, open Settings → Community Nodes, choose Install, enter n8n-nodes-bannx and confirm. The Bannx and Bannx Trigger nodes then appear in the node panel.

Connect your account

In bannx, open Settings → Space → Developers and click Create API key.
Leave the key's endpoint scopes unrestricted, or tick the three the node uses:
- Template Render API, to render.
- Template Read API, to list templates and read their variables.
- Webhook Subscriptions API, for the Bannx Trigger.
In n8n, add a Bannx API credential and paste the key. Leave Base URL as https://bannx.com.

The key works on its own space only. The Bannx Trigger also needs the key's owner to be allowed to manage webhooks in the space, like the space owner or an admin.

Render a template

Add the Bannx node, choose Template → Render and pick the Template from the list.
The template's variables appear under Variables. Map values from earlier nodes into them, or switch to automatic mapping to match input fields by name. Leave a variable empty to keep the template's own value.
Pick the Format.
Under Additional Fields, optionally set a Size (a preset such as og or story, or 1080x1350), a Brand, a Variation ID, a Scale, or Use Unpublished Changes.

The node returns the file url, the format, creditsCharged and balanceAfter. Videos and GIFs take longer than stills; the node waits up to ten minutes for the file.

Values travel as n8n sends them, and bannx converts text to each variable's type: numbers, true/false, a list as JSON or comma-separated text, an object as JSON. The Zapier guide has the full table.

Start a workflow on a new render

Add the Bannx Trigger and activate the workflow. bannx then sends each finished render to n8n with templateId, format, url and timestamp. Pick a Template to react to that template only.

While the workflow is active, its subscription shows in Settings → Space → Developers → Webhooks as n8n · render.completed. Deactivating the workflow removes it. Each delivery is signed with a secret only that workflow knows, and the trigger rejects anything unsigned.

Credits

Workflows render with your space's credits, at the same price as any other render: a still costs 1 credit and a clip 5 by default. A render without enough credits fails the node with CREDITS_EXHAUSTED. See Rendering.

Troubleshooting

What you see	Why	Fix
The credential test fails	The key was revoked, expired, or mistyped.	Create a new key and update the credential.
`This API key is missing the template.read scope`	The key is limited to other endpoints.	Edit the key's scopes in Settings → Space → Developers, or use an unrestricted key.
`not allowed to manage webhooks in this space` when activating	The key's owner cannot manage webhooks.	Use a key created by the space owner or an admin.
The trigger never fires on a local n8n	bannx only delivers to public HTTPS addresses.	Run n8n on a public URL, or use a tunnel and set n8n's `WEBHOOK_URL` to it.

All error codes are listed on Errors. The routes the node calls are listed in the Zapier guide.