Kanbanize is designed to help advanced product teams apply the principles of Lean and Kanban to their work to maximize results.
Kanbanize is designed to help advanced product teams apply the principles of Lean and Kanban to their work to maximize results. On Nagent, Kanbanize is exposed as a fully-configurable project management integration that any agent can call — 24 actions, and API key authentication. No code is required to wire Kanbanize into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Kanbanize to automate the kinds of tasks project management teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Kanbanize into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Kanbanize, with input parameters and output schema. Drop these into any step of an agent built in Helix.
KANBANIZE_ADD_CARD_COMMENTTool to add a comment to a Kanbanize card. Use when you need to add notes, updates, or any text-based information to an existing card.
Input parameters
The comment text content to add to the card.
The ID of the card to add a comment to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_CHECK_BOARD_MILESTONETool to check if a milestone is available on the specified board. Use when you need to verify milestone existence on a specific board. Returns True if the milestone is available (HTTP 204), False if not found (HTTP 404).
Input parameters
A board ID to check the milestone on.
A milestone ID to check if it is available on the specified board.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_CHECK_USER_IS_CARD_WATCHERTool to check if a user is a watcher of a specific card. Use when you need to verify if a user is watching a card.
Input parameters
A card ID.
A user ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_DELETE_BOARDTool to delete a board by its ID. Use when you need to permanently remove a board from Kanbanize. Note: The board must be archived before deletion.
Input parameters
The ID of the board to delete. Note: The board must be archived before it can be deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_DELETE_CARDTool to delete a card from the Kanbanize board. Use when you need to permanently remove a card and all its associated data from the board.
Input parameters
The ID of the card to delete from the Kanbanize board.
Optional reason to exceed a limit when deleting the card. Provide this when card deletion may exceed workflow limits or constraints.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_DELETE_TAGTool to delete a tag from Kanbanize. Use when removing a tag and optionally replacing it with another tag for all affected cards.
Input parameters
A tag ID.
The ID of the tag that will replace the deleted tag for **all** affected cards.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_DELETE_WORKFLOWTool to delete a workflow for the specified board. Use when you need to permanently remove a workflow from a board.
Input parameters
A board ID.
A workflow ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_BOARD_BLOCK_REASONSTool to get a list of block reasons available on a board. Use when you need to retrieve available block reasons for a specific board.
Input parameters
A board ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_BOARD_CARD_TEMPLATESTool to retrieve a list of card templates available on a Kanbanize board. Use when you need to see what card templates are configured for a specific board.
Input parameters
The unique identifier of the board to retrieve card templates from.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_CHILD_CARDSTool to retrieve a list of child cards for a specified parent card. Use when you need to view all cards that are children of a given parent card in the Kanbanize hierarchy.
Input parameters
Page number for pagination. If not specified, defaults to page 1
The unique identifier of the parent card whose children you want to retrieve
Number of results per page. Default is 100, maximum is 200
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_COLUMNTool to get the details of a specific column from a Kanbanize board. Use when you need to retrieve column information such as name, WIP limit, card ordering, or workflow configuration.
Input parameters
The ID of the board that contains the column.
The ID of the column to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_COLUMNSTool to get a list of columns for a specific board in Kanbanize. Use when you need to retrieve all columns configured for a board, including their workflow assignments, positions, limits, and display settings.
Input parameters
The unique identifier of the board to retrieve columns from.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_CUSTOM_FIELDSTool to retrieve a list of custom fields from Kanbanize with optional filtering. Use when you need to fetch custom field definitions, filter by field IDs, name, availability level, enabled status, types, or retrieve additional details like boards, card counts, and business rules.
Input parameters
Filters custom fields by their exact name.
A list of the types of custom fields you want to retrieve.
A list of properties for which additional details should be included in the response. Options: allowed_values, boards, board_count, card_count, outcome_count, default_contributors, business_rules.
A list of custom field IDs used to filter the returned custom fields. Example: \[1, 2, 3\]
Enum for enabled status.
A list of the availability levels by which to filter the custom fields. 0 = On-demand (can be manually added/removed from boards), 1 = Auto (automatically added to all newly created boards), 2 = Global (automatically added to all boards across all workspaces).
Enum for immutable status.
Enum for always present status.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_STICKERSTool to retrieve a list of stickers with optional filtering by sticker IDs, label, availability, and enabled status. Use when you need to fetch stickers from Kanbanize to apply to cards or to view available stickers in the system.
Input parameters
The full label of the sticker to search for. If provided, only stickers matching this label will be returned.
Filter stickers by enabled status. Use 0 for disabled stickers, 1 for enabled stickers. If not provided, all stickers are returned.
An array of sticker IDs to filter the results. If provided, only stickers with these IDs will be returned.
An array of availability values to filter stickers. Common values are board-specific availability levels.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_USERTool to get the details of a specified user in Kanbanize. Use when you need to retrieve information about a user such as their username, email, real name, avatar, enabled status, language preferences, timezone, and other attributes.
Input parameters
The unique identifier of the user to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_WORKFLOW_CYCLE_TIME_COLUMNSTool to retrieve workflow's cycle time columns from a Kanbanize board. Use when you need to identify which columns are included in cycle time calculations for a specific workflow.
Input parameters
A board ID.
A workflow ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_GET_WORKSPACE_DATA_FIELDSTool to retrieve a list of data fields available on a workspace. Use when you need to fetch all custom data fields configured for a specific Kanbanize workspace.
Input parameters
A workspace ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_REMOVE_BOARD_BLOCK_REASONTool to make a block reason unavailable on a board. Use when you need to remove a specific block reason from a board's available options.
Input parameters
A board ID.
A block reason ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_REMOVE_CHILD_CARDTool to remove the link between a parent card and a child card. Use when you need to unlink a child card from its parent card in Kanbanize.
Input parameters
A card ID.
A child card ID.
The reason for exceeding the specified limit.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_SET_CARD_BLOCK_REASONTool to block a Kanbanize card by setting a block reason. Use when you need to mark a card as blocked and specify the reason preventing progress.
Input parameters
The ID of the card to block
The ID of the block reason to apply to the card
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_UPDATE_BOARD_STICKERTool to update the properties of a sticker for the specified board. Use when you need to modify usage limits for a sticker on a board or card.
Input parameters
A board ID.
A sticker ID.
The maximum number of times the sticker can be used on a single card. Use 0 for unlimited.
The maximum number of times the sticker can be used on the board. Use 0 for unlimited.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_UPDATE_DATA_FIELD_WORKSPACESTool to add, update, or remove a data field on one or more workspaces via batch operations. Use when you need to configure data field availability and settings across multiple workspaces.
Input parameters
The data field ID to perform operations on.
List of workspace IDs where the data field should be made unavailable.
List of workspaces where the data field should be added or updated. Each entry must include workspace_id.
List of workspace IDs where the 'apply to all boards in workspace' setting should be enabled.
List of workspace IDs where the 'apply to all boards in workspace' setting should be disabled.
List of workspace IDs where the 'value is locked for all boards in workspace' setting should be enabled.
List of workspace IDs where the 'value is locked for all boards in workspace' setting should be disabled.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_UPDATE_LANE_DEFAULT_SETTINGTool to update the default value of a specific lane setting in Kanbanize. Use when you need to modify default settings for a lane on a board.
Input parameters
The new value of the setting.
A lane ID.
A board ID.
A setting name (e.g., 'lane_settings.default_template').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
KANBANIZE_UPDATE_TAGTool to update the specified tag in Kanbanize. Use when you need to modify tag properties like label, color, availability, or enabled status.
Input parameters
The color of the tag in hexadecimal format.
The unique label (i.e. the name) assigned to the tag.
A tag ID.
Tag enabled status.
Tag availability levels.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 51 agents privately built on Nagent that already use Kanbanize.
Build on Nagent
Connect Kanbanize to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Kanbanize, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Kanbanize is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Kanbanize is connected, you configure its 24 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Kanbanize steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Kanbanize event fires, the agent kicks off automatically.
Every Kanbanize action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Kanbanize ships with 24 pre-built project management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Kanbanize together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Kanbanize-based workflows tailored to your business.