Integration

Businessmap integration

Businessmap (formerly Kanbanize) is a Kanban and portfolio management platform. Create, search, update, move and delete cards; manage their comments, subtasks, attachments (links), tags, stickers, watchers, co-owners, custom field values, block reasons, milestones, logged time and parent, child, predecessor and successor links; read and change boards, workflows, lanes and columns; manage account-level tags, stickers, card types, custom fields, block reasons, milestones, workspaces and webhooks; read users and teams. Exports, documents, dashboards, business rules, outcomes, card templates, user and team administration, company settings and history routes are not exposed. Authentication is the Businessmap API key in the apikey header (My Account, API); subdomain is your account name in <subdomain>.kanbanize.com. Default limits: 600 requests per hour and 30 per minute.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Businessmap.Built from the 158 Businessmap tools below, on the connection you add once.

What you can do with Businessmap

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Card, 5 operations

  • create_cardCreate cardPOSTCreates a card. lane_id and column_id are required (see get_board_structure). Use create_many_cards to create several in one call.
  • create_many_cardsCreate many cardsPOSTCreate multiple cards in a single request.
  • delete_cardDelete cardDELETEDeletes a card permanently: it cannot be recovered.
  • get_cardGet cardGETRetrieve the details of a specific card.
  • list_cardsList cardsGETLists cards of the account, filtered by board_ids, workflow_ids, lane_ids, column_ids, state, dates, owners and more (comma-separated id lists). Paged with page and per_page (default 200, max 1000).

Workflow, 5 operations

  • copy_workflowCopy workflowPOSTCopy an existing workflow from the specified board.
  • create_workflowCreate workflowPOSTCreate a new workflow.
  • delete_workflowDelete workflowDELETEDelete a workflow of a board. A workflow that still contains cards cannot be deleted.
  • get_workflowGet workflowGETGet the details of a workflow for the specified board.
  • list_workflowsList workflowsGETRetrieves a list of workflows for the specified board with their relevant details.

Block reason, 4 operations

  • create_block_reasonCreate block reasonPOSTCreate a new block reason for the account. Its name must be unique: duplicate names are refused.
  • delete_block_reasonDelete block reasonDELETEDeletes a block reason. Cards blocked by it move to replace_with_reason_id if given, else to the Generic Blocker, with the deleted reason's name as the block comment.
  • get_block_reasonGet block reasonGETGet the details of a single block reason.
  • list_block_reasonsList block reasonsGETLists the block reasons of the account. Waiting on us and Waiting on others exist by default; the Generic Blocker is not listed (get_board_structure shows allow_generic_blocker).

Board, 4 operations

  • create_boardCreate boardPOSTCreate a new board.
  • delete_boardDelete boardDELETEDelete a board.
  • get_boardGet boardGETGet the details of a single board.
  • list_boardsList boardsGETRetrieves a list of boards with their relevant details, optionally filtered using various parameters.

Card attachment, 4 operations

  • add_card_attachmentAdd card attachmentPOSTAdds an attachment to a card, given its file_name and a link (URL) to the file.
  • delete_card_attachmentDelete card attachmentDELETEDelete a specific attachment from a card.
  • get_card_attachmentGet card attachmentGETGet the details of a specific attachment for a card.
  • list_card_attachmentsList card attachmentsGETLists the attachments of a card. Attachments can be disabled account-wide, and the account sets a maximum file size between 1 MB and 30 MB.

Card comment, 4 operations

  • add_card_commentAdd card commentPOSTCreate a new comment to a specific card. Only comments of type `plain` can be created using the API.
  • delete_card_commentDelete card commentDELETEDelete a specific comment associated with a card.
  • get_card_commentGet card commentGETRetrieves detailed information about a specific comment associated with a card.
  • list_card_commentsList card commentsGETGet a list of all comments associated with a specific card.

