Breeze

Breeze is project management built around boards of cards with time tracking built in. Agents create and move cards, assign work, add comments, log time and read board status so project boards reflect what is happening elsewhere.

Verified 56 actions API key available

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

A client request arrives through the intake form or the shared inbox

Agent reads the requester, the deliverable and the date they asked for

List Users confirms whether the intended owner's email address is already on the Breeze team

Create Card opens the card in the project's intake list, with custom fields supplied by name

Create Todo List and Create Todo add the standard steps that deliverable always needs

Agent posts the card and the proposed owner to the studio lead

The studio lead confirms the assignment, because assigning an address not already on the team invites that person into the account

What This Integration Enables

Breeze is a board of cards with time tracking built into the card rather than bolted alongside it. One property of its API shapes every flow you build here and is worth knowing before the first write: a Breeze API token identifies one person, not an application. Time entries are always attributed to the user whose token it is, and there is no way to log or edit time on somebody else's behalf. Comments are posted as that person. People are addressed by email address rather than by internal id, on projects and on cards alike. An agent on Breeze is never anonymous, and never acts on behalf of the team in general.

That turns out to suit the work. FlowRunner agents create cards from intake, fill in checklists that a deliverable always needs, move cards as the work advances, read running timers to answer who is on what, and run the time tracking report on a relative window so a monthly billing pass needs no date arithmetic. Where Breeze's email-first addressing makes an assignment reach outside the team, that is where FlowRunner puts a person. Every action here is built and verified against the Breeze API.

Without FlowRunner

Requests land in an inbox, not on a board Work exists as an email until somebody has time to turn it into a card

Standard steps recreated per job The same checklist is retyped for every deliverable of the same kind

Time reports pulled by hand each month Someone opens the reporting screen, sets the window, and copies the totals out

With FlowRunner

Requests arrive as cards with their steps in place Intake creates the card, its checklist and its custom fields in one pass

The board says who is working now Running timers and activity are read directly, so the answer does not depend on asking

The monthly report runs itself The time tracking report runs on a relative window and posts its totals where billing starts

Use Case Scenarios

Intake becomes a prepared card

A request arrives through a form in Jotform or as mail in Gmail. The agent calls Create Card in the project's intake list, supplying custom fields by name so nothing has to be looked up first, then Create Todo List and Create Todo to add the steps that deliverable always carries. Move Card places it in the right column for its current state, and Create Comment records where the request came from and what the agent inferred. The designer picking it up finds a card that is already scoped rather than a one-line title.
Who is working on what, answered without asking

List Running Timers returns the timers currently going across the team, which is the closest thing to a live view of the studio. The agent pairs that with List Activity, narrowed to a project or a person, to answer what changed and who changed it. When a card has been sitting in a column past a threshold, or when a project has open cards and no running timer against it for several days, the agent posts the exception into Slack rather than a daily status list nobody reads. The standup becomes shorter because the facts arrive before it.
Month end billing from the board's own report

Run Time Tracking Report accepts a relative period such as last month as well as explicit dates, which is what makes a scheduled report possible without recomputing the window each run. On the first working day of the month, the agent runs it across the chosen projects, people and tags, reconciles the totals against each project's budget and hourly rate from List Projects, and posts a per-client summary to the account lead. Once approved, the same figures become draft invoices in Xero, so the hours a client is billed for are the hours the board recorded.

Human-in-Loop Highlight

Breeze addresses people by email address rather than by internal id, and it is generous about what it does with one it does not recognize. Add Project People and Assign Card People both invite anyone who is not already on the team, which means a real invitation email goes to that address and a person who was never meant to be in your account now has a way in. Nothing about that fails loudly. A stale contact address in a CRM record, a client's address copied into an owner field, or a simple typo all produce the same outcome: a successful call and an invitation sent. So the routing agent checks first with List Users and stops when the address is unfamiliar: "The intake record names [email protected] as the owner of this card. That address is not on the Breeze team. Assigning it will send them an invitation and add them to the account. Assign anyway, pick someone from the team, or leave the card unassigned in triage?" The studio lead answers. The agent never guesses that an unknown address was meant to be a colleague.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

56 actions

Account and Team

Get Current User Retrieves the account the API token belongs to, including the teams it is a member of. Read first when the account belongs to more than one team, because every other call names which team it means.
List Users Retrieves the people in the team. Their ids and email addresses are what the assignment and report operations expect, and this is the read that tells an unfamiliar address from a colleague.

Workspaces

List Workspaces Retrieves the workspaces in the team. A workspace groups projects.
Get Workspace Retrieves one workspace by its id.
Create Workspace Creates a workspace to group projects under, for example one per client.
Update Workspace Renames a workspace.
Delete Workspace Deletes a workspace. Worth checking what still lives inside it first, because a workspace is a container for projects.

