Businessmap

Businessmap, formerly Kanbanize, is portfolio kanban with workspaces, boards, cards, time tracking and measurable outcomes. Agents create and move cards, update custom fields, log time and roll up outcomes across boards and workspaces.

152 actions API key available

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

The measurement window closes on a delivery outcome

List Outcome Cards returns the work linked to the goal, and List Cards returns each card's column and blocked state

List Logged Time aggregates the effort actually spent against those cards

Agent computes the outcome's current value from the system where the metric genuinely lives

Agent compares that value against the last entry in List Outcome Values and against the outcome's target

Agent posts the computed value, the contributing cards and the change since last time to the outcome owner

The owner confirms the number before Create Outcome Value writes it, because nothing in this API removes one

What This Integration Enables

Businessmap, the product formerly called Kanbanize, is portfolio Kanban for organizations that want the board to answer a question above the board. Its API shows that clearly. Alongside workspaces, boards, columns, lanes and cards, it exposes outcomes: measurable goals that cards link to, so progress on the work rolls up into a number leadership reads. It also insists on honesty about work that did not finish. A card can be archived, or it can be discarded with a named reason, and Businessmap keeps discarded work separately from both live and archived cards so the ratio between started and abandoned is a real figure rather than a guess.

FlowRunner agents run the board from the systems where work originates, create and move cards in bulk rather than one call per card, log time in the categories that make reports separable, block cards with named reasons when an external dependency stalls them, and roll the whole thing up into outcomes. One modeling detail is worth designing around: Businessmap's list fields on a card are additive, taking separate add and remove lists rather than replacing what was there. That is the opposite of most APIs, and it means an agent that sends one tag adds it rather than silently clearing the rest. Every action is built and verified against the Businessmap API.

Without FlowRunner

Goals reported from memory The board shows work in progress, and whether it moved the goal is argued in the review

Blocked work counted, not explained Cards sit blocked with a free text note, so blocked time cannot be reported against a cause

Dropped work quietly disappears Abandoned cards are deleted or left to rot, and nobody can say how much was started and not finished

With FlowRunner

Goals move on evidence Each recorded measurement arrives with the cards that contributed to it and the effort logged against them

Blocked time is attributable Blocks carry a named reason, so blocked hours roll up to a cause a process change can address

Dropped work stays on the record Cards that were dropped are discarded with a reason rather than deleted, and the ratio is readable

Use Case Scenarios

The delivery board written from the engineering systems

A pull request opens in GitHub. The agent calls Get Board Structure to resolve the column and lane identifiers, which is the one read every card write depends on, then Create Card with its type, tags, watchers and custom fields set in the same call. When the build breaks or a dependency stalls, Block Card marks it with a named block reason from the account's own list rather than free text, so blocked hours can later be reported against a cause. On merge, Move Card advances it and Create Logged Time records the effort. Where a release covers many cards, Create Cards and Update Cards send the whole set in one request, which Businessmap counts as a single call against the rate limit.
Portfolio roll up that answers whether the work is working

Initiative cards on a management workspace are linked to delivery cards below them with Link Cards, and to a measurable goal with Set Card Milestone and the outcome operations. On a schedule, the agent reads List Outcome Cards for each goal, checks how many of the contributing cards are still blocked or discarded, aggregates the logged time behind them, and writes the picture into Google Sheets for trend history. Goals that are off pace, or whose contributing work is mostly blocked, post to Slack with the blocking reasons named. The review opens on the two goals that need a decision rather than on all twelve.
Board hygiene that keeps the history

A quarterly sweep finds cards that have not moved in months. Rather than deleting them, the agent reads each one, posts a summary to its owner, and applies the reversible operation the vendor already ships: Set Card Archived for work that is genuinely done and Set Card Discarded, with a discard reason, for work that was dropped. Both keep the card, its comments, its logged time and its history. Delete Card and Delete Cards stay out of the automated path entirely, because the reporting value of a board depends on it still containing the work that did not finish.

Human-in-Loop Highlight

Create Outcome Value is the operation on this connector with no inverse. It records a measurement against a goal, which is what the outcome's progress chart is drawn from and what leadership reads as the answer. There is no operation anywhere in this API that removes a single recorded value. The only way to take one back is Delete Outcome, which destroys the goal along with every value and checkpoint it ever held, so correcting one bad number means discarding the entire history behind it. That asymmetry is the whole argument for a person on this call. So the reporting agent computes and stops: "Time to Restore is due a measurement for August. From 41 incidents I make it 3.9 hours, against a target of 4 and a July value of 5.2. Two of those incidents were reopened after closure, which I have counted once each; counting the reopen separately gives 4.4. Which number should I record?" The outcome owner picks. Create Outcome Value writes exactly that, once, and the chart the executive team reads is one somebody chose to stand behind.

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

