Workflows

Build the pipeline once, run it on every stream

Workflows turn AutoVOD's tools into a single chain that runs on its own: live downloader → generate clips → generate shorts → your approval → upload. You build the chain once in a visual editor, pick what starts it, and every future stream walks the same path without you opening a tool page.

Before workflows, every tool was a dead end. You generated clips, came back later, picked the good ones, opened the Shorts Creator, waited again, then queued uploads by hand. The only chaining that existed was a single checkbox on live downloaders that auto-generated clips. Workflows replace that with an explicit, reorderable pipeline — and keep a human gate wherever you want one.

How it works

  1. Pick a trigger. A workflow starts manually, when a live downloader finishes recording, or whenever any download completes.
  2. Add steps in order. Each step is one of the five tools — clip, shorts, re-encode, summarize, trim — plus two engine steps: an approval gate and an upload hand-off. Up to 10 steps per workflow, 10 workflows per account.
  3. Set options per step. Every step reuses the same settings form as its tool page, so a clip step takes the same clip length, count, and prompt fields you already know.
  4. The engine carries files forward. Each step's output becomes the next step's input. A clip step that produces six clips feeds all six into the shorts step below it.
  5. Approve what ships. An approval step parks the run and drops it in your Approvals inbox with a thumbnail grid. Approve a subset, and only those continue.

Runs are event-driven, not polled — each step advances the moment the job behind it finishes, so a workflow is no slower than running the same tools by hand.

What you get

  • A visual builder with reorder, remove, and inline per-step options
  • Three triggers: manual, live-recording finished, or any download finished
  • A human approval gate with thumbnails, optional auto-approve after N hours, and an optional minimum virality score
  • Upload as a final step, handing finished files to scheduled YouTube and TikTok posts
  • Full run history with per-step status, and cancel at any point
  • A pending-approval badge in the sidebar so a parked run never goes unnoticed

Built to not run away with your credits

A clip step yielding ten clips would otherwise spawn ten shorts jobs. Two things prevent that:

  • A per-step item cap. Each step carries forward at most 5 files by default, adjustable up to 25.
  • Parking instead of failing. If you run out of credits or queue slots mid-run, the workflow parks in a waiting state and resumes automatically when capacity returns, rather than erroring out. Parked runs expire after 24 hours.

Failure policy is continue with survivors: if three of six clips fail to reframe, the run carries the three that worked. A run only fails when a step ends up with nothing to pass on. Cancelling a run stops its outstanding jobs and refunds their credits.

FAQ

What happens to my live downloader's "generate clips" checkbox?

Attaching a workflow to a downloader takes over. The recording starts your workflow instead of the old hardcoded clip job, so exactly one of the two paths runs. Downloaders without a workflow keep working exactly as before, and your original setting is left untouched in case you detach later.

Can I run a workflow on files I already have?

Yes. Trigger it manually from the workflow page and pick the files to start from.

What if a step does not fit the one above it?

The builder flags it while you edit — a shorts step under a summarizer step, for example. It is advisory, not blocking: at run time the engine skips files a step cannot use rather than failing the run.

Can an approval gate approve itself?

Optionally. Set an auto-approve window, in hours, and anything still waiting when it expires proceeds automatically. You can also set a minimum virality score so weak clips never reach the inbox.

Does a broken workflow break my normal tool jobs?

No. The engine is wrapped so anything it throws is logged and swallowed — a workflow bug can never take down the tool job or upload that triggered it.