Kanban Zone

Kanban Zone is a Kanban board and flow-metrics tool built on lean principles. Agents create, move and search cards, manage checklists, comments and labels, read the eight flow reports and start flows from card events.

1 trigger 52 actions Basic auth available

Kanban Zone website Platform Documentation Capability data verified 2026-08-18

On Card Event fires when a card is created, updated or moved on the delivery board

Get Card reads the card by its board number with its owner, labels and custom fields

List Board Columns reads the destination column's work in progress limit and agreement

Agent confirms the move respects the limit rather than pushing the column past it

Add Card Comment records why the card moved and what evidence supported it

A digest of blocked and overdue cards posts to the team channel with the flow figures

The flow manager approves any sweep that moves cards other people are counting on

What This Integration Enables

Kanban Zone is built for teams who use the board as a measurement instrument rather than a to-do list. Columns carry work in progress limits and explicit agreements, boards report how many cards are active, archived, backlogged, blocked and overdue, and eight flow reports sit behind Get Board Report. That is a lean practice encoded in a product, and it changes what automation is for here. An agent that just creates cards adds noise. An agent that reads the column's limit before it moves anything, and that leaves the reason on the card, keeps the measurement honest.

FlowRunner agents create and move cards, search across the organization, manage checklists, comments, labels and tokens, and read the reports the team makes decisions from. Two details shape every workflow: a card is addressed by the number on the board while everything under it uses internal identifiers, and a card's owner, watchers and labels are set by email address and label text rather than by identifier. Both mean the agent reads the board before it writes to it. And because moving cards is what generates the flow data, the sweep that reorganizes a board is exactly where FlowRunner's human-in-the-loop gate belongs.

Without FlowRunner

Metrics nobody trusts Cards get dragged for tidiness, and the cycle time report inherits every one of those moves

Limits as suggestions A column passes its work in progress limit and nothing says so until standup

Reports pulled by hand Somebody opens each report when a stakeholder asks, and the answer is a screenshot

With FlowRunner

Moves that carry a reason Every agent move leaves a comment on the card saying what triggered it

Limits checked before the move The destination column's limit and agreement are read as part of the decision

Reports arrive on a schedule Flow reports and board metrics are read and summarized where the team already works

Use Case Scenarios

Intake that respects the column agreement

A request arrives from a form in Typeform or a ticket in Zendesk. The agent calls Search Cards to check the work is not already on the board, reads List Board Columns for the intake column's work in progress limit, and reads List Board Custom Fields so the values it writes are ones the board accepts. Create Card places the card with its owner set by email address and its label set by text. If the intake column is already at its limit, the agent does not push a card in anyway. It posts the request to the flow manager with the current count and lets them decide what leaves before anything enters.
A blocked-work watch that reaches people

On a schedule, the agent reads List Boards for the counts of blocked and overdue cards, then List Cards for the boards where those counts moved. For each blocked card it calls Get Card Metrics to see how long it has been sitting where it is and List Card History to see what changed last. The digest that lands in Slack names the cards, the owners, and how long each has been blocked, which is a different conversation from asking who forgot to update the board.
Flow reports the leadership meeting can rely on

Before the monthly review, the agent walks the boards that matter, calls Get Board Report for the time-based reports over a fixed window and again for Allocation with its grouping, and writes the results into Google Sheets so the trend survives past one meeting. Because the agent pulls the same reports over the same window every month, the comparison is a comparison rather than two differently drawn snapshots.

Human-in-Loop Highlight

Move Card looks like the safest write in this connector and is not. Two facts make it the one to gate. First, the destination is decided entirely by the column: a column identifier belonging to another board performs a cross-board move to that board, and the board field selects which mirror to move rather than where the card lands. Second, every move is data. Kanban Zone computes cycle time, allocation and the rest of its reports from the history each move writes, so a tidy-up sweep does not just rearrange a board, it rewrites the numbers the team plans capacity with. So when a hygiene agent finds forty stale cards, it does not move them. It posts to the flow manager: "38 cards have sat in Doing for more than 30 days. Moving them to Done would close them and add 38 completions to this month's throughput and cycle time. Move them to Done, move them to the Backlog column instead, or leave them and flag the owners?" The manager picks, the agent executes that choice and comments on each card with the reason. The board gets tidy without the report quietly becoming fiction.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

52 actions

Organization

Get Authenticated Organization Returns the organization the configured key belongs to. The cheapest way for a flow to confirm the connection works.
Get Organization Returns the organization with as much of its contents as you ask for. Turning on every include returns boards, members, custom fields, columns and labels in one very large answer, so a workflow asks only for what it reads.

Boards and Reports

