Breeze is a project management software that helps teams plan, track, and collaborate on projects efficiently.
Breeze is a project management software that helps teams plan, track, and collaborate on projects efficiently. On Nagent, Breeze is exposed as a fully-configurable project management integration that any agent can call — 18 actions, and API key authentication. No code is required to wire Breeze into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Breeze 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 Breeze 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 Breeze, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BREEZE_ADD_PROJECT_PEOPLEAdd people to a Breeze project by inviting them via email. This action invites one or more users to a project by their email addresses. The response returns the complete list of all users currently in the project (including the newly added ones). Use this when you need to give users access to a specific project.
Input parameters
List of email addresses to invite to the project
ID of the project to which people will be added
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
BREEZE_ARCHIVE_PROJECTTool to archive a specific project. Use when you need to hide a completed or inactive project from active views after confirming its details.
Input parameters
Team ID to specify the target team when the user belongs to multiple teams. Provide this parameter if your account has multiple teams.
The unique ID of the project to archive
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
BREEZE_CREATE_CARDTool to create a new card in a project. Use after confirming the project_id. Creates a task with details like name, due date, and assignees.
Input parameters
Name of the new card (task)
List of tags to associate with the card
Due date in ISO 8601 format (e.g., 2025-02-22T16:00:00Z)
List of email addresses to invite to the card
ID of the stage where the card will be placed
Start date in ISO 8601 format (e.g., 2025-02-20T16:00:00Z)
ID of the project where the card will be created
Optional description of the card
ID of the swimlane where the card will be placed
Planned time in minutes
List of custom fields for 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
BREEZE_CREATE_LISTTool to create a new list (stage) in a Breeze project. Use when you've selected a project and need to add a new stage. Example: "Create a new Todo list for project 42."
Input parameters
Name of the new list (stage) to create
ID of the Breeze project to add the new list 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
BREEZE_CREATE_PROJECTCreates a new project in Breeze project management system. Use this action to initialize a new project with a given name. The newly created project will: - Be automatically assigned to the authenticated user as owner - Have default budget values set to 0 - Not be assigned to any workspace initially (can be configured later) - Not be archived by default Returns comprehensive project details including ID, timestamps, budget information, and user assignments.
Input parameters
The name of the new project. Can be any string including special characters, Unicode, and emojis. Empty strings are allowed but not recommended.
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
BREEZE_CREATE_WORKSPACETool to create a new workspace. Use after deciding on the workspace name.
Input parameters
Name of the new workspace (required). Can be any string including empty.
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
BREEZE_DELETE_CARDTool to delete a specific card (task) by its ID. Use when you need to remove a task permanently; deletions cannot be undone.
Input parameters
ID of the card to delete
ID of the project containing 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
BREEZE_DELETE_PROJECTTool to delete a specific project by ID. Use when you need to remove a project after confirming its ID.
Input parameters
Numeric ID of the project to delete. Must be a positive integer.
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
BREEZE_DELETE_PROJECT_PERSONTool to delete a person from a project by user ID. Use after confirming the project and user details. Example: "Delete user 456 from project 123".
Input parameters
Numeric ID of the user/person to remove from the project
Numeric ID of the project from which the user will be removed
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
BREEZE_DELETE_WORKSPACETool to delete a specific workspace by ID. Use when permanently removing a workspace after confirming the correct workspace ID.
Input parameters
The numeric ID of the workspace to delete. Must be a positive integer.
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
BREEZE_GET_CARDTool to retrieve detailed info for a specific card (task) in a project. Use when you know the project_id and card_id and need all metadata like tags, users, todos, and time entries.
Input parameters
ID of the card to retrieve
ID of the project containing 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
BREEZE_GET_CARDSTool to get all cards (tasks) for a specific project. Use after confirming the project exists. Example: "List all cards in project 42."
Input parameters
If set to true, returns archived cards. Defaults to active cards only.
ID of the Breeze project to retrieve cards for
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
BREEZE_GET_PROJECTTool to get a specific project by ID. Use when you need detailed project information after confirming the project ID. Example: "Get project 123 details".
Input parameters
Unique identifier of the project 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
BREEZE_GET_PROJECT_PEOPLETool to get all users in a project. Use when you have a valid project ID and need to list its users.
Input parameters
Numeric ID of the project whose users 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
BREEZE_GET_PROJECTSRetrieves a list of all active (non-archived) projects in Breeze. Returns comprehensive project details including budget, time tracking, assigned users, tags, and metadata. Use this action to: - Get an overview of all current projects - Find specific projects by browsing the list - Access project IDs for use with other project-related actions - Check project budgets, hours tracked, and team assignments Note: Only returns active projects. Use GET_ARCHIVED_PROJECTS to retrieve archived projects.
Input parameters
Team ID to scope the projects to a specific team. Usually not needed as the team is determined by authentication. Only provide this if you need to override the default team or if the authenticated user belongs to multiple teams.
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
BREEZE_GET_WORKSPACETool to get a specific workspace by ID. Use when you need workspace details including projects after confirming the workspace ID.
Input parameters
ID of the workspace 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
BREEZE_GET_WORKSPACESTool to get all workspaces. Use when you need to list available workspaces for the authenticated user.
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
BREEZE_MOVE_CARDTool to move a card to a different stage or position. Use after confirming stage_id and prev_id.
Input parameters
ID of the card to move
ID of the card that should precede the moved card in the new stage
ID of the stage to move the card to
ID of the project containing 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
No publicly available marketplace agent is found using this tool yet. There are 39 agents privately built on Nagent that already use Breeze.
Build on Nagent
Connect Breeze 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 Breeze, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Breeze is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Breeze is connected, you configure its 18 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Breeze 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 Breeze event fires, the agent kicks off automatically.
Every Breeze 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 Breeze ships with 18 pre-built project management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Breeze together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Breeze-based workflows tailored to your business.