Card subtask, 4 operations

  • add_card_subtaskAdd card subtaskPOSTCreate a new subtask for a card.
  • delete_card_subtaskDelete card subtaskDELETERemove a subtask from a card.
  • get_card_subtaskGet card subtaskGETGet the details of a specific subtask for a card.
  • list_card_subtasksList card subtasksGETRetrieve a list of a card's subtasks.

Card type, 4 operations

  • create_card_typeCreate card typePOSTCreate a new card type.
  • delete_card_typeDelete card typeDELETEDelete a card type.
  • get_card_typeGet card typeGETGet the details of a single card type.
  • list_card_typesList card typesGETRetrieves a list of card types with their relevant details, optionally filtered using various parameters.

Column, 4 operations

  • create_columnCreate columnPOSTCreate a new column in a workflow of a board (board ids come from list_boards, workflow ids from list_workflows).
  • delete_columnDelete columnDELETEDeletes a column from a board. Optionally name other columns to receive its cards and its cycle time data; cycle time data with no target column is discarded.
  • get_columnGet columnGETGet the details of one column of a board (column ids come from list_columns).
  • list_columnsList columnsGETGet a list of the columns of a board (board ids come from list_boards).

Custom field, 4 operations

  • create_custom_fieldCreate custom fieldPOSTCreate a new custom field for the account. To make it available on a board, call add_board_custom_field afterwards.
  • delete_custom_fieldDelete custom fieldDELETEDelete a custom field. It is removed from all boards and cards that use it, with the values entered in it, and this cannot be reversed.
  • get_custom_fieldGet custom fieldGETGet the details of the specified custom field.
  • list_custom_fieldsList custom fieldsGETRetrieves a list of custom fields with their relevant details, optionally filtered using various parameters.

Lane, 4 operations

  • create_laneCreate lanePOSTCreate a new lane on a specific board.
  • delete_laneDelete laneDELETEDelete a lane. This action cannot be undone. If there are cards present in the lane, it will not be deleted until they're moved to another lane or discarded.
  • get_laneGet laneGETGet the details of a specific lane on a board.
  • list_lanesList lanesGETRetrieve a list of the lanes on a specified board.

Milestone, 4 operations

  • create_milestoneCreate milestonePOSTCreate a new milestone.
  • delete_milestoneDelete milestoneDELETEDelete a milestone.
  • get_milestoneGet milestoneGETGet the details of a single milestone.
  • list_milestonesList milestonesGETRetrieves a list of milestones with their relevant details, optionally filtered using various parameters.

Sticker, 4 operations

  • create_stickerCreate stickerPOSTCreate a new sticker.
  • delete_stickerDelete stickerDELETEDelete a sticker.
  • get_stickerGet stickerGETGet the details of a single sticker.
  • list_stickersList stickersGETRetrieves a list of stickers, optionally filtered by various criteria.

Tag, 4 operations

  • create_tagCreate tagPOSTCreate a new tag.
  • delete_tagDelete tagDELETEDelete a tag.
  • get_tagGet tagGETGet the details of the specified tag.
  • list_tagsList tagsGETRetrieves a list of tags with their relevant details, optionally filtered using various parameters.

Webhook, 4 operations

  • create_webhookCreate webhookPOSTCreates a webhook that posts board events of board_id to url. The vendor returns the signing secret only once, at creation, and this tool does not pass it on, so deliveries of a webhook made here cannot be verified with it.
  • delete_webhookDelete webhookDELETEDeletes the specified webhook by its unique identifier. This operation permanently removes the webhook and stops all future notifications to its URL.
  • get_webhookGet webhookGETRetrieves the details of one webhook by its identifier (from list_webhooks).
  • list_webhooksList webhooksGETGet a list of all currently defined webhooks. You can optionally filter the results by one or more board IDs (from list_boards).

Board block reason, 3 operations

  • add_board_block_reasonAdd board block reasonPUTMake a block reason available on a board.
  • list_board_block_reasonsList board block reasonsGETGet a list of the block reasons available on a board. list_block_reasons returns every block reason of the account.
  • remove_board_block_reasonRemove board block reasonDELETEMake a block reason unavailable on a board.

