Resources · Make integration

Breeze Make integrationAutomate Breeze with Make.

Can Make open, update and tidy your Breeze projects without anyone touching them? The Breeze Make integration gives you 13 modules: 2 triggers, 9 actions and 2 searches. This guide is for project leads who run their work in Breeze, and it walks you from the connection to a first working scenario.

Try the Breeze integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Breeze Make integration do for you?

The Breeze Make integration links your Breeze account to Make, a no-code tool where you build scenarios: automations made of modules, each one a single brick such as a trigger, an action or a search. Make spots new projects and tasks in Breeze, then creates, reads, changes or removes them for you.

Every new project starts with its first task. Watch New Projects picks up a new project at Make's next scheduled check, and Create a Task adds the kickoff item so nobody wonders where to begin.

Tasks from other tools land in Breeze. A form, a support app or a spreadsheet can feed Create a Task, and Search Tasks lets you check first that the same task does not exist already. Pages such as the 123FormBuilder Make integration show the other half of that flow.

Status changes travel back. When a deal closes or a ticket is solved elsewhere, Update a Task or Update a Project keeps Breeze in line, without a copy and paste.

What Make does not give you here: no instant trigger, so Breeze never pushes events to Make; the two triggers wait for the schedule. The Make documentation page for Breeze also warns that its text is AI-generated from the vendor docs, so check anything important with Breeze. When a listed module falls short, Make an API Call reaches the rest of the Breeze API with the same connection.

Breeze may also have an n8n node. The n8n vs Make comparison lays out how the two tools differ, and the Make training is there if you want to go further with scenarios.

Connect

How do you connect your Breeze account to Make?

  1. 01

    Copy your API token from Breeze

    You need an active Breeze account first. In Breeze, open your profile settings: the API token is displayed there. Copy it and keep the tab open, since Make will ask for it in a moment.

  2. 02

    Add a Breeze module in Make

    Log in to Make, open your scenario and add any Breeze module. In the module panel, click Create a connection. A connection is your Breeze account linked to Make once, then reused by every Breeze module.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear name helps when several accounts coexist. Paste the token you copied, or follow the on-screen instructions, then save. Make can now read your Breeze projects.

First scenario

Your first scenario: a kickoff task for every new Breeze project

GoalWhen a new project appears in Breeze, Make adds a first task to it so the team knows where to start.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for Breeze and pick Watch New Projects.

  2. 02

    Link your account

    Click Create a connection and paste your Breeze API token. Once the connection exists, Make can list what it reads from your Breeze account in the module fields.

  3. 03

    Add the task module

    Click the + on the right of the trigger and choose Create a Task. Map data from the trigger into its fields, so the task lands in the project Make just found.

  4. 04

    Test with Run once

    Create a test project in Breeze, then click Run once. Open the bubbles above each module to read the bundles, the items passed from one module to the next.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What starts a Breeze scenario

2 modules start a scenario when something happens in Breeze. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Breeze as soon as it happens.

Breeze1Watch New Projects

Watch New Projects

triggerIn the docs only

Watch New Projects hands your scenario every project created in Breeze since the last check, one bundle per project, so the follow-up work starts without anyone opening the app.

How it fires
scheduled, Make checks Breeze on the scenario's schedule, which is every 15 minutes by default and never shorter than 15 minutes on the Free plan. The type comes from the module name, since the documentation lists no instant tag.
When to use it
when a new project should trigger a setup routine, such as a kickoff task or a message to the people involved.
Watch out
a project created between two checks waits for the next run, so this trigger is not built for alerts that must go out on the spot.
Breeze2Watch New Tasks

Watch New Tasks

triggerIn the docs only

With Watch New Tasks, each task added in Breeze becomes a bundle your scenario can copy, announce or log elsewhere, which keeps other tools aware of the work without manual exports.

How it fires
scheduled, Make checks Breeze on the scenario's schedule rather than being called by Breeze, 15 minutes apart by default. The documentation shows no instant tag for it, so the scheduled type is read from its name.
When to use it
when new tasks must reach a chat channel, a spreadsheet or a reporting tool that your team reads.
Watch out
do not pair it with Create a Task in the same scenario, or every task the scenario creates is picked up again on the next run.
Modules

Every Breeze module, and when to pick it

Breeze gives you 11 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Breeze1

Create a Project

ActionIn the docs only

Create a Project opens a new project in Breeze from data another app sends, so a signed deal or an accepted quote turns into a workspace without retyping.

When to use it
when a sale closes in your CRM and the delivery team needs its project straight away.
Watch out
run List Projects first if the same event can fire twice, or you end up with two identical projects.
Breeze2

Create a Task

ActionIn the docs only

This module adds a task to Breeze each time the scenario reaches it, which turns a form entry, an email or a ticket into a to-do your team actually sees.

When to use it
when requests arrive outside Breeze and must end up in the right project.
Watch out
Search Tasks before it avoids duplicates when the source can send the same request again.
Breeze3

Delete a Project

ActionIn the docs only

