Kanban Tool

Kanban Tool is kanban boards with swimlanes, card types, subtasks and built-in time tracking from a Polish vendor. Agents create and move cards, manage subtasks and comments, log time and read board state to keep work visible.

31 actions API key available

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

An escalation arrives from the helpdesk and needs to become work on a board

Agent reads the request and resolves the destination with List Boards

Search Tasks runs a narrow query to see whether this work already exists as a card

Create Task places a new card on the right workflow stage with tags and an estimate

Create Subtask adds the checks the team runs on every escalation of this kind

Create Comment attaches the source thread so the assignee does not go hunting for it

The board owner confirms priority and assignee before the card counts against the column

What This Integration Enables

Kanban Tool is a board for teams who want the card to hold everything: subtasks, comments, attachments and tracked time all live on the task rather than in a companion tool. That design shows up in the API, which publishes almost no list endpoints. Subtasks, comments, attachments and time trackers are fields on their parent, not collections of their own, so reading them means reading the whole object. FlowRunner agents work with that grain rather than against it. They use Search Tasks, the one real listing the API has, to ask narrow questions, and they reach for the heavy reads only when a workflow genuinely needs the full card.

The other thing worth knowing about this board is that it forgives. Archive, unarchive, delete and restore are all states on an ordinary task update, and the vendor is explicit that a task is never permanently removed. So the exposure here is not destruction. It is scope: an agent acting on a query result acts on every card that query matched, and the only account of what it touched afterwards is the board changelog. That is exactly where FlowRunner's human-in-the-loop discipline belongs, and it is why the agent shows the match set before it acts on it.

Without FlowRunner

Board as a second job Someone retypes escalations into cards, and the board lags the real queue by a day

Search by scrolling Finding whether work already exists means reading columns instead of asking a question

Cleanup by hand Stale cards accumulate until a person spends an afternoon archiving them one at a time

With FlowRunner

Cards arrive already formed The escalation becomes a card with its stage, tags, estimate and context attached

Queries instead of scrolling Agents ask the board directly by assignee, tag, name or identifier before creating anything

Sweeps with a named scope A cleanup pass shows exactly which cards it matched, and a person approves the set

Use Case Scenarios

Escalations become cards without a person retyping them

A ticket in Zendesk crosses the threshold that means engineering has to look at it. The agent resolves the destination board with List Boards, then runs Search Tasks with the ticket's external identifier to check the work is not already on the board. If it is not, Create Task opens a card on the triage stage with the customer's tag, a time estimate in seconds and the ticket reference stored as the external identifier. Create Subtask adds the reproduction steps as a checklist, and Create Comment carries over the customer's own words. The card that reaches the standup is already complete.
A change feed nobody has to poll by hand

Kanban Tool has no trigger, but List Board Changelog pages by identifier rather than page number, which makes it a usable feed. On a schedule, the agent reads the changelog with After set to the highest identifier it saw last time, and turns what it finds into signals other systems care about. A card that entered the Done stage posts a note to the delivery channel in Slack. A card that gained a customer tag appends a row in Google Sheets. The board stays the system of record, and the reporting stops depending on somebody remembering to export it.
Time on the card, hours in the ledger

When an engineer starts work, the agent calls Create Time Tracker against the task with the end left open, which is how Kanban Tool records a running timer. When the card moves to Done, Update Time Tracker closes it. At the end of the week, the agent reads List Time Trackers and Get Task Details for each tracked card, groups the time by customer tag, and posts a summary for review before any of it becomes a bill.

Human-in-Loop Highlight

The risky operation on this board is not Set Task State on its own. Delete is a soft delete and Restore always works, so a single wrong card is a small mistake. The expensive version is a sweep: an agent handed a query like tags:"external work" with a stale date filter can archive or delete every card that matched it, and because Kanban Tool restores one card at a time, unwinding that means reconstructing the blast radius from List Board Changelog first. So the cleanup agent never runs the sweep it planned. It runs Search Tasks, counts the matches, and posts to the board owner: "This query matches 47 cards across 3 boards, including 6 in the In Progress stage and 4 with time tracked this week. Archive all 47, or exclude the in-progress cards?" The owner answers, the agent applies Set Task State to the approved set and records the identifiers it touched. The agent picked the cards. The person decided the scope.

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

31 actions

Connection and People

