Kantree

Kantree is a flexible work management platform from the French cooperative Digicoop, built on a model where everything is a card. Agents create and update cards, manage projects, groups and attributes, post comments and react to card changes as they happen.

1 trigger 139 actions API key available

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

On Project Event fires when something changes in the delivery project

Get Card reads the card, and Get Card Hierarchy places it in the board it belongs to

List Card Descendants reveals whether this card is a task or a nested body of work

List Card Attributes confirms the fields its model requires are actually filled in

Set Card Attribute and Switch Card Group record the classification and move the card

Create Card Comment records what the agent decided and the evidence behind it

Anything that would remove a card with descendants waits for a person to confirm

What This Integration Enables

Kantree, built by the French cooperative Digicoop and available self-hosted as well as hosted, makes one structural commitment and follows it everywhere: everything is a card. A task is a card, a board column's contents are cards, and a project is the children of a single top level card. Cards nest without limit, so the same object can be a checklist item today and a whole workstream next quarter, and Convert Card To Project exists precisely for the moment one outgrows the other. There is no create-in-project route, because creating a card in a project means creating it inside that project's top level card.

That model is what makes Kantree worth automating and what makes an agent's first job structural. FlowRunner agents read the hierarchy before they act on it, resolve a card's model to learn which attributes it carries, and use Kantree's own query language rather than paging through boards. They also work with the three-state model the product insists on, where a card is done, not done, or undecided, because not every card is a task. The one thing an agent should never assume is how large a card is, which is why human-in-the-loop sits in front of anything that removes one.

Without FlowRunner

Structure lost in the tool Nobody can say whether a card is a task or a whole workstream without opening it

Filters rebuilt every time The same question is retyped as a new filter whenever somebody needs the answer

Type changes made blind A field is added to a card type without anyone checking what else uses that type

With FlowRunner

Structure read before action Descendants and ancestors are checked so a workflow knows the size of what it is touching

Queries saved and reused Filters are validated once and run on a schedule, and the results reach people

Type changes reviewed Model edits are proposed with the count of cards they would reach, then approved

Use Case Scenarios

Intake that lands in the right place in the tree

A request arrives from Typeform or a thread in Slack. The agent resolves the destination with List Organization Projects and Get Project Board, then calls Create Card inside the parent card that represents the right area of the board. It reads List Card Attributes for the model that card carries, sets the classification and owner with Set Card Attribute, and uses Append To Card Attribute rather than Set Card Attribute when adding one assignee to a list that already has others. Set Card In Group places the card in the right column for each grouping the project uses, since a card belongs to one group per group type.
Saved questions instead of repeated exports

Kantree has a real query language, which changes what reporting looks like. The agent builds a filter once, calls Validate Query so a malformed expression fails before it matters, and then runs Query Project or Search Organization on a schedule. Overdue cards, cards in Undecided that have sat there too long, and cards whose required attributes are still empty all become a weekly digest written into Google Sheets and summarized where the team reads it. Where somebody asks a question in plain language, Ask Question turns it into a filter the agent can validate and reuse rather than a one-off answer.
Time and expense captured as structured logs

Kantree records time and expenses as logs, structured entries whose shape comes from a log type rather than free text in a comment. The agent creates a log against the card when work is completed elsewhere, reads List Card Logs to total effort per card, and walks Get Card Hierarchy so those totals roll up to the workstream and the project above it. Because the entries are structured, the roll-up is arithmetic rather than interpretation, and the monthly review reads from the same records the team was already keeping.

Human-in-Loop Highlight

Delete Card is dangerous here for a reason specific to Kantree's model. Cards nest without limit and the API gives a task and a sub-board the same shape, so the card an agent is about to remove may be a single checklist item or may be a quarter of work with fifty cards, their attributes, their logs and their comments nested underneath it. Deletion takes all of it, permanently, and nothing in the card itself warns you which of the two you have. So a cleanup agent always reads first and never deletes on its own. It calls List Card Descendants and Get Card Hierarchy, then posts to the project owner: "Card KT-318, Legacy import, is marked Undecided and has had no activity for 5 months. It has 22 descendants, including 3 cards still in Not Done, 14 logs totalling recorded time, and 9 comments. Deleting it removes all of that permanently. Archive it instead, convert it to its own project, or delete it?" The owner answers. Archiving is what the agent proposes, because archived cards stay readable, and deletion is the one answer only a person gets to give.

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

