--- title: "AgilePlace Integration" description: "Planview AgilePlace, formerly LeanKit, runs enterprise Kanban boards that connect strategy to delivery. Agents create and move cards, manage lanes and boards, log comments and attachments, and react to board events as they happen." url: https://flowrunner.ai/integrations/agileplace date_modified: 2026-09-04T14:21:17-07:00 --- # AgilePlace [Project Management](https://flowrunner.ai/integrations/category/project-management-productivity) Planview AgilePlace, formerly LeanKit, runs enterprise Kanban boards that connect strategy to delivery. Agents create and move cards, manage lanes and boards, log comments and attachments, and react to board events as they happen. 1 trigger · 105 actions · API key · available [AgilePlace website](https://acme.leankit.com/) · [Platform Documentation](https://www.planview.com/products-solutions/products/agileplace/) · Capability data verified 2026-08-18 1. A release finishes in the deployment pipeline 2. Agent reads the release manifest and resolves the cards it covers 3. List Cards confirms which of those cards are still sitting in the lane the release should clear 4. Get Lane Card Counts checks the destination lane against its work in progress limit 5. Create Card Comment records the release reference on each matched card 6. Agent posts the matched set and the custom event it intends to fire to the board owner 7. The board owner confirms the scope, and only then does Initiate Board Event run ## What This Integration Enables Planview AgilePlace, the product formerly called LeanKit, is enterprise Kanban for organizations where the board is governed rather than improvised. That shows up in its API. Alongside the card operations you would expect, it exposes lane work in progress limits, board access roles, parent and child connections that roll statistics up an initiative, dependencies that order work in time, planning series and increments for program-level cadence, and the board's own card automations. Roughly half of the surface is about who may change the board and how, not about individual cards. FlowRunner agents work both halves. They create and move cards from the systems where work actually originates, connect delivery cards to the initiative above them so a roll up is read rather than assembled, and record dependencies as they are discovered instead of at planning time. They also reach the administrative operations, which is precisely where FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) discipline matters: several AgilePlace operations rewrite an entire board in one call, and those pause for a person. Every action here is built and verified against the AgilePlace API. ### Without FlowRunner **Boards updated after the fact**: Cards move on Friday to describe work that shipped on Tuesday, so the board reports history rather than state **Roll ups assembled by hand**: Someone opens each child card to answer how a parent initiative is actually tracking **Board changes with no review step**: A tag cleanup or an access change is made by whoever noticed the problem, and nobody sees the blast radius first ### With FlowRunner **Board reflects the pipeline**: Deployment and incident systems push cards forward as the work actually moves **Roll ups read from the connections**: Parent initiatives report started, finished and blocked counts pulled straight from their children **Sweeping changes get a named owner**: Anything that touches a whole board arrives as a proposal with the affected count attached ## Use Case Scenarios ### The board keeps pace with the pipeline A build finishes in [GitHub](https://flowrunner.ai/integrations/github). The agent resolves the release manifest to the cards it covers with List Cards, comments the release reference onto each with Create Card Comment, and calls Move Cards to advance them into the deployed lane. Before it moves anything it reads Get Lane Card Counts against the lane's work in progress limit, so a release that would overfill the lane is reported rather than forced. A digest of what moved posts to [Slack](https://flowrunner.ai/integrations/slack). Nobody spends Friday reconciling the board against the deployment log. ### Initiative roll ups that read themselves Delivery cards on team boards are connected under initiative cards on a portfolio board with Connect Cards. On a schedule, the agent calls Get Connection Statistics for each initiative to read how many children are started, finished or blocked, and their sizes, then pairs that with List Card Dependencies to find work that is waiting on something outside its own board. Anything blocked past a threshold posts into [Microsoft Teams](https://flowrunner.ai/integrations/microsoft-teams) with the blocking card named. The portfolio review opens with the exceptions rather than with a status round robin. ### Incidents that land as cards with the evidence attached An alert fires in [PagerDuty](https://flowrunner.ai/integrations/pagerduty) and the investigation trail accumulates in [Sentry](https://flowrunner.ai/integrations/sentry). The agent calls Create Card on the incident board, uses Upload Card Attachment to put the stack trace and the timeline on the card, and Assign Card Members to add the on-call engineer and their team without disturbing anyone already assigned. When the incident closes, Create Dependencies records the follow-up work the postmortem produced as waiting on the fix, so the ordering survives the meeting. ## Human-in-Loop Highlight Initiate Board Event is the operation on this connector with the widest reach: one call fires a named custom event against an entire board, running every matching automation across as many as a thousand cards at once. AgilePlace rate limits it to five calls per event in five minutes precisely because of that, which means there is no walking it back by firing a correcting event a few seconds later. So the release agent fires against a single card freely with Initiate Card Event, and stops before the board-wide version. It posts: "Release 2026.9.1 matches 214 cards on the Delivery board. Firing release-shipped board wide will run three automations against every matching card, including the one that closes them. Fire, or should I move only the 47 cards in the Ready to Deploy lane?" The board owner answers. The agent does whichever it was told. The reason this is safe is not that the agent matched carefully. It is that the call with a thousand-card blast radius was made by the person who owns the board. 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 105 actions ### Account 4 - **Get Account** Returns the account's settings and which features are switched on. The cheapest way for a flow to confirm the connection is pointed at the right account. - **List API Tokens** Returns the API tokens the current user holds. Useful when auditing which integrations are reaching the account, though every token shares one rate limit. - **Create API Token** Creates an API token for the current user. The token value is returned once and never again, so a provisioning flow captures it in the same step. - **Delete API Token** Revokes an API token. Anything still using it stops immediately, so revocation flows confirm ownership first. ### Boards 15 - **List Boards** Returns the boards the token's user can reach. Filter by minimum access to get only the boards a flow can actually write to. - **Get Board** Returns one board with its lanes, card types, custom icons and settings. This is the call that tells a flow which lane a card may go in. - **Create Board** Creates a board, optionally copying a template or an existing board. Used to provision a per-initiative or per-client board on demand. - **Update Board** Changes a board's title, sharing, work in progress behavior or defaults. Anything left empty keeps its current value. - **Delete Board** Deletes a board and every card on it. Archiving is the reversible alternative, so deletion belongs behind a review step. - **Archive Board** Takes a board out of circulation without deleting it. Archived boards stay readable and can be brought back. - **Unarchive Board** Brings an archived board back into circulation. - **List Board Lanes** Returns only the lanes that can actually hold cards, which is what a flow needs before moving one. - **Get Lane Card Counts** Returns how many cards sit in each lane. Used to check a work in progress limit before a move rather than after it is breached. - **Update Lane** Changes one lane's title, policy, work in progress limit or card status. Used when a process change needs to reach the board. - **List Board Users** Returns the people on a board with their roles and work in progress counts. The read behind an access audit. - **List Board Assigned Users** Returns the people actually assigned to cards on a board, which is a smaller list than the people who can see it. - **Set Board Access** Grants a role on one or more boards to people named by email, by user id or by team. Lowering somebody to Reader unassigns them from every card on the board, so a downgrade is a change flows treat as consequential. - **Remove Board Access** Takes people off one or more boards. Their subscriptions to card, lane and board changes go with the access and do not return when access is restored. - **Export Board History** Downloads a board's history into FlowRunner file storage and returns a URL later steps can use. The input for an audit or an analytics load. ### Cards 11 - **List Cards** Returns cards across boards, filtered any way the board interface can filter them. Use the since filter to poll for what changed rather than reading everything again. - **Get Card** Returns one card in full, including its lane, assignees, tags and custom fields. The follow up after a trigger, which delivers ids rather than the card. - **Create Card** Creates a card. The destination decides what you get: a board drops it in the default lane, a lane places it exactly, and naming a parent card makes it a task on that card's taskboard instead. - **Update Card** Changes a card. Anything left empty is untouched, and passing the card's version makes AgilePlace refuse the write if somebody else changed it first. - **Move Cards** Moves cards between lanes or boards. This is how progress is recorded, and naming a parent card as the destination converts a card into a task. - **Assign Card Members** Adds or removes people and teams on one or more cards without disturbing the assignees you did not mention. The additive alternative to a full card update. - **Delete Card** Deletes one card. The board's card deletion setting has to allow it unless the token's user is a board administrator. - **Delete Cards** Deletes several cards at once, all of which must be on the same board. Bulk removal is worth a confirmation step for the same reason a single delete is. - **List Card Activity** Returns a card's recent history, newest first. Used to answer who moved or changed a card and when. - **List Card Tasks** Returns the task cards on a card's taskboard. - **Get Card Taskboard** Returns the lanes of a card's taskboard, which a flow needs before creating a task in a particular one. ### Comments 4 - **List Card Comments** Returns a card's comments, oldest first, optionally interleaving the conversation on connected child cards. - **Create Card Comment** Adds a comment to a card. A comment also fires the comment added trigger event, so this is one way a flow wakes another. - **Update Card Comment** Rewrites a comment. This replaces the whole comment rather than appending, so the previous text is gone. - **Delete Card Comment** Removes a comment from a card. ### Attachments 4 - **List Card Attachments** Returns the files attached to a card, with their sizes and who added them. - **Upload Card Attachment** Attaches a file to a card from a URL, a base64 string or raw bytes. Used to put evidence on the card where the reviewer will look for it. - **Download Card Attachment** Downloads an attachment into FlowRunner file storage and returns a URL later steps can use. - **Delete Card Attachment** Removes an attachment from a card. ### Connections 6 - **Connect Cards** Links cards into a parent and child hierarchy, which is what drives connected card statistics and roll up dates. - **Disconnect Cards** Removes parent or child links between cards, leaving the cards themselves in place. - **List Child Cards** Returns the cards connected below one card, optionally narrowed to a board or a stage of work. - **List Parent Cards** Returns the cards connected above one card. - **Get Connection Statistics** Returns the roll up across a card's children: how many are started, finished or blocked, and their sizes. The read behind an initiative status without opening its children. - **Disconnect Board Cards** Removes every child connection a card has to one board at once. This is a whole board's worth of links rather than one, so flows name the board deliberately. ### Dependencies 4 - **List Card Dependencies** Returns what a card waits on and what waits on it. A dependency orders work in time, where a connection nests it. - **Create Dependencies** Records that some cards wait on others, with the timing relationship between them. - **Update Dependency** Changes the timing of one dependency between two cards. - **Delete Dependencies** Unlinks cards that were waiting on others. ### Board Setup 17 - **List Card Types** Returns a board's card types with their colors. Card types belong to one board, so an id from another board is refused. - **Create Card Type** Adds a card type to a board. A type is unusable until it is marked for cards, for tasks, or for both. - **Update Card Type** Renames a card type, recolors it, or changes whether it applies to cards, tasks or both. - **Delete Card Type** Removes a card type from a board. AgilePlace refuses while cards still use it. - **List Custom Icons** Returns a board's custom icons, which AgilePlace uses for class of service. - **Create Custom Icon** Adds a custom icon to a board, with an optional policy explaining when to use it. - **Update Custom Icon** Changes a custom icon's name, image, color or policy. - **Delete Custom Icon** Removes a custom icon from a board. - **List Custom Fields** Returns a board's custom fields with their ids and types, which a flow needs before setting one on a card. - **Change Custom Field** Adds, replaces or removes one custom field on a board. Used when a process change needs a new field to exist before cards can carry it. - **List Board Tags** Returns every tag in use on a board. - **Replace Board Tags** Renames tags across a whole board by folding several old tags into one new one. Every card carrying any of the old tags is rewritten and there is no undo. - **Delete Board Tags** Removes tags from every card on a board. - **List Board Templates** Returns the board templates the account has, which are what board creation can start from. - **Get Board Template** Returns one board template with its layout. - **Create Board Template** Saves an existing board as a template so new boards can start from it. - **Delete Board Template** Removes a board template. Boards already created from it are untouched. ### Teams 12 - **List Teams** Returns the account's teams. A team can be assigned to a card and granted board access just as a person can. - **Get Team** Returns one team. - **Create Team** Creates a team, which is how a new squad gets a single handle for assignment and access. - **Update Team** Renames a team, changes its description, or disables it. Disabling stops the team being offered while keeping its history. - **Delete Team** Deletes a team. Its members keep their own accounts and board access. - **List Team Members** Returns the people in a team. - **Add Team Members** Adds people to a team, capped by AgilePlace at 100 per call. - **Remove Team Members** Takes people out of a team, capped at 10 per call, which is a tighter limit than adding them. - **List Subteams** Returns the teams nested directly under a team. - **Add Subteams** Nests teams under a team, capped at 10 per call. - **Remove Subteams** Unnests teams from a team, leaving both in place. - **List Team Boards** Returns the boards a team has been granted access to. ### Users 10 - **List Users** Returns the account's users. The read behind joiner and leaver reconciliation. - **Get User** Returns one user. - **Get Current User** Returns the user the token belongs to, and which account it reaches. The cheapest connection check available. - **List My Cards** Returns the cards assigned to, or subscribed to by, the token's user. A personal work list rather than a board query. - **List My Recent Boards** Returns the boards the token's user opened most recently, which is a sensible default when a flow needs a board and nobody named one. - **Create User** Creates a user. The administrator role grants full control of the whole account rather than of one board, so provisioning flows set roles explicitly. - **Update User** Changes a user, including their administrator flag and whether they are enabled. Turning enabled off locks somebody out without deleting their history. - **Delete User** Deletes a user. Disabling through the update operation is the reversible alternative and keeps the person's history intact. - **List Invitations** Returns user invitations, pending by default. Ask for accepted ones to see who has joined. - **Revoke Invitation** Revokes an open invitation, or restores one revoked by mistake. ### Planning 11 - **List Planning Series** Returns the planning series in the account. A series is a calendar of increments that cards are tagged into. - **Get Planning Series** Returns one planning series. - **Create Planning Series** Creates a planning series, scoped either to every board or to the boards you name. - **Update Planning Series** Changes a planning series. Supplying boards replaces the list, so a board left out loses access to the series and every increment in it. - **Delete Planning Series** Deletes a planning series and every increment in it. Cards tagged with those increments lose the tag. - **List Planning Increments** Returns the increments in a series, which are the sprints or program increments cards get assigned to. - **Get Planning Increment** Returns one planning increment with its dates. - **Get Increment Status** Returns how the cards in an increment are progressing, grouped by not started, started and finished. The read behind an increment review. - **Create Planning Increment** Adds an increment to a planning series. - **Update Planning Increment** Changes an increment's name or dates. - **Delete Planning Increment** Removes an increment from a series. Cards tagged with it lose the tag. ### Automations 7 - **List Automations** Returns a board's card automations, including any created by this connector's trigger. The read that finds a rule firing when it should not. - **Get Automation** Returns one automation with its full configuration. - **List Automation Runs** Returns the recent runs of one automation, which is the only way to see whether it fired and what happened. - **Set Automation Enabled** Turns an automation on or off without deleting it. The safe way to stop a misbehaving rule. - **Delete Automation** Deletes an automation from a board. Deleting one that a FlowRunner trigger created stops that trigger firing. - **Initiate Card Event** Fires a named custom event against one card, running any automation on its board that listens for it. How a system outside AgilePlace pushes a single piece of work forward. - **Initiate Board Event** Fires a named custom event against a whole board, running matching automations for every card that matches, up to a thousand of them. This is the operation the human gate on this page exists for. ## Triggers 1 triggers ### Event Triggers 1 - **On Card Event** Fires when the chosen event happens to a card on a board. AgilePlace has no webhook resource, so this registers a card automation whose action is a web service call: it appears in the board's card automation list, and anyone with board admin rights can disable or delete it there. The delivery carries ids rather than the card itself, so a flow follows it with Get Card when it needs the fields. ## Frequently Asked Questions ### What can FlowRunner do with AgilePlace? FlowRunner agents can run Get Account, List API Tokens, and Create API Token in AgilePlace, plus 102 more actions. ### Does connecting AgilePlace to FlowRunner require OAuth? No. AgilePlace connects to FlowRunner with an API key, no OAuth flow required. ### Can AgilePlace trigger a FlowRunner workflow automatically? Yes. AgilePlace supports 1 trigger that can start a FlowRunner workflow automatically. **Work at AgilePlace?** This integration exposes AgilePlace to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/agileplace. Site index: https://flowrunner.ai/llms.txt