Projects

List Projects Retrieves the projects in the team, with their budgets and hourly rates. Breeze returns the whole list in one response rather than paging.
Get Project Retrieves one project by its id, including its budget and rate.
Create Project Creates a project, optionally inside a workspace and with a budget. People are invited by email address, so a new collaborator can be added in the same call.
Update Project Updates a project's name, description, budget or rate. Only the fields supplied are sent.
Delete Project Permanently deletes a project with its cards, lists and tracked time. Archiving is the alternative when the work is simply finished.
Set Project Archived Archives a project or brings it back. The reversible way to take a finished engagement off the board.
List Project People Retrieves the people on a project.
Add Project People Adds people to a project by email address. Breeze invites anyone who is not already on the team, so this can send a real invitation email.
Remove Project Person Removes a person from a project. Time they already logged against it is kept.

Cards

List Project Cards Retrieves the cards of a project. A card is Breeze's unit of work, carrying its list, swimlane, dates, assignees, checklists and time entries.
List Cards In List Retrieves the cards sitting in one list of a project, which is how a single column of the board is read.
List Cards In Swimlane Retrieves the cards sitting in one swimlane, which is how a single row is read.
List All Cards Retrieves cards across every project. Used when the question is everything due this week rather than one project's board.
Get Card Retrieves one card by its id. The response carries its time entries, checklists and comments, so this is often the only read a flow needs.
Create Card Creates a card in a project. People are assigned by email address and custom fields are supplied by name, so a card can be created without looking either up first.
Update Card Updates a card's editable fields. Only what is supplied is sent, and moving between lists is a separate operation.
Delete Card Permanently deletes a card with its comments, checklists and time entries.
Move Card Moves a card into a different list, optionally placing it after a specific card. This is how progress is recorded on a Breeze board.
Assign Card People Assigns people to a card by email address. Breeze invites anyone who is not already on the team, which is the operation the human gate on this page exists for.
Unassign Card Person Removes a person from a card. Time they already logged against it is kept.

Board Structure

List Lists Retrieves the lists of a project. Breeze calls the board's columns stages in its API and lists in its interface; they are the same thing.
Create List Adds a list to a project's board.
Update List Renames a list on a project's board.
Move List Reorders a list on the board by placing it after another one.
Delete List Removes a list from a project's board. Worth checking what is still in it first, because a list is a container for cards.
List Swimlanes Retrieves the swimlanes of a project. Swimlanes are the board's rows, cutting across every list.
Create Swimlane Adds a swimlane to a project's board, for example one per client or per workstream.
Update Swimlane Renames a swimlane on a project's board.
Delete Swimlane Removes a swimlane from a project's board.

Time Tracking

List Card Time Entries Retrieves the time logged against one card. The same entries are also embedded in the full card read.
Create Time Entry Logs time against a card, in minutes. Breeze always attributes the entry to the user whose API token this is, so there is no logging time on somebody else's behalf.
Update Time Entry Changes a time entry's amount, date or note. Breeze updates the entry belonging to the token's own user, so this cannot edit somebody else's time.
Delete Time Entry Permanently deletes a time entry from a card. The minutes come off every total that included them.
List Running Timers Retrieves the timers currently running across the team, which is how a flow tells who is actively working and on what.

Comments

List Card Comments Retrieves the comments on a card.
Create Comment Adds a comment to a card, attributed to the user whose API token this is. Used to record what an agent found and where a request came from.
Update Comment Rewrites the text of a comment on a card.
Delete Comment Permanently deletes a comment from a card.

Checklists

List Todo Lists Retrieves the checklists on a card. A card can carry several, each with its own items.
Create Todo List Adds a checklist to a card, which is how a deliverable's standard steps land on it.
Delete Todo List Removes a checklist from a card, with the items inside it.
List Todos Retrieves the items in one of a card's checklists.
Create Todo Adds an item to one of a card's checklists.
Update Todo Renames a checklist item or ticks it off.
Delete Todo Removes an item from one of a card's checklists.

Activity and Notifications

List Activity Retrieves the activity feed, optionally narrowed to one project, one person, or both. The read that answers what changed and who changed it.
List Notifications Retrieves the notifications for the account the token belongs to.
Update Notification Updates a notification, which is how one is marked read.

Reporting

Run Time Tracking Report Runs the time tracking report across chosen projects, people, lists and tags. The period accepts a relative word such as last month as well as explicit dates, which is what makes a scheduled billing report possible without recomputing the window each run.

Frequently Asked Questions

What can FlowRunner do with Breeze?

FlowRunner agents can run Get Current User, List Users, and List Workspaces in Breeze, plus 53 more actions.

Does connecting Breeze to FlowRunner require OAuth?

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

Can Breeze trigger a FlowRunner workflow automatically?

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

Start building with Breeze

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us