139 actions

Account

Get Current User Retrieves the account the API key belongs to. Every operation runs as this person with their permissions, so this is the first call in most flows.
Get Current User Full Retrieves the signed-in account with its organizations, settings and preferences attached. Heavier, and worth it when a flow needs the whole context at once.
Ping Checks that the key and the host are both working. The guard at the start of a flow that must not proceed on a broken connection.
List Notifications Retrieves the signed-in person's notifications.
Clear Notifications Clears the whole notification list at once, because Kantree publishes no route to dismiss just one.
Get Unread Notification Count Retrieves how many notifications are waiting without reading them.
List Favorites Retrieves the cards, projects and views the signed-in person has starred.
List Pins Retrieves the cards the signed-in person has pinned for quick access.
List Reminders Retrieves every reminder set for the signed-in person, across all projects.
Get Inbox Retrieves the items waiting on the signed-in person.
List API Keys Retrieves the keys on the signed-in account. Treat anything it returns as a credential rather than as data to pass around.

Organizations

List Organizations Retrieves the organizations the signed-in person belongs to. An organization owns projects, models and roles.
Get Organization Retrieves one organization by its identifier.
Create Organization Creates an organization. On a paid plan this can affect what the account is billed for.
Update Organization Renames an organization.
Delete Organization Permanently deletes an organization with every project, card and attachment it owns.
List Organization Members Retrieves the people in an organization with their roles.
Remove Organization Member Removes somebody's access. What they created stays behind.
List Organization Invites Retrieves invitations that nobody has accepted yet.
Invite To Organization Invites people by email address. Real invitation mail, and accepting one can consume a paid seat.
Set Organization Invite Link Turns the shareable invite link on or off. While it is on, anybody holding the link can join.
List Organization Projects Retrieves the projects in an organization.
List Organization Teams Retrieves the teams in an organization, which group people so a project can be shared with all of them at once.

Teams

Create Team Creates a team inside an organization.
Get Team Retrieves one team by its identifier.
Update Team Renames a team.
Delete Team Deletes a team. The people in it keep their organization membership.
List Team Members Retrieves the people in a team.
Set Team Member Adds an organization member to a team or takes them out, addressed by the membership identifier rather than the user's.

Organization Roles and Models

List Organization Roles Retrieves the roles defined in an organization, each a named set of permissions.
List Organization Models Retrieves the card models defined at organization level. A model is a card type and decides which attributes a card carries.
Search Organization Searches within one organization using the query language. Narrower than the account-wide search.

Projects

List Projects Retrieves the projects the signed-in person can reach. A project is a board, and everything inside it is a card.
List All Projects Retrieves every reachable project including the archived ones the ordinary listing leaves out.
List Shared Projects Retrieves the projects shared with the signed-in person rather than owned by their own organizations.
Get Project Retrieves one project. Kantree project identifiers are opaque strings rather than numbers, so a workflow keeps them as text.
Create Project Creates a project, optionally inside an organization and optionally from a template.
Update Project Updates a project's title, color, visibility and behavior settings.
Delete Project Permanently deletes a project with every card inside it. Archiving is the answer when the work is simply finished.
Set Project Archived Archives a project or brings it back. Archived projects stay readable.
Copy Project Duplicates a project, optionally into a different organization. The fast path for a repeatable engagement shape.
Get Project Board Retrieves a project's board with its groups and the cards inside them, which is what the interface itself loads.
List Project Cards Retrieves a project's cards, optionally narrowed by a query language filter, with a lighter summary mode for large boards.
Get Project Card By Reference Retrieves a card by the short reference people see in the interface rather than by its internal identifier. The bridge between a human mentioning a card and a workflow finding it.
Query Project Runs a query language expression against one project and returns what matches.

Project Members

