schedule_slideshow_series is a carousel clock, not a video series
A recurring slideshow is one named automate job: a premise, a UTC cron, a fresh caption-in-image carousel each tick. A video workflow on the same cadence is a different bill.
schedule_slideshow_series is a carousel clock. One premise. A fresh slideshow every tick. It is not a recurring video series, not a one-off slideshow, not a scheduler for last week's carousel. Point a video workflow at this tool, or this tool at a talking-head show, and you will either get stills when you wanted motion, or you will pay motion when you wanted stills.
Schedule a recurring slideshow series is the named agent job. Required: series_premise and schedule_cron. On each tick an LLM invents a brief that fits the premise and avoids recent ones, then generates a new slideshow with the caption baked into each image (Nano Banana Pro by default, async). Optionally auto-post as a carousel to connected accounts. Captions are in-image, not overlay. This is not the Pinterest-plus-overlay style.
Cadence is a five-field UTC cron. "Every day at 10am" is 0 10 * * *. Unspecified timezone is UTC. The agent should ask for local time when unclear. Neither this series nor the video series stores America/New_York.
Each run is priced like a slideshow generation, charged when it actually runs — not when you set the clock.
What the job is
A premise that can yield a new brief forever: "5 coffee tips a day," weekly cooking slides, a Sunday roundup. list_slideshow_schedules is how you find the id to pause (active: false). Auto-post needs connected accounts first.
The AI slideshow maker is the one-shot launcher. Generate a slideshow from a prompt is the one-shot agent job. This capability is the clock on top of a theme, not a saved deck you rerun identically.
What it is not
- A recurring video series. Run a recurring video series is
schedule_workflowon a saved scene workflow: new plot, same cast, video models, video prices. Same English ("every morning") does not make them the same tool. - Posting one existing slideshow on a clock. That is post or schedule with
scheduled_at. This job makes a new deck each tick. If you wanted the same six slides on Thursday, you wanted post. - A full content pipeline from a vague campaign brief. Set up a full content pipeline plans mixed steps. A slideshow series will not become a week of Reels because the premise mentioned TikTok.
- Overlay-caption carousels. In-image bake is the path. If you needed stamped overlay type on photos you uploaded, that is a different slideshow job.
The waste is almost always the video series you started because you said "series," or the slideshow series you started because you said "every day" about a file you already liked.
The test
Do you want a new carousel of stills, on a cron, from a premise that can mutate without repeating last week?
Yes: this job. Premise plus UTC schedule. Auto-post only after accounts exist.
If you want new video, save a workflow and schedule that. If you want the same file twice, post it twice. Name the artifact before you name the clock.
FAQ
Does creating the schedule charge every future run up front?
No. Each run is priced when it generates. Turning the series on is not a bulk purchase of the quarter. Turning it off is how you stop the bill.
Can I use this for a daily talking-head show?
Not as this tool. Talking-head is video (and usually lipsync). Recurring video series is the named job for that artifact.
What timezone is 9am?
UTC unless you translated from a local time the agent asked for. DST is your problem to fold into the five fields. The cron will not spring forward for you.
How do I stop it without deleting the idea?
list_slideshow_schedules, then schedule_slideshow_series with active: false and the id. Pause is a first-class path. Do not create a second overlapping series because you could not find the first.