Bannerbear integration

What it does

The Bannerbear integration lets your agency render on-brand creative for a client from inside a workflow. Connect a client's Bannerbear project once and your workflows can generate static images from a template with per-layer modifications, kick off video renders against a video template, render a full template set as a collection in one call, look up the status of any render by UID, page through historical renders, and react in real time when Bannerbear finishes a render and posts the completed object to the workflow's inbound URL.

Connect a Bannerbear account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Bannerbear and click Connect.
3. In a new tab, open the Bannerbear dashboard signed in as the client (or as your agency, if the client has invited you into their project).
4. Open the project you want to wire up, go to Settings, API Key, and copy the project API key. Project-scoped keys are preferred so revocation stays scoped to that one client.
5. Paste the key into TaskJuice. Bannerbear authenticates every request with Authorization: Bearer {api_key}.

To rotate or revoke credentials, return to the Bannerbear project Settings, regenerate the API key, and update the TaskJuice connection.

Triggers

• bannerbear/image-created fires when Bannerbear finishes rendering an image and posts the completed object to the workflow's webhook URL. One POST carries one render, and the workflow receives the full image object (including uid, template, image_url, dimensions, and any echoed metadata) as a single activation.

The trigger publishes an inbound URL. Paste it into Bannerbear as the webhook_url parameter on each Create Image action (or set it on the project's default webhook). Embed an unguessable token in the URL or front it with a proxy that sets the X-TaskJuice-Inbound-Secret header to a shared secret you also paste into the TaskJuice trigger. TaskJuice verifies that header on every inbound POST before activating the workflow.

Actions

• bannerbear/create-image renders a single image from a Bannerbear template with a list of layer modifications, optional transparent background, optional PDF render, and optional template version pin.
• bannerbear/get-image fetches the current state of a Bannerbear image render by UID and returns the final image_url once status is completed.
• bannerbear/list-images pages through image renders for the connected project using page-number pagination (max 100 per page).
• bannerbear/create-video renders a branded video from a Bannerbear video template with optional input media URL, layer modifications, and GIF preview generation.
• bannerbear/create-collection renders a full Bannerbear template set as a single collection so a workflow can produce all sizes for a campaign in one call.

Known limitations

• The Bannerbear API enforces a rate limit of 30 requests per 10 seconds per account. When Bannerbear returns 429, the action surfaces as a retryable rate-limit error so the workflow can back off and resume.
• Image, video, and collection renders are asynchronous and respond with 202 Accepted. The action returns immediately with status pending and the render's uid; use bannerbear/get-image to poll for completion, or wait for the bannerbear/image-created webhook to fire.
• Inbound webhook verification uses a shared secret on a custom header. Bannerbear does not sign webhook bodies, so the shared secret lives in the webhook URL (or in a fronting proxy that injects the header). Rotate it alongside the API key.
• The connected project is fixed on the connection itself. To work across two Bannerbear projects, create a second connection scoped to that project key.
• Template, template-set, and video-template UIDs must exist in the connected project. Bannerbear returns 404 for unknown UIDs and the action surfaces it as a non-retryable NOT_FOUND error.