Short-Video Script & Storyboard Writer guide

What it does

Topic or blog post → ready-to-film Reels, TikTok and Shorts scripts, storyboards, captions and a posting plan.

Receives a topic, blog post or notes through a webhook, with the platforms and how many videos you want (1–3).
AI writes each short video: a 2-second hook, a timed voiceover script, a shot-by-shot storyboard with on-screen text, a shot list and a music mood.
Writes captions and hashtags for TikTok, Instagram Reels and YouTube Shorts (title and description), plus a suggested posting plan and a filming checklist.
Saves everything to a page in your Notion content database and adds a row to your posting-plan sheet in Google Sheets.
Posts the batch title, video count, platforms and the Notion link to your Slack channel; briefs without a usable topic go back to Slack with questions instead.

What it needs

A paid plan (agents run live on paid plans).
An AI provider key (Settings → AI Providers).
Notion, Google Sheets and Slack, connected in Settings → Integrations.
A form or tool that can send briefs to a webhook URL.

What it doesn't do

It doesn't render, edit or export video, and doesn't create voiceovers, b-roll, music or burned-in captions.
It doesn't post to TikTok, Instagram or YouTube, or schedule posts in a social tool.
Posting times are starting points from your posting window, not from your accounts' analytics.
It writes in one language per brief (the brief's language field, otherwise English); it doesn't translate or localize a batch into several languages.

Availability and plans

Available

Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.

Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.

Before you start

A paid plan: agents run live, and the Free plan only runs Dry Runs.
An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
These apps, connected in Settings → Integrations: Notion, Google Sheets and Slack.
A form, app or system that can send each new item to a webhook URL (the agent starts from a webhook).
About 15 minutes.

Set it up step by step

Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.

1. Connect your AI provider

The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.

Connect your AI provider

2. Connect Notion

Connect the Notion workspace that holds your content database (Settings → Integrations → Notion), and share the database with Fluxo Flow.

Connecting Notion

3. Connect Google Sheets

Connect the Google account that can edit your posting-plan sheet (Settings → Integrations → Google Sheets).

Connecting Google Sheets

4. Connect Slack

Connect the Slack workspace your content team uses (Settings → Integrations → Slack).

Connecting Slack

5. Describe your brand and style

Open “Write scripts, storyboards and captions” and replace the placeholder with your brand, audience, on-camera style, call to action and posting window.

Setting	What to enter	In step
Your brand, audience, style and posting window	Replace the placeholder with who you are, who watches, the on-camera style (face to camera, voiceover, screen recordings), your call to action, topics to avoid and when your audience is online. It starts as “[DESCRIBE YOUR BRAND, AUDIENCE, ON-CAMERA STYLE AND POSTING WINDOW HERE]” until you replace it.	“Write scripts, storyboards and captions”

6. Pick the Notion database

Open “Save scripts and storyboards to Notion” and pick your account and database.

Setting	What to enter	In step
Notion account	The Notion workspace the scripts are saved to. Pick your connected Notion account.	“Save scripts and storyboards to Notion”
Notion content database	The database each batch of scripts becomes a page in. Share it with Fluxo Flow first: ••• → Connections.	“Save scripts and storyboards to Notion”

7. Pick the posting-plan sheet

Open “Add the batch to the posting-plan sheet”, pick your Google account, paste the spreadsheet link and pick the tab.

Setting	What to enter	In step
Google account (posting plan)	The Google account that can edit your posting-plan sheet. Pick your connected Google Sheets account.	“Add the batch to the posting-plan sheet”
Posting-plan spreadsheet	Paste the link of the Google Sheet you plan videos in. Columns: Added, Batch, Topic, Videos, Platforms, Suggested slots, Status.	“Add the batch to the posting-plan sheet”
Posting-plan tab	The tab (sheet) inside the spreadsheet the rows are added to.	“Add the batch to the posting-plan sheet”

8. Pick the Slack channels

Open the two Slack steps and pick your account and a channel in each (they can be the same). Invite the app to private channels first (/invite @Fluxo Flow).

Setting	What to enter	In step
Slack account (brief questions)	The Slack workspace questions about thin briefs are posted to. Pick your connected Slack account.	“Ask for a better brief in Slack”
Channel for brief questions	Where the people who send briefs will see the questions.	“Ask for a better brief in Slack”
Slack account (scripts ready)	The Slack workspace the “ready to film” notice is posted to. Pick your connected Slack account.	“Tell the team the scripts are ready”
Channel for finished scripts	Where your creators hear that new scripts are ready, e.g. #video.	“Tell the team the scripts are ready”

9. Test it with Dry Run

Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.

Dry Run vs Run

10. Switch the trigger on

Open the trigger, switch the webhook on and point your brief form or tool at its URL (send the secret in the x-fluxo-secret header).

How it works

The agent is a normal workflow with 10 steps (1 AI step). You can open, edit and monitor it like any other workflow.

New video brief — Starts when your form or app sends data to the agent's webhook URL. Your form or content tool posts a topic, a blog post or notes to the workflow's webhook URL, with the platforms and how many videos you want (1–3).
Write scripts, storyboards and captions — AI step (runs on your AI provider key). AI turns the brief into 1–3 ready-to-film short videos: hook, timed voiceover script, shot-by-shot storyboard, on-screen text, captions per platform, hashtags, music mood and a suggested posting plan.
Brief usable? — Decision: picks the branch to follow. Briefs without a usable topic go back to Slack with questions; the rest become a script page in Notion and a row in your posting plan.
Ask for a better brief in Slack — Slack: Post a message. Branch: Needs more info. Posts the topic and the AI's questions to your content channel.
Sent back for details — Kept in the run history. The run history keeps the brief and the questions asked.
Save scripts and storyboards to Notion — Notion: Create a page in a database. Branch: Brief OK. Creates a page in your content database with every video's script, storyboard, shot list, captions, the posting plan and a filming checklist.
Tell the team the scripts are ready — Slack: Post a message. Posts the batch title, topic, number of videos, platforms and the Notion page link to your content channel so a creator can start filming.
Scripts delivered — Kept in the run history. The run history keeps the scripts.
Add the batch to the posting-plan sheet — Google Sheets: Add a row. Branch: Brief OK. Adds a row to your posting plan in Google Sheets: date, batch title, topic, number of videos, platforms, suggested slots and status “Scripted”.
Plan updated — Kept in the run history. The run history keeps the posting-plan row that was added.

Test it with Dry Run

Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. Edit the sample to match the fields your own form or app sends.

Sample data fields

topic, source_text, platforms, videos, call_to_action, requester_name.

Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.

Go live

Open the trigger, switch the webhook on and point your brief form or tool at its URL (send the secret in the x-fluxo-secret header).
The webhook is protected by a secret: send it in the header shown in the Activation panel (requests without it are refused with 403). Each request starts one run.
The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.

Questions

Does it make the video?

No. It writes scripts, storyboards, shot lists and captions that a creator films and edits (on a phone, CapCut, Premiere…).

Does it post to TikTok or Instagram?

No. The captions and posting plan are ready to paste into the apps or your scheduling tool.

Are the posting times based on my analytics?

No. They follow the posting window you describe, or general starting points; test and adjust them.

Troubleshooting

“No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
Nothing happens when your form sends data: check the webhook is switched on and the request carries the secret header (403 means it's missing or wrong).
A step failed: open the run in History and check that step in the Trace tab for the error and what it received.

Generated from the agent's own workflow, so it always matches what the agent does. Last updated October 12, 2026.