Content workflow template
This template takes a written brief to a published piece. A model drafts it, unsupported claims are flagged, an editor approves the text, and publishing waits for a named person.
Last reviewed 7 October 2026
Starting point
The status rests on the workflow openai-multi-modal, which sets a topic and asks a model for a blog post, then runs an embedding and a summary. Only the draft step is relevant. The brief, the claim check, the editing and the publishing are yours to build.
The library has a template, chatflow, MCP server or governed template that covers part of the job. You assemble the rest in Studio.
What this template does
A content lead or head of marketing owns the workflow, with writers, editors and a channel owner for each place the work appears. The job is steady output that sounds like the organisation and says only what it can stand behind.
By hand, drafts sit in documents with comments nobody resolves, a claim from a sales call reaches a post with no source, and publishing depends on whoever has the login that day. This flow starts from a brief that names the sources a piece may rely on, flags what they do not support and records who approved the final text.
The workflow, step by step
Steps marked as approval gates pause the run until a named person approves. Nothing after a gate runs before that decision, and the decision is recorded.
- 01
Capture the brief
The requester completes a form: topic, audience, goal, the sources the piece may rely on and the claims it must not make. Studio stores it as the brief record. The shipped workflow sets only a topic, so this is the step that makes the draft usable. The next step receives the brief. - 02
Draft the piece
A model writes the first draft from the brief and your style guide, using the blog post prompt as a base. It is told to use only the supplied sources. The shipped workflow generates a post from a topic alone, so replace that input with the brief. The next step receives the draft. - 03
Flag unsupported claims
A second pass lists every number, name, date and factual claim in the draft and looks for it in the supplied sources. Anything it cannot find is marked for the editor, with the sentence quoted. It does not remove or rewrite them. The editor receives the draft with the flags. - 04
Editor approval
The run pauses for the named editor, who edits the text, resolves each flag and approves it or returns it with comments. A returned draft goes back to the draft step with the comments attached, up to a limit you set. The approved text is frozen and passed on.Approval gate: a named person approves before the next step runs. - 05
Approve publishing
The workflow prepares a headline, a meta description and short channel posts from the approved text alone, using the social post prompt as a base. The run then pauses for the channel owner, who confirms text, headline, channel and time. Assign someone other than the editor if your policy needs two views.Approval gate: a named person approves before the next step runs. - 06
Publish and record
After approval the workflow publishes to the site and schedules the channel posts. It writes the live addresses back to the brief record, with the approved text, the flags, the editor and channel owner decisions and the times, so a later challenge can be answered.
What it can do, cannot do, needs approval for, and records
Can
- Draft from a brief and your style guide
- List claims the supplied sources do not support
- Prepare headline, description and channel variants
- Publish and schedule after approval
Cannot
- Publish anything an editor and a channel owner have not approved
- Add facts that are not in the brief or its sources
- Remove a flag without the editor resolving it
- Change the style guide or the claims it must not make
Requires approval
- The final text, by the named editor
- Publishing and scheduling, by the channel owner
- Any claim about customers or results, by the person who owns the source
Records
- The brief and the sources named
- The draft, the flags and the editor’s changes
- The approved text
- Each approver, decision and time
What the library holds for this job
| Asset | Type | Covers | Role in this flow |
|---|---|---|---|
| Openai Multi Modal | Workflow template | Part of the job | Sets a topic, asks a model to generate a blog post and then runs an embedding and a summary. It supplies the draft step only. |
| Write a Blog Post Introduction | Prompt | Used inside the flow | A starting prompt for the opening of a post. |
| Create Social Media Posts | Prompt | Used inside the flow | A starting prompt for the short posts that accompany a piece. |
| Wordpress | Integration | Used inside the flow | A publishing target if the site runs on WordPress. |
Integrations this flow uses
- WordPress: A publishing target if the site runs on it.
- Notion: Holds briefs and the editorial calendar if the team keeps them there.
- Slack: Carries the approval requests to the editor and channel owner.
- Mailchimp: A possible target for the newsletter version.
The full list of tools Studio connects to is on the integrations page.
What you supply, and what this page does not cover
- You supply the brief form, the style guide, the list of claims the organisation must not make and the people who approve.
- A model draft needs an editor. This template does not judge quality, originality or whether a topic is worth writing about.
- Search ranking, distribution and measurement are outside this page.
- Check the rules on disclosing AI-assisted content that apply where you publish. This page is not legal advice.
Common questions
- Does it publish without a person?
- No. The design has two pauses: the editor approves the text and the channel owner approves publishing. Nothing leaves before both decisions are recorded. You choose whether those are two different people. The platform does not enforce that, so you do it by how you assign the gates.
- How does it stop made-up facts?
- It cannot stop them entirely. The brief names the sources a piece may use, the model is told to stay inside them, and a second pass flags every claim it cannot find there. The editor resolves each flag. This lowers the risk of an invented fact reaching publication. A person still has to read.
- What does the shipped workflow give me?
- A model call that writes a blog post from a topic, followed by an embedding and a summary step. That is useful as a draft step. It has no brief, no source checking, no editing and no publishing, so those are parts you build around it in Studio.
- Can it write for several channels?
- Yes. After the editor approves the main text, the workflow prepares headline, description and short-post variants for each channel from that text alone. The channel owner approves them with the article. Posting to a channel needs its integration, which you connect and control.