# Vitra Flow — Agentic Content Workflow Builder | Vitra.ai > Compose image, video, translation and personalization steps into one run, with switch, parallel, merge, approval and delay gates, callable over MCP and API. **Canonical URL**: https://www.vitra.ai/features/agentic-workflows **Source**: This is the Markdown rendering of https://www.vitra.ai/features/agentic-workflows, generated at build time from that page. --- Orchestration # Vitra Flow — Agentic Content Workflows One idea, drawn from your own context, becomes a campaign image. That image becomes twenty languages and five aspect ratios. A video of the same concept becomes twenty dubs and five ratios of its own. Then it personalizes to a thousand distributors and publishes itself. Vitra Flow is where that runs as one flow instead of eleven tools and a spreadsheet — with switch, parallel, merge, approval and delay gates deciding what happens next. [Start creating free→](https://universe.vitra.ai/auth/sign-up)[Book a demo](https://sales.vitra.ai/meetings/akash-nidhi-p-s) Free to start · 75+ languages · No credit card required Capabilities ## What Vitra Flow does ### One canvas, every modality Image creation, video creation, dubbing, translation, personalization and QC are nodes on the same canvas. A flow can start at an idea and end at a published asset without ever leaving it. ### Five gates that make it a workflow Switch branches on a value — a QC score above 85 goes straight to dub, below it goes to review. Parallel runs branches at once. Merge brings them back. Approval parks the run until a named person signs off. Delay waits. Without these you have a pipeline; with them you have a workflow. ### Fan out by language One approved concept becomes twenty language versions in a single parallel branch, each resolving wording from VitraTM and context from Vitra Memory, so the twentieth is as on-message as the first. ### Fan out by aspect ratio The same asset is adapted to 1:1, 9:16, 16:9, 4:3 and 3:4 rather than cropped to them — layout, focal point and text re-fit per frame. Twenty languages across five ratios is one hundred variants from one node. ### Fan out by recipient Personalization turns the localized set into a version per distributor, partner or segment. A thousand distributors is a list length, not a project plan. ### Quality gates in the flow, not after it Quality control returns Approved, Review or Blocked as a value a switch node can read, so a failing asset routes to a human while the rest of the batch keeps moving. ### Publish as a step The last node is distribution — social channels, CMS, LMS, email campaigns, or a webhook into whatever you already run. The flow ends at published, not at a download folder. ### MCP, API, SDK and CLI Every node is also a callable skill, so your own agents can drive the same capabilities, and n8n, Make, Zapier or a webhook can trigger a flow from the system that owns the content. ### Auditable, and reusable as a template Every run is recorded node by node against an append-only ledger, so cost and outcome are attributable per run. A flow that works becomes a template the next campaign starts from. How it works ## Four steps, one orchestrated run Every stage runs on the same platform, so nothing is exported, re-uploaded, or handed between tools. - 01 ### Start from context, not a blank node The first node draws on Vitra Memory — company, product and market context, plus your prompts — so the concept is grounded in what is true about you before anything is generated. - 02 ### Fan out in parallel Split into branches: images one way, video the other. Each branch multiplies across languages and aspect ratios simultaneously rather than waiting its turn. - 03 ### Gate on quality, then on a person QC scores every variant and a switch node routes on the verdict. An approval node holds anything carrying a claim until a named reviewer releases it, while clean branches continue. - 04 ### Merge, personalize, publish Merge brings the branches back into one set, personalization expands it per recipient, and the final node pushes to your channels — with every artifact landing in the Asset Manager. Who it is for ## Teams using Vitra Flow ### One idea to a global campaign A concept becomes 100 image variants and 100 video cuts — twenty languages across five aspect ratios each — before personalization multiplies it again per market. ### Distributor and partner networks A thousand distributors each receive the same campaign carrying their own name, region and language, generated from one template and one approval. ### Catalogue pipelines A new SKU in the PIM triggers imagery, video and localized copy without anyone writing a brief, gated so nothing reaches a storefront unreviewed. ### Agent-driven production Your own agents call Universe skills as tools inside a larger flow, with the human gates still enforced by the platform rather than by the agent's judgement. FAQ ## Questions people ask What logic gates are available? + Switch sends the flow down a different branch depending on a value. Parallel runs several branches at once and continues when they all finish. Merge brings branches back into a single path. Approval waits for a named person before continuing. Delay waits a set amount of time. Together they are what turn a fixed pipeline into a workflow that can react. Can one workflow span images, video, text and audio? + Yes — that is the reason it exists. Image creation, video creation, dubbing, translation, personalization and QC are nodes on the same canvas, so a single run can take an idea to a finished multi-format campaign without exporting between tools. How does aspect-ratio adaptation work? + Assets are adapted to 1:1, 9:16, 16:9, 4:3 and 3:4 rather than cropped, so layout, focal point and text re-fit for each frame. It runs as a fan-out node, which is why twenty languages across five ratios is one hundred variants produced by one step rather than one hundred jobs. Can a workflow wait for human approval? + Yes, and it is a first-class node rather than a workaround. The run parks at the approval gate until a named reviewer signs off, while independent branches keep processing — so oversight costs latency on the gated branch only, not on the whole batch. How is this different from n8n or Zapier? + Those orchestrate calls between systems; this orchestrates content production inside one. The nodes are dubbing, image translation and personalization rather than HTTP requests, and they share a translation memory, a brand kit and a QC layer. Vitra Flow also connects to n8n, Make and Zapier, so a flow can be triggered from the automation platform you already run. Can my own AI agents drive it? + Yes. Universe is MCP-native, so any MCP-aware agent can discover and call its capabilities as tools, and the same capabilities are available over REST API, SDK and CLI. The approval gates remain enforced by the platform, which is what makes agent-driven production reviewable. Can I see what each run cost? + Yes. Every execution is recorded node by node against an append-only credit ledger that is the single source of truth for usage, so cost is attributable per run, per workflow and per team — including the runs that a gate blocked. ## Explore next [Vitra Memory→The context a flow starts from.](https://www.vitra.ai/features/knowledge-base) [Asset Manager→Where every artifact lands.](https://www.vitra.ai/features/asset-manager) [Video Personalization→The fan-out per recipient.](https://www.vitra.ai/features/video-personalization) [Quality Control→The verdict a switch reads.](https://www.vitra.ai/features/quality-control) ## Start with Vitra Flow. Grow into the whole platform. Everything in Vitra Universe shares one translation memory, one brand kit, and one quality bar — so the work you do here makes everything you do next faster. [Start creating free→](https://universe.vitra.ai/auth/sign-up)[Book a demo](https://sales.vitra.ai/meetings/akash-nidhi-p-s) --- ## Structured data ```json { "@context": "https://schema.org", "@type": "SoftwareApplication", "name": "Vitra Flow — Agentic Content Workflows", "applicationCategory": "BusinessApplication", "operatingSystem": "Web", "url": "https://www.vitra.ai/features/agentic-workflows", "description": "Compose image, video, translation and personalization steps into one run, with switch, parallel, merge, approval and delay gates, callable over MCP and API.", "featureList": [ "One canvas, every modality", "Five gates that make it a workflow", "Fan out by language", "Fan out by aspect ratio", "Fan out by recipient", "Quality gates in the flow, not after it", "Publish as a step", "MCP, API, SDK and CLI", "Auditable, and reusable as a template" ], "isPartOf": { "@type": "SoftwareApplication", "name": "Vitra Universe", "url": "https://www.vitra.ai" }, "publisher": { "@id": "https://www.vitra.ai/#organization" } } ``` ```json { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.vitra.ai" }, { "@type": "ListItem", "position": 2, "name": "Features", "item": "https://www.vitra.ai/features" }, { "@type": "ListItem", "position": 3, "name": "Vitra Flow — Agentic Content Workflows", "item": "https://www.vitra.ai/features/agentic-workflows" } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What logic gates are available?", "acceptedAnswer": { "@type": "Answer", "text": "Switch sends the flow down a different branch depending on a value. Parallel runs several branches at once and continues when they all finish. Merge brings branches back into a single path. Approval waits for a named person before continuing. Delay waits a set amount of time. Together they are what turn a fixed pipeline into a workflow that can react." } }, { "@type": "Question", "name": "Can one workflow span images, video, text and audio?", "acceptedAnswer": { "@type": "Answer", "text": "Yes — that is the reason it exists. Image creation, video creation, dubbing, translation, personalization and QC are nodes on the same canvas, so a single run can take an idea to a finished multi-format campaign without exporting between tools." } }, { "@type": "Question", "name": "How does aspect-ratio adaptation work?", "acceptedAnswer": { "@type": "Answer", "text": "Assets are adapted to 1:1, 9:16, 16:9, 4:3 and 3:4 rather than cropped, so layout, focal point and text re-fit for each frame. It runs as a fan-out node, which is why twenty languages across five ratios is one hundred variants produced by one step rather than one hundred jobs." } }, { "@type": "Question", "name": "Can a workflow wait for human approval?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, and it is a first-class node rather than a workaround. The run parks at the approval gate until a named reviewer signs off, while independent branches keep processing — so oversight costs latency on the gated branch only, not on the whole batch." } }, { "@type": "Question", "name": "How is this different from n8n or Zapier?", "acceptedAnswer": { "@type": "Answer", "text": "Those orchestrate calls between systems; this orchestrates content production inside one. The nodes are dubbing, image translation and personalization rather than HTTP requests, and they share a translation memory, a brand kit and a QC layer. Vitra Flow also connects to n8n, Make and Zapier, so a flow can be triggered from the automation platform you already run." } }, { "@type": "Question", "name": "Can my own AI agents drive it?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Universe is MCP-native, so any MCP-aware agent can discover and call its capabilities as tools, and the same capabilities are available over REST API, SDK and CLI. The approval gates remain enforced by the platform, which is what makes agent-driven production reviewable." } }, { "@type": "Question", "name": "Can I see what each run cost?", "acceptedAnswer": { "@type": "Answer", "text": "Yes. Every execution is recorded node by node against an append-only credit ledger that is the single source of truth for usage, so cost is attributable per run, per workflow and per team — including the runs that a gate blocked." } } ] } ```