List Project Members Retrieves the people on a project, optionally with the role each holds.
Add Project Member Adds somebody to a project, optionally with a role.
Update Project Member Changes the role somebody holds on a project.
Remove Project Member Removes somebody from a project. The cards they created stay.
Invite To Project Invites people to a project by email address, which sends real invitation mail.
Set Project Membership Joins the signed-in person to a project or leaves it, where the project's settings allow it.

Project Structure

List Project Activities Retrieves a project's activity feed, which answers what changed and who changed it.
List Project Files Retrieves the files attached anywhere in a project.
Get Project File Retrieves one attached file's details.
List Project Group Types Retrieves a project's group types. A group type is a whole way of grouping the board, such as status or assignee, and a project can carry several at once.
Create Project Group Type Adds a group type, giving the board another way to be organized.
Delete Project Group Type Removes a group type along with the groups under it. The cards themselves stay.
List Project Views Retrieves a project's saved views: filter, grouping and display mode combinations people switch between.
Create Project View Saves a view on a project.
Delete Project View Removes a saved view. The cards it showed are untouched.
List Project Automations Retrieves the automation rules configured on a project.
Trigger Project Automation Runs one of those rules on demand rather than waiting for whatever normally sets it off.
List Recurring Cards Retrieves the rules that create the same card again on a schedule.
List Card Templates Retrieves the prefilled cards people start from.

Cards

Get Card Retrieves one card. In Kantree a task, a column's contents and a project's top level are all cards.
Create Card Creates a card inside another card. There is no create-in-project route, so a project's top level card is the parent for a top level card.
Update Card Updates a card's title, color, state or default child model.
Delete Card Permanently deletes a card and everything nested inside it. The operation this page's human gate exists for.
Set Card State Marks a card done, not done or undecided. Kantree keeps three states because not every card is a task.
Set Card Archived Archives a card or brings it back. Archived cards stay readable through the listings that ask for them.
Move Card Moves a card to a different parent, group or position. How progress is recorded, since a board column is a group.
Copy Card Duplicates a card, optionally into a different parent or group.
Convert Card To Project Turns a card and everything inside it into a project of its own, for the moment a task outgrows being a task.
List Card Children Retrieves the cards directly inside a card.
List Card Descendants Retrieves everything nested below a card at any depth. The read that tells a workflow how large the thing it is about to touch really is.
Get Card Hierarchy Retrieves a card's ancestors up to the project's top level, which is how a deeply nested card is placed.
Get Card History Retrieves a card's change history.
List Card Activities Retrieves the activity feed of one card.

Card Attributes

List Card Attributes Retrieves a card's attribute values. Which attributes a card has is decided by its model.
Get Card Attribute Retrieves one attribute on a card with its definition as well as its value.
Get Card Attribute Value Retrieves just the value of one attribute, without its definition.
List Card Attribute Choices Retrieves the values an attribute will accept, for attributes that are a fixed list.
Set Card Attribute Sets an attribute's value, replacing whatever was there.
Append To Card Attribute Adds a value to a list attribute without disturbing the rest. How one assignee or one label is added rather than replacing the set.
Pop From Card Attribute Removes a value from a list attribute, leaving the rest alone.
Clear Card Attribute Clears a card's value for an attribute. The attribute stays defined on the model.

Card Comments

List Card Comments Retrieves the comments on a card.
Create Card Comment Adds a comment attributed to the account behind the key. Where an agent records what it decided and why.
Get Card Comment Retrieves one comment on a card.
Update Card Comment Rewrites a comment.
Delete Card Comment Permanently deletes a comment from a card.
Pin Card Comment Pins a comment to the top of a card's discussion.
Get Pinned Card Comment Retrieves the pinned comment, if there is one.
Unpin Card Comment Unpins whichever comment is pinned. Kantree unpins by card, so no comment identifier is needed.

Card Groups

