A single agent produces a single piece of content. A workflow chains several agents together to produce a complete, coordinated set of content pieces in one run. The fastest way to launch your first workflow is to start from a Template, a pre-built blueprint kept in your library. This guide walks you through the full path, end to end.
📌 What you'll learn
The difference between a Workflow and a Template
How to find and pick the right Template from your library
How to brief and launch a Workflow run
How to monitor a multi-step execution and review coordinated outputs
The three reflexes to adopt when working with Workflows
Workflow vs Template: how to think about them
A Workflow is... | A Template is... |
The actual execution of a multi-step content process | A saved blueprint of a workflow, kept in your library |
A one-off, specific to a campaign or initiative | Reusable across many campaigns |
Live: it runs, produces outputs, and completes | Static: it sits in the library until someone launches it |
Found in the "Workflows" view of the Workflows module | Found in the "Templates" view of the Workflows module |
Mental model: a Template is the recipe in your cookbook. A Workflow is the meal you cook from it. Every time you launch a Template, you create a new Workflow run.
Before you start
To follow this guide, you need:
Access to a Mark AI workspace with at least one Template in the library
A campaign or initiative to produce content for (an event, a product launch, a customer win, a recurring update)
The key inputs ready: topic, target audience, key message, priority markets if applicable
If your Templates library is empty, contact your Mark AI administrator. Most accounts include 3 to 5 pre-built templates aligned with common content use cases.
Step 1 — Open the Workflows module
From the left navigation, open the Workflows module. Inside, you'll see two views:
Workflows — the runs your team has launched so far (empty if this is your first time)
Templates — the library of pre-built blueprints you can use as a starting point
The Workflows module hosts both your live runs and the Templates library that powers them.
For your first run, head to the Templates view. This is where every reusable blueprint lives.
💡 Best practice
Most teams never build a workflow from scratch. They start from a Template, customize the brief, launch the run, and refine the outputs. Reserve workflow building from scratch for genuinely new use cases.
Step 2 — Browse the Templates library
The Templates library lists every blueprint available to your team. Each row shows four key indicators:
Name — the title of the template
Description — what the template produces (blog article, LinkedIn posts, email sequence, etc.)
Contents to create — the number of distinct outputs generated in a single run
Created at and Created by — when the template was built and who built it
The Templates library lists every multi-step blueprint your team can use as a starting point.
You can filter templates by name using the search bar at the top of the list. Click on any template row to inspect its structure.
💡 Best practice
For your first workflow run, pick a template with 2 to 4 contents to create. It gives you a meaningful taste of orchestration without overwhelming your review queue with a large volume of outputs.
Step 3 — Inspect the template
Before running anything, take a moment to review the template's structure. From the Templates library, click on the template you've chosen to open its detail view. You'll see the chain of agents involved, the order they execute in, and what each one produces.
You'll know you're looking at a template (not a live workflow) in two ways:
The Template label is displayed at the top of the page
There is no Run button available, since templates cannot be executed directly. They are blueprints, not runs.
A template shows you exactly which agents will run, in what order, and what they will produce. You cannot launch it directly: templates are blueprints, not runs.
If the template fits your need, head to the Workflow tab inside the Content factory, click Create, then From Template. You'll be prompted to select the template you just inspected and to open the briefing form, which creates a new Workflow run.
Step 4 — Brief the workflow
Once you've created a new Workflow from a template, you'll land on the workflow builder. The structure is already in place (you started from a template, after all), but each block needs to be configured for this specific run: your topic, your inputs, your goal.
The workflow builder organizes blocks into six types. Each one has a clear role in the chain.
Block | Role | What you configure |
Source / Context | The starting point. Provides the raw material every downstream agent will use. | Upload files (PDF, Word, Excel, images, audio, video), import from URL, or pull from your Knowledge Base. Only one Source block per workflow. |
AI Instructions | The orchestration layer. Defines, in plain language, what the workflow should produce overall. | Campaign objective, channels covered, tone for this run, success criteria. Sits between the Source and the production agents. |
Content to Produce | A specific agent doing a specific job. One block per output (SEO blog, LinkedIn founder post, LinkedIn company post). | Agent Instructions specific to this run: length, angle, points to cover. The agent already knows your brand voice and glossary. |
Manual Approval | A control gate. Pauses the workflow until designated reviewers sign off. | Assign reviewers, choose between All reviewers must approve or Any reviewer can approve. |
Export to File | Saves the output of the previous step as a file. | Choose format (PDF, Word, Excel, CSV, JSON, Text) and filename (custom or auto-generated). |
Action blocks | Publish the output directly to a connected external platform. | WordPress (publish article), LinkedIn (post directly), and other connectors as they become available. Requires the account to be connected. |
The workflow builder lets you assemble any content process from six block types. The left panel is your toolbox; the canvas is your assembly line.
The brief you provide across these blocks is the single source of truth for every agent in the workflow. Be specific. Vague inputs produce vague outputs across the board.
💡 Best practice
Prepare your inputs before opening the workflow. Have your source document, key message, audience, and reference assets ready. The briefing should take 2 minutes per block, not 20.
Step 5 — Launch and monitor execution
Click Run. Mark AI creates a new Workflow run from the template and executes every agent in sequence, passing the output of each step as context to the next.
The new run now appears in the Workflows view of the module, where you can monitor its progress in real time.
Track every step of the workflow in real time. Each output is generated, validated, and saved before the next one starts.
A complete workflow run typically finishes in 2 to 10 minutes, depending on the number of agents and their output length.
Step 6 — Review the coordinated outputs
Once the workflow finishes, every output is displayed in a consolidated view. You can review the pieces using the side panel.
Every output generated by the workflow is organized and ready for review in one consolidated view.
Three checks specific to a workflow run:
Tone consistency. All pieces should sound like they were written by the same team.
Message consistency. The core value proposition should appear in every piece, adapted to the format.
Source consistency. Each piece should cite knowledge base documents aligned with the campaign's claims.
💡 Best practice
Read every output in sequence before refining anything. A holistic review reveals inconsistencies that you won't see piece by piece.
Step 7 — Refine and publish
Each output can be refined individually, exactly as you would refine a single agent's output: inline edits, section regeneration, or conversational refinement.
When a refinement affects a foundational element (the key message, the customer name, a core fact), you have two options:
Refine only the piece concerned if the change is local
Relaunch the workflow with an updated brief if the change cascades across multiple pieces
💡 Best practice
If you find yourself manually fixing the same issue across multiple outputs, that issue lives upstream in the agent brief or in the knowledge base. Fix it there, then relaunch.
Once every piece is ready, export them individually or publish directly to your connected channels (CMS, social, email platform).
The three reflexes to adopt with workflows
Start from a Template. Building a workflow from scratch is rarely worth it for the first runs. The library gives you battle-tested orchestrations, ready to launch.
Think campaigns, not pieces. A workflow exists to produce a coordinated set of outputs. Brief it as a campaign, not as a single piece of content.
Review holistically. Read every output before refining anything. The consistency check is the most valuable review.
Common questions
Can I modify a Template before launching it? Yes. Some teams customize the template inputs at launch time without modifying the underlying blueprint.
Can I build a workflow from scratch instead of using a Template? Yes, but we recommend starting with a Template for your first 3 to 5 runs.
Can I save my workflow run as a new Template? Yes. After a successful run, you can save the workflow's structure to the Templates library so your team can reuse it.
One of the outputs feels disconnected from the others. Why? Usually, it means the agent in that step has a different knowledge base scope or a conflicting brief. Re-check the agent's configuration with your administrator.
Can I run the same Template in parallel for multiple campaigns? Yes. Each launch creates an independent Workflow run. You can launch the same Template several times in parallel with different briefs without any interference.
➡️ Next step
You've completed your first workflow run. To finish the Get Started collection, head over to Platform tour for a guided overview of the interface and where every feature lives.
Once you've explored the platform, the Core features collection will show you how to go further: customizing templates, adapting agents to new use cases, and connecting Mark AI to your other tools.