List Boards Returns the organization's boards with their card counts, including how many are active, archived, backlogged, blocked and overdue. The cheapest way to notice a board that needs attention.
Get Board Returns one board with its card counts, and optionally its members and labels. The board read to prefer.
Get Board Metrics Returns one board through the older singular route, kept because the vendor's earlier examples use it.
List Board Columns Returns a board's columns with their work in progress limits and explicit agreements. Also where the column identifiers that card creation and moves depend on come from.
List Board Custom Fields Returns a board's custom field definitions with the options each one allows. Reading this first is what keeps a card's custom field values from being rejected.
List Board Labels Returns a board's labels with their colors and sort positions.
List Board Members Returns the people on a board with their status, and the email addresses a card's owner and watchers are set by.
Get Board Report Returns one of a board's eight flow reports. The seven time-based reports take a window; Allocation takes a grouping instead.

Cards

List Cards Returns a board's cards a page at a time, up to one hundred per page, reporting whether more remain so a flow can walk to the end.
Search Cards Searches cards by text across the organization or within one board. The duplicate check before anything is created.
Get Card Returns one card, addressed by the number shown on the board rather than an internal identifier.
Get Card By Number Returns one card through the older singular route, which requires the board alongside the number.
Get Card Metrics Returns a card's flow figures: how long it has spent where. The evidence behind an aging or blocked-work report.
List Card History Returns what changed on a card and when. The from date has to be before today, so a workflow asks for yesterday onward rather than this morning.
Create Card Adds a card to a board. Owner and watchers are set by email address and the label by its text, so all three come from the board rather than from an identifier lookup.
Create Cards Adds several cards to a board in one call. A batch can be half accepted, and the rejections come back in the answer rather than being lost silently.
Update Card Changes a card. Setting blocked to false unblocks it, which is a different request from leaving the field alone.
Patch Card Changes a card through the vendor's patch route, which takes the same body as Update Card.
Move Card Moves a card to a column. The column decides the destination board, so a column belonging to another board performs a cross-board move. The operation this page's human gate exists for.
Move Card By Number Moves a card through the older singular route.
Update Card By Number Changes a card through the older singular route.
Create Card On Board Adds a single card through the older singular route.
Delete Card Deletes a card.
Link Cards Links a card to another card or to an external address. The link types are directional, so parent and child, and predecessor and successor, are opposites.
Unlink Cards Removes a link from a card, either to another card or to an external address.

Checklists and Tasks

List Card Checklists Returns a card's checklists with the tasks inside each one.
Create Card Checklist Adds a checklist to a card, optionally seeded from a checklist template. The fast way to attach a standard process to a card as it is created.
Create Checklist Adds a checklist through the standalone route, which can create its tasks in the same call and addresses the card by its internal identifier.
Update Checklist Renames a checklist or moves it up or down the card.
Delete Checklist Deletes a checklist and the tasks inside it.
Create Task Adds a task to a checklist. The owner here is an internal account identifier rather than the email address a card's owner takes.
Update Task Changes a task, including ticking it off. Setting completed to false reopens a finished task.
Move Task Moves a task to another checklist or to another position in the same one. Both checklists and the position are required.
Delete Task Deletes a task from its checklist.

Comments

List Card Comments Returns a card's comments with their replies and reactions.
Add Card Comment Adds a comment to a card in plain text or markdown. Where an agent records what it did and why.
Create Comment Adds a comment through the standalone route, addressing the card by its internal identifier.

Labels and Tokens

Get Label Returns one label.
Create Label Adds a label to a board. The visible text lives in the description field, and setting a label as default clears the flag on whichever label held it.
Update Label Changes a label's text, color, position or default flag.
List Card Tokens Returns the tokens on a card, which are Kanban Zone's markers for a card standing in for work elsewhere.
Add Card Token Puts a token on a card.
Create Token Puts a token on a card through the standalone route, where every identifier including the card is an internal one.
Delete Token Takes a token off a card.

Webhooks

List Webhooks Returns a board's webhook subscriptions. Used to inspect or clean up hooks something else registered, since the trigger manages its own.
Get Webhook Returns one webhook.
Create Webhook Registers a webhook on a board. Deliveries are signed with the organization's webhook key, which is generated in Kanban Zone and has to be given to the receiving side separately.
Update Webhook Changes a webhook, which is also how one is turned on or off without deleting it.
Test Webhook Fires a synthetic delivery so the receiving side can be checked before real events arrive. It works even on a webhook that is turned off.
Delete Webhook Removes a webhook.

Triggers

1 triggers

Event Triggers

On Card Event Fires when a card on a chosen board is created, updated or moved. The trigger registers a webhook on the board while the flow is on and removes it when the flow is turned off, and it matches the board as well as the event so a flow watching one board does not fire on another board's cards. Set a webhook key in the connection to have deliveries verified; once a key is on record the check fails closed rather than waving an unsigned delivery through.

Frequently Asked Questions

What can FlowRunner do with Kanban Zone?

FlowRunner agents can run Get Authenticated Organization, Get Organization, and List Boards in Kanban Zone, plus 49 more actions.

Does connecting Kanban Zone to FlowRunner require OAuth?

No. Kanban Zone connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Kanban Zone trigger a FlowRunner workflow automatically?

Yes. Kanban Zone supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Kanban Zone

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us