Bannerbear, without opening Bannerbear.
The template is already designed. Ray fills it in and sends the file.
- Free to start
- No card
- Every write waits for you
- One key for the workspace
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Bannerbear details, and Ray takes it from there.
@Ray render the launch banner in all five sizes.
@Ray how many renders do we have left this month?
@Ray put subtitles on the demo video.
@Ray turn these six product shots into a slideshow.
What Ray can and cannot do in Bannerbear
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
26 reads wired, 23 actions that wait for a human.
Runs on its own
What Ray reads in Bannerbear
- Your image and animation templates, with the layer schema saying which fields each one takes
- Every image, animation, video and PDF the workspace has rendered, and the assets behind them
- Whether a render has finished, plus batches and workflow runs started in Bannerbear itself
- The plan, the render quota left, and what the connected key is allowed to do
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Rendering an image, an animation or a voiceover from one of your templates
- Editing video: trim, crop, resize, join, subtitle, overlay, background removal
- Building a slideshow or a PDF out of images and clips you point at
- Saving a template, running a workflow, and opening an Instant URL others render through
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete a template, an Instant URL or a webhook
- Queue up to a hundred renders against your quota behind one approval
- Add or edit the webhooks Bannerbear posts finished renders to
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Bannerbear actions Ray can take, each one stopping in the thread with the real content before it happens.
- Generate a Bannerbear image
- Generate a Bannerbear animation
- Generate a Bannerbear voiceover
- Create video slideshow
- Create pdf
- Run a Bannerbear workflow
- Add audio
- Add cover art
- Apply color filter
- Concat videos
Generate a Bannerbear image
Showing Template and Modifications, each carrying the exact content that will land.
How Ray works with Bannerbear
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Bannerbear
Bannerbear has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Bannerbear, and tell Dana it is being looked at.
Generate a Bannerbear image
- Waiting on
- your approval
Ray uses Bannerbear together with the rest of your tools.
One ask can read Bannerbear, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Bannerbear to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Bannerbear and it can do the Bannerbear part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Bannerbear has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see Bannerbear. Every write still stops for approval first.
Security and permissions
- You paste the Bannerbear key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- An admin, or whoever connected it, can disconnect Bannerbear in a message. Uninstall Ray and every connection it held is revoked.
Bannerbear and Ray, answered
The questions teams ask before they connect Bannerbear. Every answer is how this integration is built rather than a promise about it.
More design & whiteboards integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Bannerbear.
Free to start, no credit card, and it asks before it acts.