Productivity · Integration
Breeze
Add Breeze to your product for your customers, and give your AI agents governed access to it.
Breeze is a lightweight project tool whose API sits at api.breeze.pm, and the authentication style is the first surprise: the key travels as an api_token query parameter rather than a header, so a call with the parameter returns 401 for a bad token while a call without it fails outright with a 500. Because the credential rides in the URL it lands in access logs and proxy traces, so requests should never be logged verbatim. The hierarchy is project, then task list, then task, and task lists are the board columns rather than a separate labelling concept, which means moving a task between stages is a change of list rather than a status field update. Tasks carry assignees, due dates and estimated hours, and time entries are separate objects logged against a task, so reporting effort requires reading both. Endpoints are nested under the project id, so a cross-project view has to be assembled client-side from per-project calls rather than requested in one go. fastn holds each customer's Breeze token, keeps it out of your logs, and maintains the connection so your team is not chasing endpoint changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Breeze account and choose which projects your product syncs
Create a Breeze task automatically when something in your product needs follow-up, assigned to the right person
Roll up time entries per project into your invoicing or reporting screens
Mirror task list positions so your UI shows the same board stages the customer sees in Breeze
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent create a task in a named project with a due date, restricted to projects the tenant approved
Have an agent report tasks overdue by more than a week across a tenant's projects, audited per tenant
Let an agent move a task to a different list only when a human confirms the stage change
Example prompt
Which tasks on the website rebuild are overdue and who are they assigned to?
Set up Breeze in 4 steps
- 01Enable the Breeze connector from your fastn dashboard.
- 02Have each customer authorise their own Breeze account, so calls run under their credentials rather than a shared key.
- 03Decide which work items, assignees and due dates your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Breeze integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Breeze integration without building it. Your customers connect their own Breeze account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Breeze update is not your on-call problem.
- One integration serves your product and your agents. The same governed Breeze connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Jira
Asana
ClickUpOften used alongside
Tools the same teams tend to run next to Breeze, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceBreeze integration FAQ
How do I add a Breeze integration to my product?
Enable the Breeze connector in your fastn dashboard, then let each customer authenticate their own Breeze account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Breeze client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Breeze account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Breeze account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Breeze integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent create a task in a named project with a due date, restricted to projects the tenant approved
Who maintains the Breeze integration?
fastn does. When Breeze changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Breeze automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Breeze can trigger your workflows in return.
Does it adapt to each team's own Breeze setup?
Yes. However a team has configured Breeze, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Breeze integration?
A common starting point: let a customer connect their own Breeze account and choose which projects your product syncs. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Breeze integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Breeze does not change your per-connector cost. You can start free with 3 connected accounts.
Add Breeze to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.