Delete a Project removes a Breeze project, which keeps your list clean when a deal falls through or a test project was created by mistake.

When to use it
after a filter in the scenario has confirmed the project really must go.
Watch out
nothing on this page says a deleted project can be recovered, so test on a dummy project with Run once before you point it at real work.
Breeze4

Delete a Task

ActionIn the docs only

Removing a single task is what this module does, and it saves someone the cleanup when a request is cancelled in the tool it came from.

When to use it
when a ticket or form entry is withdrawn and its twin task in Breeze no longer makes sense.
Watch out
nothing here says a deleted task comes back, so feed it the exact task found by Get a Task or Search Tasks, never a guess.
Breeze5

Get a Project

ActionIn the docs only

Get a Project fetches one Breeze project you already know, and its details become available to every module placed after it in the scenario.

When to use it
when an earlier module gives you the project reference and you need the rest of its information for a message or a report.
Watch out
it reads one known project; to look through several, List Projects is the module to pick.
Breeze6

Get a Task

ActionIn the docs only

Reading one task in full is the point of Get a Task, handy when a trigger only passes along part of what you need to write a useful notification.

When to use it
right after Watch New Tasks, or before an update, to check the current state of that task.
Watch out
it expects a task you can already identify; when you only know a keyword, start with Search Tasks.
Breeze7

List Projects

SearchIn the docs only

List Projects returns your Breeze projects as separate bundles, so the following modules run once for each project in the list.

When to use it
when you build a portfolio overview in a spreadsheet, or check whether a project already exists before creating one.
Watch out
as a search, it can return zero, one or many projects, and every module after it then runs, and counts operations, once per project.
Breeze8

Make an API Call

ActionIn the docs only

Make an API Call covers what the other Breeze modules leave out: it calls any endpoint of the Breeze API while reusing the connection you already created.

When to use it
when the operation you need has no dedicated module in the list above.
Watch out
you write the request yourself, so keep the Breeze API documentation at hand; this page does not cover its endpoints.
Breeze9

Search Tasks

SearchIn the docs only

Search Tasks finds the Breeze tasks that match what you are looking for and passes each one on as its own bundle, ready to be updated, deleted or reported.

When to use it
before creating a task, to make sure the same request has not been logged already.
Watch out
a search can come back empty; add a filter after it so the next module does not act on nothing.
Breeze10

Update a Project

ActionIn the docs only

Update a Project changes an existing Breeze project with fresh data from elsewhere, so the project page reflects what your other tools already know.

When to use it
when a contract is amended or a client record changes and the matching project should follow.
Watch out
map only the fields you mean to change, and point it at the project returned by Get a Project or List Projects.
Breeze11

Update a Task

ActionIn the docs only

Keeping a task in step with the outside world is the job of Update a Task, for example when the ticket behind it is solved in your help desk.

When to use it
when the same work moves forward in another app and Breeze should show the same thing.
Watch out
updating tasks inside a scenario started by Watch New Tasks is fine, since changes are not new tasks, but test with Run once first.
Need help

Need help automating Breeze with Make?

A person reads every message.

FAQ

Breeze and Make: common questions

01Is the Breeze Make integration free?
Yes, on the Make side. Breeze is a standard app, so its modules work on the Free plan, which allows 2 active scenarios, runs no closer than 15 minutes apart, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. You still need an active Breeze account, and its subscription is set on the Breeze pricing page, not by Make.
02What do you need to connect Breeze to Make?
An active Breeze account and its API token. The token is displayed in your Breeze profile settings, where you copy it. In Make, add a Breeze module, click Create a connection, optionally name the connection, then paste the token or follow the on-screen instructions. That single connection is then reused by every Breeze module in your scenarios, so you only do this once per account. No other prerequisite appears in the Make documentation for Breeze.
03Do Breeze triggers in Make fire in real time?
No. Watch New Projects and Watch New Tasks are scheduled triggers: Make checks Breeze on the scenario's schedule, every 15 minutes by default, and at best every 1 minute on a paid plan. The documentation lists no instant tag for them, which is where this reading of their type comes from. If you need a reaction as close as possible to the event, shorten the schedule within what your plan allows rather than expecting Breeze to call Make.
04What if a Breeze module you need is missing in Make?
It depends on the task, but Make an API Call usually solves it. This module calls any endpoint of the Breeze API with the connection you already have, so an operation without a dedicated module stays within reach. You write the request yourself, based on the Breeze API documentation. Keep in mind that the Make help page for Breeze is marked as AI-generated from the vendor documentation, so confirm important details with Breeze before relying on them.
05Should you use Make or n8n for Breeze?
It depends on the tool you already run. Breeze may also have an n8n node, so both routes can exist. With Make, you get 13 ready modules, including 2 scheduled triggers and Make an API Call for the rest, plus a visual editor where Run once shows every bundle. The sensible choice is the platform your team already uses for its other automations, so all scenarios live in one place and share the same habits.
Same platform

Other docs you might need on this stack.

Browse all integrations