152 actions

Account and Workspaces

Get Current User Reads the Businessmap user the API key belongs to. Used to confirm a connection works and to discover the identifier user-scoped filters need, because a key carries its owner's permissions rather than an application's.
List Workspaces Lists the workspaces the key can see. A workspace holds boards, and its type decides whether it is a team workspace or a management one.
Get Workspace Reads one workspace.
Create Workspace Creates a workspace. A team workspace holds the boards a team works on; a management workspace holds portfolio boards that roll work up from other workspaces.
Update Workspace Renames a workspace or archives it. Businessmap publishes no delete route for a workspace, so archiving is how one is retired.
List Workspace Managers Lists the users who can manage a workspace, which is who can change its boards' structure.
Set Workspace Manager Adds a user as a manager of a workspace, or removes them. A workspace manager can change the structure of every board in it, so this grants real authority.

Boards

List Boards Lists boards, optionally narrowed to a workspace or to archived ones.
Get Board Reads one board's details. For its layout, the structure operation returns everything in a single call.
Get Board Structure Reads a board's workflows, columns and lanes together with their identifiers. The call to make first, because creating or moving a card needs identifiers that only exist here.
Create Board Creates a board in a workspace, arriving with Businessmap's default workflow, columns and lanes.
Update Board Updates a board's name, description or archived state. Archiving keeps its cards and history.
Delete Board Permanently deletes a board along with its cards, their comments and their history. Archiving through the update operation is the alternative that keeps everything.

Board Structure

List Columns Lists a board's columns with their identifiers, sections and work in process limits.
Get Column Reads one column of a board.
Create Column Adds a top level column to one of a board's workflow sections.
Create Subcolumn Adds a column nested inside an existing one. Businessmap takes a parent column instead of a workflow and a section here, which is why it is a separate operation.
Update Column Updates a column's name, description, color, position or work in process limit.
Delete Column Deletes a column from a board. Businessmap refuses while it still holds cards.
List Lanes Lists a board's lanes, which are the horizontal swimlanes cards sit in.
Get Lane Reads one lane of a board.
Create Lane Adds a lane to a board, belonging either directly to a workflow or nested inside another lane.
Update Lane Updates a lane's name, description, color or position.
Delete Lane Deletes a lane from a board. Businessmap refuses while it still holds cards.

Cards

List Cards Lists cards, narrowed by board, workflow, column, lane, owner, type, priority, blocked state or any of Businessmap's date windows. Cards are always paginated, and the pagination block comes back alongside them so a flow can loop.
Get Card Reads one card. Expanding the response pulls its comments, subtasks, attachments, custom field values, tags or watchers back in the same call rather than one request each.
Create Card Creates a card in a column. A card belongs to a column and a lane rather than to a board, and tags, milestones, co-owners, watchers, custom fields, subtasks and attachments can all be set in this one call.
Update Card Updates a card. Businessmap's list fields are additive, taking a to-add list and a to-remove list, so sending only the add list leaves everything already there in place.
Move Card Moves a card to a column, a lane or a position. The placement operation narrowed to the fields that place a card.
Set Card Archived Archives a card or brings it back. An archived card keeps its history and stops appearing on the board.
Set Card Discarded Discards a card or brings it back. Discarding records work that was dropped rather than finished, kept separately from both live and archived cards.
Block Card Marks a card as blocked, either generically with a comment or against a named block reason. Naming the reason is what makes blocked time reportable.
Unblock Card Clears a card's block, letting it move again.
Create Cards Creates several cards in one request. Businessmap counts this as one API call rather than one per card, so an import uses it rather than a loop.
Update Cards Updates several cards in one request, each entry naming the card it changes and carrying the same additive list semantics.
Delete Cards Permanently deletes several cards in one request, along with their comments, logged time and history.
Delete Card Permanently deletes a card together with its comments, logged time and history. Archiving and discarding are the reversible alternatives.

Card Relations

List Linked Cards Lists every card linked to this one, of every kind: parents, children, predecessors, successors and relatives, with the kind of each link.
Link Cards Links one card to another. Each kind of link is its own sub resource and the link is directional, so the flow states which end it is writing from.
Unlink Cards Removes a link between two cards. The link kind must match the one that was made.