Board custom field, 3 operations

  • add_board_custom_fieldAdd board custom fieldPUTAdds a custom field to a board. Check the field's global availability first with get_custom_field: 0 manual, 1 added to all new boards, 2 added to every board and not removable.
  • get_board_custom_fieldGet board custom fieldGETGet a custom field available on a specified board.
  • list_board_custom_fieldsList board custom fieldsGETGet a list of the custom fields available on a board. get_custom_field returns the full definition of one of them.

Card custom field, 3 operations

  • add_card_custom_fieldAdd card custom fieldPUTAdd a new custom field to a card or update the specified custom field if it is already added to the card.
  • get_card_custom_fieldGet card custom fieldGETRetrieve the details of a specific custom field associated with a card, if the field has been added to it.
  • list_card_custom_fieldsList card custom fieldsGETRetrieve a list of the custom fields added to a specific card along with their associated values.

Logged time, 3 operations

  • add_logged_times_manyAdd logged times manyPOSTAdd multiple logged times to cards in a single request. All entries are created inside one database transaction, so if any entry is invalid, none of the entries are saved.
  • get_logged_timeGet logged timeGETGet the details of a specific logged time entry.
  • list_logged_timesList logged timesGETGet a list of the logged times added to cards. The logged times are listed in the order in which they were added.

User, 3 operations

  • get_current_userGet current userGETRetrieves details for the currently authenticated user, for example their username, email and other profile settings.
  • get_userGet userGETGet the details of the specified user.
  • list_usersList usersGETRetrieves a list of users with their relevant details, optionally filtered using various parameters.

Workspace, 3 operations

  • create_workspaceCreate workspacePOSTCreate a new workspace.
  • get_workspaceGet workspaceGETGet the details of the specified workspace.
  • list_workspacesList workspacesGETRetrieves a list of workspaces with their relevant details, optionally filtered using various parameters.

Board card type, 2 operations

  • add_board_card_typeAdd board card typePUTMakes a card type available on a board. With no body fields, it is added with null board values, so its global settings apply.
  • list_board_card_typesList board card typesGETGet a list of the card types available on a board. list_card_types returns every card type of the account.

Board tag, 2 operations

  • add_board_tagAdd board tagPUTMake a tag available on the specifie board.
  • list_board_tagsList board tagsGETGet a list of the tags available on the specified board.

Card co owner, 2 operations

  • add_card_co_ownerAdd card co ownerPUTAssign a user as a co-owner of a card.
  • list_card_co_ownersList card co ownersGETRetrieve a list of a card's co-owners.

Card milestone, 2 operations

  • add_card_milestoneAdd card milestonePUTMake a milestone available on a card.
  • list_card_milestonesList card milestonesGETGet a list of the milestones added to a card.

Card revision, 2 operations

  • get_card_revisionGet card revisionGETRetrieve the details of one revision of a card (revision numbers come from list_card_revisions).
  • list_card_revisionsList card revisionsGETRetrieve a list of all revisions made to the specified card, including the date and time each revision was replaced.

Card sticker, 2 operations

  • add_card_stickerAdd card stickerPOSTAdds a sticker to a card. A sticker can be added several times; set if_not_present=1 to get a 409 instead when it is already on the card.
  • list_card_stickersList card stickersGETGet a list of the stickers added to a card. The stickers are listed in the order in which they were added.

Card tag, 2 operations

  • add_card_tagAdd card tagPUTAdd a tag to a card. list_tags returns every tag of the account, list_board_tags the tags of one board.
  • list_card_tagsList card tagsGETGet a list of all tags that have been added to the specified card.

Card watcher, 2 operations

  • add_card_watcherAdd card watcherPUTAdds a user as a watcher of a card: the user is notified of every change to the card, even without notifications for its board.
  • list_card_watchersList card watchersGETRetrieve a list of the users assigned as a card's watchers.

