Turn a speaker spreadsheet of up to 20 speakers into social cards, stories, a lineup reel with music and a print-ready programme




This workflow turns a speaker spreadsheet into a promo kit for your event. You give it the sheet, the event name, the date and a short summary. It makes a card and a story for each speaker, a lineup reel with music, a programme to read or print, and post copy. The sheet can have up to 20 speakers.
You control the speaker sheet, the event name, the date and the summary. Each speaker gets a card, a story and a programme page, in the order of the rows.
Every template in this workflow is yours to edit. Add your own logo, change the colors and fonts, move the layers or change the dimensions. Your next run uses the new design.
Run this workflow yourself in the app, or start it from your own code, your other apps or an AI assistant.
Install the workflow, fill in its inputs in your dashboard and run it. You can also share a form so that other people can run it.
Send the workflow uid and its inputs to one endpoint. The run continues in the background and returns the finished files.

Start a run when something happens in another app, such as a new row in a sheet or a new form entry.
Connect Claude or Cursor to the Bannerbear MCP server, and then ask it to run the workflow with your data.
This workflow is a starting point. Add, remove or reorder steps to make it do more. Each Bannerbear tool can be a step, with over 25 tools on offer.
The common questions about this workflow, and their answers
Up to 20. The lineup reel is made from one story card for each speaker, and the reel tool takes at most 20 images. A sheet with more rows fails at the reel step.
Seven columns: name, company, role, talk, event, date and photo. The photo column holds the link to an image of the speaker. Open the example input on this page to see the layout.
Each programme page is A5 (148 x 210 mm). Two pages fill an A4 sheet in landscape, so the sheet has perforation lines to cut along and no room for crop marks. The CMYK file is the same sheets, for a print shop.
The post copy is written by AI from the event name, the date and your summary. The music for the reel is made by AI. The cards, the stories, the programme and the print sheets come from your spreadsheet and the templates, with no AI.
The example run on this page used 61 API credits and 10.1 AI credits. The cost of a run can change with your input, for example the length of a video or the number of rows in a spreadsheet. There is no charge for the workflow itself.
Yes. You do not have to open the app to run it. You can start it from your own code with the API, from a Zap in Zapier, or from an AI assistant that is connected to the Bannerbear MCP server. Each run takes your data and gives you the finished files.
Yes. The install gives you your own copy of the workflow and of its templates. You can change the templates, such as the colors, fonts and logo, and you can change the steps of the workflow.
A run is not instant, so the API answers at once, and the run continues in the background. Ask for the run to see its status. The status is queued, running, completed or failed. When the run is completed, it lists its outputs.
A sequence of steps that runs as one thing. Each step is an image render, an animation render, or a tool — and a step can use the output of an earlier step as its input.
Define its inputs, then supply them when you run it. Steps reference those inputs the same way they reference each other’s outputs.
POST to the workflow’s run endpoint with its inputs. The run is queued and reports progress as each step completes.
That is the point of inputs. Define the parts that change — a headline, an image URL, a name — and supply them per run.
Yes. Each run records every step, its inputs, its outputs and how long it took, so a failure points at the step that caused it rather than the whole workflow.
The run stops there and the failure is recorded against that step, with the outputs of the steps that already succeeded still available.
As long as its steps need — video work is not instant, and a workflow with several video steps takes minutes rather than seconds. Use the run’s progress or a webhook rather than holding a request open.
The workflow and its bundled templates are copied into your workspace, and the steps are rewritten to point at your copies rather than the originals.
Three on a trial. They are counted per workspace.
A workflow decides what gets made. An integration decides what triggers it and where the result goes. They are often used together.
Other ready-made workflows you can install









Turn a guest spreadsheet into A4 sheets of tent cards that read correctly from both sides when folded








Turn an attendee spreadsheet into personal badges, A4 sheets with cut guides and a CMYK file for a print shop






Give photos of empty rooms and get AI staged images, before and after videos, a social card and a seller brochure
Start a free trial with 30 API credits, no credit card required