Comments

List Card Comments Lists the comments on a card.
Get Card Comment Reads one comment on a card.
Create Card Comment Adds a comment to a card, optionally with attachments, posted as the user the API key belongs to.
Update Card Comment Rewrites a comment on a card.
Delete Card Comment Deletes a comment from a card together with its attachments.

Subtasks

List Card Subtasks Lists a card's subtasks with their owners, deadlines and finished state.
Get Card Subtask Reads one subtask of a card.
Create Card Subtask Adds a subtask to a card. A subtask carries its own owner and deadline, and time can be logged against it separately.
Update Card Subtask Updates a subtask, including ticking it off. Only the fields supplied are changed.
Delete Card Subtask Deletes a subtask from a card.

Attachments

List Card Attachments Lists a card's attachments with their names and links.
Create Card Attachment Attaches a file to a card by link. Businessmap's API attaches an address rather than uploading bytes, so the file must already be reachable at a URL.
Update Card Attachment Renames a card attachment or moves it in the list.
Delete Card Attachment Removes an attachment from a card.

Card Assignment and Labels

List Card Tags Lists the tags on a card.
Set Card Tag Puts a tag on a card or takes it off. The tag must already be available on that card's board.
List Card Milestones Lists the milestones a card is linked to.
Set Card Milestone Links a card to a milestone or unlinks it. The milestone must already be available on that card's board.
List Card Co-Owners Lists a card's co-owners, who share responsibility for it with its owner.
Set Card Co-Owner Adds a user as a co-owner of a card or removes them. A card has exactly one owner but any number of co-owners.
List Card Watchers Lists the users watching a card, who are notified when it changes.
Set Card Watcher Adds a user as a watcher of a card or removes them, which turns that person's notifications for the card on or off.
List Card Stickers Lists the stickers on a card. Each entry carries its own identifier, separate from the sticker's own.
Add Card Sticker Puts a sticker on a card. The sticker must already be available on that card's board.
Remove Card Sticker Takes a sticker off a card, using the identifier that belongs to the sticker on this card.

Card Custom Fields

List Card Custom Fields Lists the custom field values set on a card.
Set Card Custom Field Sets a custom field's value on a card. Which parameter carries the value depends on the field's type, so a flow reads the definition before writing.
Remove Card Custom Field Clears a custom field from a card. The field itself and its definition are untouched.

Time Tracking

List Logged Time Lists logged time entries, optionally narrowed to a card, a user or a date window.
Get Logged Time Reads one logged time entry.
Create Logged Time Logs time against a card, or against one of its subtasks. The duration is in seconds, and leaving the user empty logs it for whoever the API key belongs to.
Update Logged Time Updates a logged time entry, changing only the fields supplied.
Delete Logged Time Removes a logged time entry from a card.

Stickers

List Stickers Lists the account's stickers, which are the icon badges cards can carry.
Get Sticker Reads one sticker.
Create Sticker Creates a sticker.
Update Sticker Updates a sticker's name, color, availability, icon or enabled state.
Delete Sticker Deletes a sticker from the account and from every card carrying it.

Card Types

List Card Types Lists the account's card types. A card type carries a color and an icon and is what tells a bug apart from a feature on a board.
Get Card Type Reads one card type.
Create Card Type Creates a card type, which is how a new class of work becomes distinguishable on every board.
Update Card Type Updates a card type's name, description, color, icon or enabled state.
Delete Card Type Deletes a card type. Businessmap refuses to delete one that cards still use.

Milestones

List Milestones Lists the account's milestones, each carrying a date that cards can be linked to.
Get Milestone Reads one milestone.
Create Milestone Creates a milestone with a date, which then appears as a marker on the board's timeline.
Update Milestone Updates a milestone's name, date, description, color, availability or enabled state.
Delete Milestone Deletes a milestone and unlinks it from every card.

Block and Discard Reasons

List Block Reasons Lists the account's block reasons, which are the named explanations a block can use.
Get Block Reason Reads one block reason.
Create Block Reason Creates a named block reason. Named reasons are what make blocked time reportable, because a generic block records only free text.
Update Block Reason Updates a block reason's name, color, availability or enabled state.
Delete Block Reason Deletes a block reason from the account.
List Discard Reasons Lists the account's discard reasons, which explain why work was dropped rather than finished.
Get Discard Reason Reads one discard reason.
Create Discard Reason Creates a discard reason. Businessmap accepts a label, an availability rule and an enabled flag, without the color a block reason takes.
Update Discard Reason Updates a discard reason's name, availability or enabled state.
Delete Discard Reason Deletes a discard reason from the account.

