KanbanFlow

KanbanFlow pairs a WIP-limited kanban board with a built-in Pomodoro timer and stopwatch. Agents create and move tasks, manage subtasks, labels and dates, read time entries and start flows when board events fire.

1 trigger 69 actions API key available

KanbanFlow website Platform Documentation Capability data verified 2026-08-18

On KanbanFlow Event fires when a task moves into the review column

Get Task reads the card with its subtasks, labels, dates and custom fields

List Subtasks confirms every checklist item is ticked before the card is treated as ready

List Task Manual Time Entries confirms the work carries logged time against it

Add Comment records what the agent verified and what it found missing

The reviewer is named through Add Collaborator so the card appears in their view

Anything leaving this board for another one waits for a person to confirm the destination

What This Integration Enables

KanbanFlow makes a commitment most board tools avoid: a token is issued from inside one board, and every route resolves against that board and no other. There is no board identifier in any path and no route that lists boards. So a FlowRunner connection here is a connection to one board, columns and swimlanes and users are board-scoped by construction, and a workflow that spans two boards is deliberately a workflow with two connections. That constraint is worth understanding because it is also a safety property: an agent cannot wander into a board it was not given.

The other thing that shapes automation here is that KanbanFlow tracks time in three shapes. Manual entries are the only kind the API can create or edit, while stopwatch and Pomodoro sessions can be read and deleted but not written, and a single session can span several tasks. FlowRunner agents create and move tasks, manage subtasks, labels, dates, collaborators, comments and attachments, and record time as manual entries against the task that earned it. Where a write reaches past the board the connection covers, FlowRunner's human-in-the-loop gate is what stands in the way.

Without FlowRunner

Reviews start with questions The reviewer opens the card and works out for themselves whether it is actually ready

Time logged from memory Hours get entered days later, or not at all, and the board's totals stop meaning anything

Board hopping by hand Moving work to another team's board means recreating the card and losing its history

With FlowRunner

Cards arrive pre-checked Subtasks, dates and logged time are verified before the card reaches a reviewer

Time recorded as work happens Manual entries are written against the task from the system where the work was done

Cross-board moves with a witness A move that takes a card off this board is proposed, confirmed, then executed

Use Case Scenarios

A definition of done the board actually enforces

When a card lands in the review column, the trigger fires and the agent reads it back with Get Task. It walks List Subtasks to confirm the checklist is complete, reads List Task Dates to see whether the card missed its deadline for reaching this column, and reads List Task Manual Time Entries to confirm somebody actually logged the work. If anything is missing, Move Task returns the card to the previous column and Add Comment says exactly what was outstanding. If everything checks out, Add Collaborator brings in the reviewer and a message goes to Slack. The reviewer's first question stops being whether this card is ready.
Time that arrives while the work is still fresh

An engineer closes a pull request in GitHub or finishes a session in another tool. The agent resolves the task on the board with Search Tasks, then calls Add Manual Time Entry with the real start and end timestamps, credited to the right user. It uses the manual entry rather than the deprecated total seconds field on the task, because KanbanFlow ignores a decrease to that field outright and turns an increase into a manual entry anyway. At the end of the week, List Board Time Entries gives a complete picture across manual, stopwatch and Pomodoro sessions, and the summary lands in Google Sheets.
An audit answer that does not depend on memory

Somebody asks why a card's estimate changed. List Task Events is the only place that answer lives, because each entry records the old and the new value of every property that changed, along with who changed it. The agent pulls the task's history, pairs it with List Board Events for the same window, and writes a short account of what moved and when. Because a call returns at most one hundred entries, the agent walks the window with its from and to bounds rather than assuming one page is the whole story.

Human-in-Loop Highlight

Move Task To Another Board is the only operation in this connector that reaches beyond the board the connection belongs to, and it is built out of the two permissions that matter most. The source token needs the delete tasks permission, because the card leaves this board, and the destination token needs the create tasks permission. There is no route anywhere in this API that lists boards, so the agent cannot show anybody the destination by name. It has a second token and a promise about where that token points. That is not enough certainty for a one-way move, so the agent does not make it alone. It posts: "Card 412, Migrate billing webhooks, has been in Blocked for 11 days with 6 hours logged and 3 collaborators. The platform team has asked for it. Moving it removes it from this board and it cannot be moved back without a token from their side. Move it into their first column, or leave it here and add them as collaborators instead?" The board owner answers, and the card only crosses the boundary when somebody who knows both boards says it should.

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

69 actions

Connection and Board

