Breeze for AI agents
Agents read Breeze at once. Changes and sends are held for a person's approval by default.
About Breeze
Breeze is a project management software that helps teams plan, track, and collaborate on projects efficiently.
What an agent can do in Breeze
Every Breeze action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Breeze without asking first. 7 actions.
- 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.
- GET_CARDSTool to get all cards (tasks) for a specific project. Use after confirming the project exists. Example: "List all cards in project 42."
- 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".
- Get Project PeopleTool to get all users in a project. Use when you have a valid project ID and need to list its users.
- 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 a
- Get WorkspaceTool to get a specific workspace by ID. Use when you need workspace details including projects after confirming the workspace ID.
- Get WorkspacesTool to get all workspaces. Use when you need to list available workspaces for the authenticated user.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 11 actions.
- 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
- 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.
- 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.
- 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."
- 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 authenticat
- Create WorkspaceTool to create a new workspace. Use after deciding on the workspace name.
- Delete CardTool to delete a specific card (task) by its ID. Use when you need to remove a task permanently; deletions cannot be undone.
- Delete ProjectTool to delete a specific project by ID. Use when you need to remove a project after confirming its ID.
- Delete Person from ProjectTool 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".
- Delete WorkspaceTool to delete a specific workspace by ID. Use when permanently removing a workspace after confirming the correct workspace ID.
- Move CardTool to move a card to a different stage or position. Use after confirming stage_id and prev_id.
Changes wait in Needs you
Changes and sends in Breeze are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Breeze questions
Can an agent change data in Breeze on its own?
Not by default. Changes and sends in Breeze are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Breeze?
This connector lists 7 read actions. Reads run at once, without waiting for approval.
How does Breeze connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.