Child card, 2 operations

  • add_child_cardAdd child cardPUTAssigns the specified card as a child of a specified parent card, establishing a parent-child relationship between them.
  • list_child_cardsList child cardsGETRetrieves a list of child cards associated with the specified parent card.

Parent card, 2 operations

  • add_parent_cardAdd parent cardPUTEstablishes a parent-child relationship between two cards by designating one card as the parent of a specified card.
  • list_parent_cardsList parent cardsGETRetrieve a list of the parent cards of a given card.

Predecessor card, 2 operations

  • add_predecessor_cardAdd predecessor cardPUTCreate or update a predecessor-successor relationship between two cards by designating one card as the predecessor of the specified card.
  • list_predecessor_cardsList predecessor cardsGETRetrieve a list of cards that are predecessors to the specified card. Predecessor cards are linked cards that must be completed before the given card can proceed.

Successor card, 2 operations

  • add_successor_cardAdd successor cardPUTCreate or update a successor-predecessor relationship between two cards by designating one card as the successor of the specified card.
  • list_successor_cardsList successor cardsGETRetrieve a list of cards that are successors to the given card. Successor cards are linked cards that depend on the completion of the specified card to proceed.

Team, 2 operations

  • get_teamGet teamGETGet the details of a single team.
  • list_teamsList teamsGETRetrieves a list of all teams with their relevant details, optionally filtered using various parameters.

Api limit, 1 operation

  • get_api_limitsGet api limitsGETReturns the hourly and minutely API request limits of the account (defaults 600 per hour and 30 per minute).

Board assignee, 1 operation

  • list_board_assigneesList board assigneesGETGet a list of user IDs assigned to a specific board, along with their respective roles.

Board assignee role, 1 operation

  • get_board_assignee_roleGet board assignee roleGETReturns the role of a user assigned to a specific board.

Board structure, 1 operation

  • get_board_structureGet board structureGETReturns the current structure of a board: its workflows, lanes and columns with their ids. Read it before create_card, which needs a lane_id and a column_id.

Board structure revision, 1 operation

  • get_board_structure_revisionGet board structure revisionGETGet the current revision of the board structure for the specified board. The revision number denotes the number of times edits were made to the board structure.

Board user, 1 operation

  • assign_board_userAssign board userPUTAssign a user to a board or update their role.

Card block reason, 1 operation

  • get_card_block_reasonGet card block reasonGETCheck whether a specific card is currently blocked and, if so, the reason for the block.

Card logged time, 1 operation

  • add_card_logged_timeAdd card logged timePOSTAdd a logged time entry to a card or a subtask.

Child card graph, 1 operation

  • get_child_card_graphGet child card graphGETReturns the hierarchy of a card's children as a graph; depth is the level relative to the card: 1 direct child, 2 child of a level 1 card, and so on.

Comments for card, 1 operation

  • list_comments_for_cardsList comments for cardsGETRetrieve comments associated with multiple cards.

Linked card, 1 operation

  • list_linked_cardsList linked cardsGETRetrieve a list of the cards that are linked to a given card ordered by position.

Parent card graph, 1 operation

  • get_parent_card_graphGet parent card graphGETRetrieves not only the immediate parent cards of a specified card.

Predecessor card graph, 1 operation

  • get_predecessor_card_graphGet predecessor card graphGETGet the full list of predecessor cards for a given card, including the predecessor cards of those predecessor cards.

Successor card graph, 1 operation

  • get_successor_card_graphGet successor card graphGETGet the full list of successor cards for a given card, including the successor cards of those successor cards.

Showing the first 120 of 158 endpoints. The rest are in the product, searchable from the workflow builder and from chat.

Use Businessmap from Claude Code, Cursor or Codex

Connect Businessmap in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Businessmap operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Businessmap

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Businessmap once

    Add your Businessmap connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Businessmap integration FAQ

What can you do with the Businessmap integration?

LiveContext exposes 158 operations on Businessmap, covering card, workflow, block reason and board.

Popular integrations

Browse the whole catalog