Verify API Token Confirms the domain and token together by reading the account behind them and reporting how many boards it can reach. The first call in any new connection.
Get Current User Returns the account the token belongs to, including the boards it can reach and the time trackers it owns. Kanban Tool answers several questions through this one object, so most flows start here.
Get User Returns one user by identifier. Used to resolve an assignee before a card is created or reassigned.

Boards

List Boards Returns the boards this account can reach, projected out of the current user record. The step that turns a board name in a request into an identifier the rest of the workflow can use.
Get Board Returns a board's own record: its name, settings, card types and workflow stages, without the tasks. Used to map an incoming status onto a real stage.
Get Board Details Returns the board together with its swimlanes, stages, card types and every task on it. The heavy read, used when a workflow genuinely needs the whole picture.
List Board Tasks Returns the tasks on a board by reading the board and projecting them out. Useful for a full reconciliation pass, and expensive enough that Search Tasks is the better default.
List Board Changelog Returns who changed what and when, paged by identifier through Before and After. This is the mechanism a polling workflow is built on, and the record a reviewer reads after a bulk change.
Search Tasks Finds tasks using Kanban Tool's own query syntax across text, name, assignee initials, tags, identifier, priority and external identifier. The cheap listing, and the call that resolves the match set before any sweep.

Tasks

Get Task Returns one task's own record: name, description, board, stage, assignee, estimates and dates. Used when a workflow needs the card's own fields and nothing more.
Get Task Details Returns the task with its subtasks, comments, attachments, collaborators, changelogs and time trackers. The only way to reach those collections, and worth spending when a decision depends on them.
Create Task Creates a card on a board, with the stage and swimlane defaulting to the board's first. Tags go on as one comma separated string and the time estimate is in seconds.
Update Task Updates the properties supplied and leaves the rest alone. Moving a card between columns or swimlanes happens here, by giving it a new workflow stage or swimlane.
Set Task State Archives, unarchives, deletes or restores a card. All four are states on an ordinary update rather than separate routes, and the delete is a soft delete that Restore reverses.

Subtasks

List Subtasks Returns a task's subtasks by reading the task and projecting them out. Read this immediately before any write that depends on the current order.
Create Subtask Adds a subtask, optionally assigned to somebody in its own right and optionally already checked.
Update Subtask Updates a subtask's text, assignee or checked state. The call that ticks an item off without rewriting it.
Delete Subtask Removes a subtask from its task, soft-deleted the way tasks are.
Reorder Subtasks Sets the complete order of a task's subtasks in one call. The list you send is the whole new order, so read the current one first and rearrange it rather than sending a partial list.

Comments

List Comments Returns a task's comments by reading the task and projecting them out.
Create Comment Adds a comment attributed to the account behind the token. Used to carry source context onto a card where the assignee will actually read it.
Delete Comment Removes a comment from a task, soft-deleted like everything else here.

Attachments

List Attachments Returns the files attached to a task by reading the task and projecting them out.
Create Attachment Uploads a file from a URL and binds it to a task or a board using Kanban Tool's own reference syntax, built for you from the kind and identifier you choose.
Detach Attachment Unbinds an attachment from a task or board without deleting the file. Leaving the record empty detaches it everywhere.
Set Attachment Mode Decides how an attachment appears on the card: pinned, used as the cover, both, or neither. Stored by Kanban Tool as flags in a single integer and offered here as the four named combinations.
Download Attachment Downloads one of a task's attachments into FlowRunner file storage and returns its URL, so a later step can read or forward the file.

Time Tracking

List Time Trackers Returns the time trackers belonging to the account behind the token, projected out of the user record because the API offers no other route to them.
Create Time Tracker Records a stretch of time against a task, or starts a running timer by leaving the end open. Both the board and the task are required.
Update Time Tracker Changes a tracker's start, end, position or listing. Setting the end on a running timer is how it stops.
Delete Time Tracker Removes a time tracker and the hours it recorded. Used in correction passes, and worth reviewing before it runs against anything already reported.

Frequently Asked Questions

What can FlowRunner do with Kanban Tool?

FlowRunner agents can run Verify API Token, Get Current User, and Get User in Kanban Tool, plus 28 more actions.

Does connecting Kanban Tool to FlowRunner require OAuth?

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

Can Kanban Tool trigger a FlowRunner workflow automatically?

Kanban Tool doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Kanban Tool

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us