Logged Time Categories

List Logged Time Categories Lists the account's logged time categories, which separate development time from support time in reports.
Get Logged Time Category Reads one logged time category.
Create Logged Time Category Creates a logged time category, which is how a new kind of effort becomes separable in reporting.
Update Logged Time Category Updates a logged time category's name, description, color, availability or enabled state.
Delete Logged Time Category Deletes a logged time category from the account.

Custom Fields

List Custom Fields Lists the account's custom fields with their types. Read before writing a value, because which parameter carries it depends entirely on the type.
Get Custom Field Reads one custom field's definition, including its type and settings.
Create Custom Field Creates a custom field of a given type. A dropdown's allowed values are added afterwards as separate values.
Update Custom Field Updates a custom field's name, description, availability or enabled state. A field's type cannot be changed once it exists.
Delete Custom Field Deletes a custom field. Every value stored in it on every card goes with it, and that data cannot be recovered.
List Custom Field Values Lists the allowed values of a dropdown custom field, which is what a card write selects from.
Create Custom Field Value Adds an allowed value to a dropdown custom field.
Update Custom Field Value Renames an allowed value of a dropdown custom field or moves it in the list. Cards already carrying it follow the rename.
Delete Custom Field Value Removes an allowed value from a dropdown custom field, and from every card that had selected it.

Users

List Users Lists the account's users.
Get User Reads one user.
Invite User Adds a user to the account and emails them an invitation. Skipping the email creates the account without notifying anyone, which is what an automated import usually wants.
Update User Updates a user's details or disables them. Disabling frees the license while keeping everything the person did.
List User Boards Lists the boards a user is assigned to, together with the role they hold on each.
Delete User Permanently deletes a user from the account. Disabling through the update operation is the alternative when the aim is only to free a license.

Teams

List Teams Lists the account's teams.
Get Team Reads one team.
Create Team Creates a team. Members are added afterwards.
Update Team Renames a team or changes its description.
List Team Members Lists the users in a team.
Set Team Member Adds a user to a team or removes them.
List Team Managers Lists the users who can manage a team.
Set Team Manager Makes a user a manager of a team or removes that role.
Delete Team Deletes a team. Its members keep their accounts and their board access.

Outcomes

List Outcomes Lists outcomes, which are Businessmap's measurable goals. Cards are linked to an outcome so progress on the work rolls up to the goal.
Get Outcome Reads one outcome with its current and target values.
Create Outcome Creates an outcome, either recording its value by hand, driving it from a custom field, or driving it from a calculation rule.
Update Outcome Updates an outcome's name, description or targets.
List Outcome Cards Lists the cards linked to an outcome, which is the work expected to move it.
List Outcome Values Lists the recorded values of an outcome over time, which is what its progress chart is drawn from.
Create Outcome Value Records a new measurement against an outcome. This is the operation the human gate on this page exists for, because no operation removes a single recorded value.
Delete Outcome Deletes an outcome together with its recorded values and checkpoints. The cards that were linked to it are untouched.

Roles

List Roles Lists the account's board roles, which decide what a user may do on a board.
Get Role Reads one role.
List Role Permissions Lists a role together with every permission granted to it, which is the only way to see what a role can actually do.
Create Role Creates a board role. A new role starts with no permissions.
Update Role Renames a role, leaving its permissions unchanged.
Delete Role Deletes a role. Users who held it lose that access, so an access audit runs first.

Webhooks

List Webhooks Lists the account's webhooks, each of which posts board events to an address.
Get Webhook Reads one webhook.
Create Webhook Subscribes an address to a board's events, or to every board's when no board is named. Businessmap publishes neither the list of events nor the shape of what it posts, so a flow receiving these discovers the payload from a real delivery, which is why this ships as an action rather than as a FlowRunner trigger.
Update Webhook Updates a webhook's address, board or enabled state. Turning it off stops deliveries without losing the subscription.
Delete Webhook Deletes a webhook so Businessmap stops posting to it.

Frequently Asked Questions

What can FlowRunner do with Businessmap?

FlowRunner agents can run Get Current User, List Workspaces, and Get Workspace in Businessmap, plus 149 more actions.

Does connecting Businessmap to FlowRunner require OAuth?

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

Can Businessmap trigger a FlowRunner workflow automatically?

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

Start building with Businessmap

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us