Breeze Zapier integrationAutomate Breeze with Zapier.
The Breeze Zapier integration gives you 7 triggers, 2 actions and 1 search, and it works on the free plan. Below: what each operation does for a project team, what it costs in tasks, and the few places where a Breeze Zap stops doing what you expected.
Verified Trustpilot reviews · AI, automation & growth agency
What the Breeze Zapier integration actually does
Breeze is a lightweight project management tool where a team plans its work as projects, lists and tasks. Connected to Zapier, it can start an automation when something moves on a board, and it can receive new projects and tasks sent from other tools. You set it up once, then the board stays in step without anyone copying things across by hand.
Three outcomes come up again and again. A kickoff task in every new project: New Project starts the Zap and Create New Task drops the first to-do in place, so nobody forgets the brief. A heads-up when work changes hands: Task Moved or Task Status Updated can tell another tool that a card reached review. Projects opened from outside Breeze: a signed deal in your sales tool can call Create New Project, with Find Project checking first that the name is not already taken.
Now the honest part. The visible Breeze operations only create things: there is no action to update, move, tag or close a task, and no action to delete anything. Every trigger on this app works by polling, so none of them is instant, and on the free plan a change can wait up to 15 minutes before the Zap notices it. If a scenario needs a task edited after it exists, Zapier alone will not do it with this app.
The same app also exists on the other big automation platform: the Breeze Make integration covers it there, and the Make vs Zapier page is there if you are still choosing a platform.
Zapier words in one minute
Seven terms come back on every Zapier page. Here they are once, in plain English, so the rest reads easily.
- Zap
- The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event.
- Action
- What the Zap does once it has started: the step that writes, sends or creates something for you.
- Task
- The unit Zapier bills. One task is one action your Zap completed successfully; your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment it happens.
- Filter
- A step that lets the Zap continue only when the incoming item meets your condition, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, so later steps can use what it found.
What a Breeze Zap really costs
Breeze is not a premium app, so it runs on the free plan. The free plan has a catch, though: it only builds Zaps of two steps, one trigger and one action.
- Free plan100 tasks per month, unlimited Zaps
- Free plan stepsOne trigger and one action only
- Breeze on freeYes, not a premium app
- BilledEach successful action, never the trigger
The trigger never costs a task, and neither do Zapier's checks for new items, however often they run. Each action that succeeds counts once; an action that fails is not billed. Add a filter or a Find Project search and the Zap becomes a multi-step Zap, which needs a paid plan. Since all seven Breeze triggers are polling triggers, your plan also decides how quickly a change on the board shows up in the Zap, which matters more here than on apps with instant triggers.
Connect your Breeze account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Breeze account linked once, then reused by every step that touches Breeze.
- 02
Pick Breeze and confirm
Type Breeze in the search box of the dialog, select it, then click Add connection. You need an existing Breeze account before this step, with the projects the Zap will use already visible to your user.
- 03
Sign in and grant access
Log in to Breeze in the tab that opens and allow Zapier to reach your account. If the Zap must touch projects someone else owns, your Breeze user needs read or write access to them.
Your first Zap: a kickoff task for client projects
GoalEvery new Breeze project whose name marks it as a client job gets a first task called Kickoff call.
- 01
Build the trigger
Create a new Zap, choose Breeze as the app and New Project as the event, then pick your Breeze connection. This trigger is polling, so Zapier checks on your plan's interval.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent projects from your account, so you can pick a real one and map from it instead of guessing.
- 03
Add the filter
Click the plus icon, add a Filter, and set three boxes: the project name, a text rule such as contains, and the word Client. This step makes it a multi-step Zap, so a paid plan.
- 04
Add the action
Add Breeze again with Create New Task. Map the project from the trigger into Project and type Kickoff call as the Task Name. Both fields are required.
- 05
Test, then publish
Test the action and open Breeze to check the task really landed in the right project. When it looks right, click Publish to switch the Zap on.
Breeze triggers: 7 polling events
7 events start a Zap when something happens in Breeze. Zapier checks for them at the interval your plan allows.
Task Moved
Polling triggerIn Zapier“Triggers when a task is moved to another list.”
Starts your Zap when someone drags a task from one list to another, for example from In progress to Review. It is the closest thing Breeze offers to a workflow stage change.
Task Status Updated
Polling triggerIn Zapier“Triggers when a task's status is updated.”
Fires when the status of a task changes in Breeze. Use it when your team tracks progress with statuses rather than by moving cards between lists, since the two are separate events here.
Tag Added to Task
Polling triggerIn Zapier“Triggers when a tag is added to a task.”
Reacts when a tag lands on a task. Adding a tag is a deliberate gesture, which makes this trigger a handy manual switch: add the tag, and the automation runs.
New Task
Polling triggerIn Zapier“Triggers when a new task is created.”
Picks up each task created in Breeze, whoever created it and in whichever project. It is the broadest Breeze trigger, so it suits Zaps that log or mirror work rather than react to one precise change.
New File
Polling triggerIn Zapier“Triggers when a new file is added.”
Runs when a file is added in Breeze. This trigger lets the rest of your tools know a deliverable is there.
New Project
Polling triggerIn Zapier“Triggers when a new project is created.”
Starts the Zap each time a project is created in Breeze. Because a project usually comes with a standard set of first steps, this is the natural trigger for setting up everything around it.
Project Renamed
Polling triggerIn Zapier“Triggers when a project is renamed.”
Fires when a Breeze project gets a new name. Names often carry the client or the phase, so a rename can be a signal that something changed in the project's life, not just a typo fix.
Breeze actions: 2 ways to create work
Breeze gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create New Project
ActionIn Zapier“Creates a new project.”
Opens a fresh project in Breeze from whatever happened in another tool. Only the Project Name is required, so the action stays simple to map.
Create New Task
ActionIn Zapier“Creates a new project task.”
Adds a task to an existing Breeze project. It needs two things: the Project it belongs to and a Task Name.
The Breeze search: Find Project
1 search step looks for data that already exists in Breeze, so a later step can use it.
A search step looks for something that already exists, then hands it to the next steps. Searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not clean.
Find Project
SearchIn Zapier“Finds a project by name.”
Looks up a Breeze project by its name and hands it to the following steps. Part of the name is enough to get matches, which is convenient but also loose.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into find-or-create. Breeze offers no such variant for Find Project, so the box does not apply here.
- If multiple search results are found?Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When a Breeze Zap breaks
Zapier links no help article to Breeze and lists no Breeze-specific limit, so what follows comes from how Zapier itself behaves.
Four situations are worth knowing on this app. If one of them does not match yours, the Zapier troubleshooting page is the next stop.
Old projects are ignored
A Zap only reacts to what happens after you publish it. Projects, tasks and files that existed before are never picked up; moving that backlog is a separate job.A Zap that triggers itself
New Task plus Create New Task in one Zap: each task created starts another run. The loop keeps going and eats your task count quickly.A bulk import goes quiet
After importing a large batch of tasks, the trigger can return a huge pile at once, and Zapier's flood protection may hold it back.The same item never runs twice
Zapier remembers what a polling trigger has already seen. An item it has already seen will not start the Zap a second time, which keeps duplicates out.
Need help automating Breeze with Zapier?
A person reads every message.