List Card Groups Retrieves the groups inside a card. A group is what a board column or swimlane actually is.
Create Card Group Adds a group to a card, which is how a column is added to a board. The group type decides which grouping it belongs to.
Get Card Group Retrieves one group by its identifier.
Update Card Group Changes a group's title, color, limit or the state it applies to cards moved into it.
Delete Card Group Removes a group, which is how a column is taken off a board.
Set Card Group Archived Archives a group or brings it back, hiding a column without losing what is in it.
List Group Cards Retrieves the cards in one group, which is how a single column is read.
Set Group Cards State Sets the state of every card in a group at once. A write that reaches an entire column, so read what is in it first.
Set Card In Group Adds a card to a group or takes it out. A card belongs to one group per group type at a time.
Switch Card Group Moves a card from its current group to another of the same type in one call.

Card Logs

List Card Logs Retrieves the logs on a card. A log is Kantree's structured entry for things like time spent or an expense.
Create Card Log Records a log on a card. The attributes it carries come from the log type, so this is structured capture rather than a comment.
Get Card Log Retrieves one log entry.
Update Card Log Changes a log entry's values or date.
Delete Card Log Permanently deletes a log entry. Whatever it recorded comes off every total that included it.

Card Reminders and Personal Flags

List Card Reminders Retrieves the reminders set on a card.
Create Card Reminder Sets a reminder on a card for one or more people, which will notify real people at the time you set.
Delete Card Reminder Removes a reminder before it fires.
Set Card Favorite Stars a card for the signed-in person, or removes the star.
Set Card Pinned Pins a card for the signed-in person, or unpins it.
Set Card Subscription Subscribes the signed-in person to a card's notifications, or unsubscribes them.

Models

List Models Retrieves the card models available to the signed-in person. A model decides which attributes a card of that type carries.
Get Model Retrieves one model by its identifier.
Create Model Creates a card model, shared across an organization or kept local to one project.
Update Model Changes a model's name, color or indicator. A model is shared, so this reaches every card already using it.
Delete Model Deletes a card model. Check what still uses it first, because a model spans every card of that type.
Copy Model Duplicates a model, which is how one board's card type is reused on another.
List Model Attributes Retrieves the attributes a model defines: the custom fields every card of that model carries.
Create Model Attribute Adds an attribute to a model. Every card already using the model gains the field.
Delete Model Attribute Removes an attribute from a model, taking the field off every card using it along with whatever was stored there.
List Attribute Types Retrieves the attribute types the account supports, which is the vocabulary a new attribute is built from.

Search

Search Searches everything the signed-in person can see using the query language, with an identifiers-only mode for large workspaces.
Validate Query Checks a query language expression before a flow relies on it, which matters most when the filter is built from user input.
Ask Question Turns a question in plain language into a query language filter using the account's own assistant.
List Query Functions Retrieves the functions the query language offers, which is the vocabulary a filter can use.

Roles

List Roles Retrieves the roles the signed-in person can see.
Get Role Retrieves one role with its permissions.
Create Role Creates a role in an organization.
Delete Role Deletes a role. Check who holds it first, because their permissions change the moment it goes.
List Available Role Actions Retrieves every permission a role can be given.

Webhooks

List Webhooks Retrieves a project's webhooks. Read this to find a stale subscription or one a trigger left behind.
Get Webhook Retrieves one webhook by its identifier.
Create Webhook Subscribes an address to a project's events. Kantree groups events by kind rather than naming them individually.
Update Webhook Changes a webhook's address, events or active state.
Delete Webhook Removes a webhook from a project so it stops delivering.

Triggers

1 triggers

Event Triggers

On Project Event Fires when something happens in the chosen Kantree project. Kantree subscribes by kind of event rather than by named event, so the subscription takes something like cards rather than a specific event name, and the exact event arrives with each delivery for the flow to branch on. Kantree publishes no signature or shared secret for webhook deliveries, so the callback address is what keeps the flow private, which is a reason to treat a delivery as a prompt to read the card back rather than as evidence in itself.

Frequently Asked Questions

What can FlowRunner do with Kantree?

FlowRunner agents can run Get Current User, Get Current User Full, and Ping in Kantree, plus 136 more actions.

Does connecting Kantree to FlowRunner require OAuth?

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

Can Kantree trigger a FlowRunner workflow automatically?

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

Start building with Kantree

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us