Verify API Token Reads the board the token belongs to and reports which board this connection actually covers, along with its columns and swimlanes. The first call on any new connection.
Get Board Returns the board's structure: every column and swimlane with its identifier and description, plus any custom color names the board defines. Almost every write needs an identifier from here.
Get Users Returns everyone with access to the board with their identifier, name and email. These identifiers are what assignments, collaborators, subtasks and time entries expect, and there is no other way to look them up.
Get Board Custom Fields Returns the board's custom field definitions with their types, which is what tells a workflow whether a field takes text or a number.
Get Rate Limit Status Reports how much of the request quota is left. KanbanFlow locks a token outright after enough requests in a day, so a flow that loops over tasks checks this rather than discovering the ceiling by being cut off.

Events

List Board Events Returns the board's audit history with the acting user and the old and new value of every changed property, up to one hundred entries per call.
List Task Events Returns one task's audit history. The only way to see what a task looked like before an edit.

Tasks

Get Task Returns one task with its column, swimlane, estimates, dates, subtasks, labels, collaborators and custom fields. Empty collections are omitted rather than returned empty.
List All Tasks Returns every task on the board, grouped by column and swimlane and also flattened with the names carried onto each row. Watch the truncated flag, because a date grouped column returns only part of its contents.
List Tasks By Column Returns the tasks in one column, named by identifier, by name or by index. A date grouped column pages through its cap with the returned next task identifier.
List Tasks By Swimlane And Column Returns the tasks in the single cell where a swimlane and a column meet. The paging call for a truncated date grouped column.
Search Tasks Finds tasks by name, description, color, responsible user or label. KanbanFlow has no search route, so this reads the board once and filters here, which costs one request and inherits the board read's own cap.
Create Task Creates a task and returns its identifier. A name and column are required, a swimlane too on a board that has them, and position accepts top, bottom or an index.
Update Task Updates the properties supplied. Clearing a field takes an explicit empty value rather than an omission, so leaving the assignee out keeps the current one.
Move Task Moves a task to another column, swimlane or position on the same board. A column that groups by date needs a grouping date, or the task is filed under today.
Set Task Color Sets a task's color. KanbanFlow boards use color as their main way of typing work, and a board can name its own colors on top of the ones the API accepts.
Assign Task Sets or clears the responsible user. Clearing works here because the operation sends an explicit null rather than omitting the property.
Delete Task Permanently deletes a task with its subtasks, labels, comments and attachments. The token needs the delete permission, which is granted separately from create and update.
Move Task To Another Board Moves a task to a different board using a second token issued from that board. The only operation that reaches past this connection, and the one this page's human gate exists for.

Subtasks

List Subtasks Returns a task's subtasks in board order. Subtasks have no identifiers, so read this immediately before any write that addresses one.
Create Subtask Adds a subtask and returns the index it landed at, optionally assigned and with a due date.
Update Subtask By Index Updates the subtask at a zero based position. An index shifts whenever one above it is added or removed.
Update Subtask By Name Updates the subtask with an exact name. The comparison is case sensitive, and a mismatch is reported as missing rather than resolved loosely.
Delete Subtask By Index Removes the subtask at a position. Everything below shifts up, so deleting several by index works from the bottom up.
Delete Subtask By Name Removes the subtask with an exact, case sensitive name. With two identically named subtasks it removes one, so prefer index there.

Labels

List Task Labels Returns a task's labels with their pinned state. Labels belong to the task rather than the board, so there is no board wide list and no identifier.
Create Task Label Adds a label to a task. A pinned label stays visible on the card face rather than only in the detail view.
Update Task Label Renames a label or changes whether it is pinned, found by its exact case sensitive current name.
Delete Task Label Removes a label from one task. Nothing board wide changes, because the label is not a board object.

Dates

List Task Dates Returns a task's due dates. A KanbanFlow due date is a deadline for reaching a particular column, so a task can hold several at once, each with its own status.
Set Task Date Creates or replaces the due date for one target column. Calling it again for the same column overwrites rather than adding a second.
Delete Task Date Removes the due date a task holds for one target column.

Collaborators

List Collaborators Returns a task's collaborators as user identifiers, which is how KanbanFlow expresses shared ownership alongside the single responsible user.
Add Collaborator Adds a user as a collaborator on a task. The step that puts a card in a reviewer's view.
Delete Collaborator Removes a collaborator without touching the responsible user, which is a separate field.

Comments

List Comments Returns a task's comments oldest first with author and timestamp. Unlike subtasks and labels, comments do have identifiers.
Add Comment Adds a comment, attributed to the token owner unless an author is given and stamped now unless a timestamp is given, which is what makes importing a discussion possible.
Update Comment Edits a comment. Author and timestamps can be rewritten too, so a migration can preserve original attribution.
Delete Comment Permanently removes a comment from a task.

