Skip to main content

Workflows

A Workflow is a reusable, ordered pipeline that a Request flows through — Brief → Script → Image → Voice → Video → Review → Publish, or whatever your process is. Workflows are where Vidiking stops being a planning tool and starts doing the work: stages can execute automatically (fire an AI job, push a publish) and advance themselves.

Open Manage → Workflows (/workflows) to build them. Building, editing and attaching workflows is free — only the AI-generation stages cost credits when they run.

Building a workflow​

The Workflows page is a drag-and-drop stage builder. You add stages, order them, and for each stage pick a kind:

Stage kindWhat it doesRuns automatically?
👤 PersonAssigned to a specific user.No — waits for that person.
👥 TeamAssigned to a team.No — waits for the team.
🏢 DepartmentAssigned to a department.No — waits.
⚡ AI generateFires an AI job (image, video, music, voiceover or script) from the request's brief.Yes — auto-runs on entry.
📤 PublishPushes the latest output to a configured destination.Yes — auto-runs, then auto-advances.

Each stage can also be marked as an approval gate and given an SLA (hours).

Auto-generation mapping

An ⚡ AI generate stage maps the layer kind to a provider automatically: Image → DALL·E 3, Video → Runway, Music → ElevenLabs music, Voiceover → ElevenLabs Flash, Text → AI script. Image stages use DALL·E 3 by default (works with the configured OpenAI key); video stages use Runway and require a Replicate key to be configured.

Attaching a workflow to a request​

From a request's detail panel, Attach Workflow and pick one. Attaching:

  • links the workflow to the request,
  • immediately enters stage 0 and runs it if it's an executable (AI/Publish) stage.

The request detail then shows a stepper of stages with the current position highlighted, plus controls to advance, approve, reject, run-now (↻) and skip.

How progression works​

When a stage finishes, Vidiking tries to advance:

  • Executable stages (AI generate, Publish) run on entry and, when done, cascade forward automatically through any subsequent auto stages.
  • Manual stages (Person/Team/Department) wait — the assignee does the work, then someone advances the request.
  • Approval gates block. The request cannot move past a gate until an approval with decision APPROVED exists. Trying to advance through an un-approved gate is refused.
  • Reaching the last stage marks the request DONE at 100%.

Every transition (stage started, stage completed, approved, rejected, published) is written to the Activity Log, and SLA targets are stamped as each stage is entered.

Approval gates​

At a gate, a REVIEWER+ (or a manager) approves or rejects:

  • Approve records an APPROVED decision and auto-advances the request to the next stage.
  • Reject records a REJECTED decision and holds the request for rework.

The request keeps a full approval history so you can see who approved what and when.

Running and skipping stages manually​

For auto stages, the panel shows "⚡ auto-generating…" while a job is in flight, plus:

  • ↻ Run now — re-run the stage (e.g. retry a failed AI job),
  • Skip — move past the stage without running it.

A typical pipeline​

Brief ─▶ ⚡ Script ─▶ ⚡ Image ─▶ ⚡ Voiceover ─▶ ⚡ Video ─▶ ✋ Review (gate) ─▶ 📤 Publish
        (AI)        (AI)        (AI)            (AI)        (REVIEWER+)        (auto)

Attach this to a request and the AI stages fire in sequence, pausing at Review for a human approval, then auto-publishing once approved. Don't want to build it by hand? Install one from the Marketplace.

Publishing your own workflows​

A workflow you've built can be shared to the Marketplace with Publish (choose a category); published workflows show a 📢 Published badge. Unpublish removes them again. Both actions are manager-only.

Next​