What is a kanban board for a marketing team?
It is a shared board where each card is one deliverable and each column is a stage it passes through. A card might be a blog post, a newsletter issue or a campaign asset, moving left to right from research to draft to approved to scheduled. Kanban suits marketing because requests arrive all the time: you pull the next idea when there is room, and a card waiting in Review is waiting for a person.
How do you set up a Flux board for content and campaigns?
Start from the built-in Content Calendar template, add a Research column, and use labels for channels and due dates for publish dates. The steps:
- Set the workspace type to Marketing. An owner or admin picks Marketing under Workspace type in the workspace settings. Flux then suggests its marketing templates first on the boards page.
- Create the board from Content Calendar. It starts with Ideas, Drafting, Review, Scheduled and Published, plus a few sample cards you can archive. The Free plan allows one board, so rename the columns of the Project Board created at sign-up instead.
- Add a Research column between Ideas and Drafting. Research agents pick up work there.
- Create a label per channel, such as Blog, Newsletter or Social, and filter the board by label.
- Put publish dates in due dates. The due-date filter shows what is coming up.
- Give campaigns their own board on Pro or Expert, which have unlimited boards. Create it from the built-in Campaign Tracker template, or adapt the marketing campaign template's columns.
The resulting board, and who moves cards into each column:
| Column | What happens there | Who moves cards in |
|---|---|---|
| Ideas | Topics and requests, one deliverable per card | Anyone on the team, or a research agent proposing topics |
| Research | A brief goes into the card description: audience, angle, sources, open questions | A person, once the idea is approved |
| Drafting | The first draft is posted as a comment, or linked from one | The research agent, when the brief is done |
| Review | An editor checks facts, voice and claims, then approves or sends it back | The drafting agent or a writer, when the draft is done |
| Scheduled | Approved work, with the publish date as its due date | An editor, never an agent |
| Published | Live work, with the URL in a comment | The person who published it |
More column ideas: the content calendar template and the SEO project template.
Where do AI research and drafting agents fit on the board?
Agents work the middle of the board, Research and Drafting. People own both ends: what gets made, and what ships. Flux does not run agents or write anything itself. It is the board they connect to, as Claude, Codex, Cursor or your own script, through the Flux MCP server. Each step maps to one MCP tool:
| Step | What the agent does | Flux MCP tool |
|---|---|---|
| Find work | Reads the board, then the cards in Research or Drafting | get_board, list_cards |
| Avoid duplicates | Checks card titles for the topic before adding a new idea | search_cards |
| Read the task | Reads the description and every comment, including editor feedback | get_card |
| Write the brief | Saves the brief to the card description | update_card |
| Share the draft | Posts the draft, or a link to it, as a comment | add_comment |
| Hand off | Moves the card to the next column | move_card |
| Propose topics | Adds a new card to Ideas | create_card |
Keep the brief in the description and put drafts in comments. update_card replaces the whole description, so a drafting agent that saved its draft there would overwrite the brief. Comments add up instead: each revision is a new comment, with the editor's feedback next to it. Both render Markdown. Long drafts can stay in your document tool, with the link in the comment.
Write the rules into the instructions your agents read at the start of every session. An example to adapt:
## Content board rules (example) - Work only on the board "Content - Blog". Do not read or change other boards. - Research agent: take cards from "Research". Write the brief into the card description: audience, angle, 3-5 sources with links, open questions. Then move the card to "Drafting". - Drafting agent: take cards from "Drafting". Read the description and every comment first. Post the draft as one comment, then move the card to "Review". - Start every comment with your agent name, for example "[drafting-agent]". - Never invent statistics, quotes or customer names. Link a source for every number. - Never move a card to "Scheduled" or "Published".
These rules are instructions, not locks. Flux does not stop an agent with a Write key from moving a card to Published, so the review step depends on the rules and on your editors. For what a card should carry, see context engineering for AI agents.
How do you connect an AI agent to a marketing board?
Create an API key for the agent, add the Flux MCP server to its client with that key, give it the board rules and test it on one card. In detail:
- Create one API key per agent in Settings, under API Keys. Every key can read boards and cards; tick Write only for agents that change cards. Name the key after the agent, for example "research-agent". Create it from the account of a workspace owner, admin or member (not a viewer), because a board guest's key cannot reach the board over MCP.
- Add the Flux MCP server to the agent's client with the key, following the setup for your client. Claude Code, Cursor, Codex, Windsurf and Cline connect directly. Claude's web and desktop apps connect as a custom connector only if your account has the Request headers option, which Anthropic describes as a beta for a limited set of organizations.
- Give the agent the board rules in the file it reads at the start of every session, such as
CLAUDE.mdorAGENTS.md. - Test on one card. Put a test card in Research, ask the agent to take it, and check the description and comment before giving it more.
A key acts as the person who created it: the agent can reach every board that person can, and its comments appear under that person's name. That is why agents should sign their comments. One key per agent lets you revoke a single agent.
How do editors review and approve AI drafts?
The Review column is the approval step, and only people move cards out of it. An editor reads the brief, the draft and its sources, checks every claim, then moves the card to Scheduled or back to Drafting with a comment. Google's guidance says: "It is critical to manually factcheck and review all AI-generated content for accuracy and trustworthiness before publishing." That includes titles, meta descriptions, structured data and image alt text (Google Search Central).
- Open the card and read the brief, the draft comment and the sources it links.
- Check every number, quote and name against its source. Anything unsourced goes back.
- Approve: move the card to Scheduled and set its due date to the publish date.
- Or send it back: comment what to change and move the card to Drafting. The agent reads your comment through
get_card, which returns each comment's text and time but not its author. Agents therefore sign their comments, and anything unsigned reads as feedback from a person. - Once a week, check Scheduled and Published for cards that skipped Review. One means the rules need tightening.
The same guidance warns that using generative AI "to generate many pages without adding value for users may violate" Google's spam policy on scaled content abuse. A Review column won't stop a team publishing too much, but it puts a person in front of every piece. See also human-in-the-loop for AI agents.
How do stakeholders, clients and freelancers sign off without a paid seat?
Invite them to the one board they need as board guests. Board guests are not workspace members, so they are never billed. An owner or admin invites them in the board's settings, under Guests. The invitation is valid for 7 days, and the guest accepts it by signing in, or signing up for free, with the same email address.
| Who | Joins as | What they can do | Billed on Pro and Expert |
|---|---|---|---|
| Your marketing team | Workspace member (owner, admin, member or viewer) | Work on every board in the workspace; viewers only read | Yes, per member |
| Leadership or sales following progress | Board guest, viewer role | See every card, comment and attachment on that board; cannot comment or move cards | No |
| Legal, brand, a client who signs off, or a freelancer | Board guest, member role | Comment, move and edit cards, and attach files, on that board only | No |
| AI agent | API key created by a workspace member | What the key's creator can do | No |
Guests can also be given an admin role, but inviting or removing guests still takes a workspace owner or admin. Flux has no comment-only role, so a guest who can comment can also edit cards. A guest sees every card on the board, so keep budgets and internal notes elsewhere. For agencies, see kanban for agencies with client access; for roles, workspaces and roles.
How do you plan publish dates without a calendar view?
Flux has no calendar or Gantt view. Publish dates live in each card's due date, and the due-date filter does the calendar's job. What you can use:
- Due dates and start dates on every card. Filter by Overdue, Due in the next day, Due in the next week or Due in the next month.
- Recurring cards, from Daily to Yearly. When someone marks a weekly newsletter card's due date complete in the app, the same card stays on the board, its due date moves to the next week and its checklist resets.
- The Multi-Board View shows the content board and every campaign board on one screen, with the same filters. It merges columns that share a name, so name your Review columns the same on every board.
What can Flux automate for a marketing team?
Two extensions: Slack, which posts board events, and Automation, which assigns people to new cards. Recurring cards also roll forward when completed in the app. None of this is triggered by changes agents make over MCP.
- Slack extension. Posts board events such as card created, card moved and new comments to a Slack channel, so the managing editor hears when a writer moves a card to Review (moves made over MCP don't post, see below).
- Automation on Pro and Expert. A rule assigns members when a card is created in a column, for example the managing editor on every new card in Ideas.
- The agent gap. Changes made in the app and through the REST API are recorded in the activity log, post to Slack and run automation rules. Changes made over MCP do none of these, so check the Review column directly.
What doesn't Flux do for marketing teams?
Flux tracks the work. It does not write, schedule or publish content, and it does not enforce your approval step. In detail:
- No publishing. Flux has no CMS, email or social scheduling integration.
- No approval button, locked columns or WIP limits. Approval is a person moving the card, and nothing caps how many cards wait in Review.
- No hidden cards and no public share link. Guests need a free Flux account.
- Agents can't label, assign or attach. Over MCP an agent can set a card's title, description, due date and priority, but not its labels, assignees or attachments. People add those.
- MCP changes are not logged, and an agent's comments show under the name of the person who created its key. Signed comments and one key per agent keep the trail readable.
For agent-heavy teams in engineering as well as marketing, see the kanban board for AI agents. Current plans and prices are on the pricing page.