Attachments

List Attachments Returns a task's attachments with name, size, type and link. Files stored at KanbanFlow carry a temporary link with an expiry, while third party attachments link to the provider.
Get Attachment Link Returns one attachment's metadata and link without downloading anything. The right call for files held at another provider.
Add Attachment Uploads a file to a task from a URL. Give a file name when the URL does not end in a usable one.
Download Attachment Downloads an attachment stored at KanbanFlow into FlowRunner file storage. It refuses a third party attachment rather than saving a share page as though it were the file.
Delete Attachment Removes an attachment from a task. For a file stored at KanbanFlow this deletes the file; for a third party attachment it only removes the link.

Relations and Custom Fields

List Task Relations Returns how a task relates to others, and is the only place the API mentions another board at all. Relations are read only here and have to be created in the interface.
List Task Custom Fields Returns the custom field values set on a task. A field never given a value is absent rather than empty.
Set Task Text Custom Field Sets a text or dropdown custom field, replacing any value there. A dropdown value has to be one of the board's own options.
Set Task Number Custom Field Sets a number custom field, replacing any value there. Decimals are accepted.
Delete Task Custom Field Clears a task's value for a custom field. The field stays defined on the board.

Time Tracking

List Board Time Entries Returns manual, stopwatch and Pomodoro time across the board inside a window, optionally for one user. An entry that merely overlaps the window is included.
List Task Time Entries Returns every kind of time entry recorded against one task, with no window needed.
List Manual Time Entries Returns manually logged entries across the board inside a window. Manual entries are the only kind this API can create or edit.
Get Manual Time Entry Returns one manual entry with its start, end, author, task and any comment or labels.
List Task Manual Time Entries Returns the manual entries recorded against one task, with no window needed.
Get Task Manual Time Entry Returns one manual entry through the task it belongs to, which also verifies it really is on that task.
Add Manual Time Entry Logs time against a task between two timestamps. The supported way to record time, credited to the token owner unless a user is given.
Update Manual Time Entry Changes an entry's start, end, comment or labels, and recalculates the time spent on the related task.
Delete Manual Time Entry Removes a manual entry and reduces the task's recorded time to match.
Delete Task Manual Time Entry Removes a manual entry through the task it belongs to, verifying it is on that task first.
List Stopwatch Entries Returns stopwatch sessions inside a window. A running stopwatch can be moved between tasks, so a session records the parts it covered.
Get Stopwatch Entry Returns one stopwatch session with every task it covered and when each part stopped.
Delete Stopwatch Entry Removes a stopwatch session and reduces the time on every task it covered, which can be several at once.
List Pomodoro Entries Returns Pomodoro sessions inside a window, with target length, whether the session earned a point and any interruption reason.
Get Pomodoro Entry Returns one Pomodoro session with its parts and details.
Delete Pomodoro Entry Removes a Pomodoro session and reduces the time on every task it covered.

Web Hooks

Create Web Hook Registers a webhook on the board and returns the signing secret, which KanbanFlow shows only once. The callback has to answer an HTTP HEAD request before it is accepted, and a board holds a limited number of hooks in total.
Update Web Hook Changes a webhook's name, callback, events or filter. The signing secret is not rotated here, so an existing receiver keeps verifying with the secret it holds.
Delete Web Hook Removes a webhook so it stops delivering. KanbanFlow publishes no route that lists webhooks, so a lost identifier has to be found in the board settings.
Verify Webhook Signature Checks that a delivery really came from KanbanFlow for a webhook registered by hand rather than by the trigger, using a constant time comparison against the signature header.

Triggers

1 triggers

Event Triggers

On KanbanFlow Event Fires when a task or a task comment changes on the board. One trigger becomes one KanbanFlow webhook carrying every event chosen, and the optional column, swimlane and changed property filters are applied by KanbanFlow before it delivers. The FlowRunner callback answers an HTTP HEAD request with a success status, because KanbanFlow refuses to register a webhook it cannot reach that way, and a board holds at most twenty webhooks counting any created by hand.

Frequently Asked Questions

What can FlowRunner do with KanbanFlow?

FlowRunner agents can run Verify API Token, Get Board, and Get Users in KanbanFlow, plus 66 more actions.

Does connecting KanbanFlow to FlowRunner require OAuth?

No. KanbanFlow connects to FlowRunner with an API key, no OAuth flow required.

Can KanbanFlow trigger a FlowRunner workflow automatically?

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

Start building with KanbanFlow

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us