Resources · Make integration

Cloze Make integrationAutomate Cloze with Make.

Can Cloze keep your follow-ups moving on its own? The Cloze Make integration offers 22 modules: 3 instant triggers, 16 actions and 3 searches. This guide is for sales and ops teams new to Make, from the first connection to a scenario that runs.

Try the Cloze integration on MakeSee the 22 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cloze Make integration do for you?

The Cloze Make integration links your Cloze account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, finds or changes something. Cloze can wake a scenario the moment a company, a person or a project changes stage, and Make then writes back to Cloze or to any other app you use.

A follow-up task that writes itself. When a contact reaches a new stage, Watch Person Audit Changed starts the scenario and Create a To Do puts the next call on the list. Nobody has to remember it after the meeting.

Leads that land in Cloze without copy and paste. A form entry or a spreadsheet row from another app goes through Find People first, to see whether the contact already exists, and then Create a Person or Update a Person does the rest.

Project news the whole team sees. Watch Project Audit Changed reacts when a project moves to another segment, stage or step, and the scenario can post the update in your team chat or file a note with Create a Content.

What the integration does not do: its 3 triggers only react to audited timeline changes, and no scheduled trigger sweeps your whole database. For any other Cloze endpoint, Make an API Call reuses the same connection. Before you build, the Make review and the Make pricing page help you size the plan.

Many apps that Make supports also have an n8n node, so it is worth checking what exists for Cloze on that side too. The n8n vs Make comparison lays out the criteria.

Connect

How do you connect Cloze to Make?

  1. 01

    Request API access

    The Cloze doc asks for two things first: an active Cloze account and API access, which you request by emailing support. Without that access, Make has nothing to connect to, so start here.

  2. 02

    Create your API key in Cloze

    In Cloze, click More, then Settings. Under Accounts and Services, expand API Key, click Add, give the key a label you will recognize and copy the key shown on screen.

  3. 03

    Create the connection in Make

    Add any Cloze module to a scenario and click Create a connection. The Connection name field is optional. Paste your key or follow the on-screen instructions, and every Cloze module reuses this connection afterward.

First scenario

Build your first scenario with Cloze

GoalWhen a contact changes stage in Cloze, Make creates a to do so the next step is never forgotten.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.

  2. 02

    Add the Cloze trigger

    Search for Cloze and pick Watch Person Audit Changed. Click Create a webhook, then Create a connection, and paste the API key you copied from Cloze.

  3. 03

    Add the to do

    Click the + on the right of the trigger and choose Create a To Do. Map data from the person bundle, the item the trigger hands over, into the to do fields Make shows you.

  4. 04

    Test with Run once

    Click Run once, then move a test contact to another stage in Cloze. Read the bundles each module received and check that the to do shows up in Cloze.

  5. 05

    Switch it on

    Turn the scenario on. The trigger is instant, so Cloze calls Make through the webhook as soon as a stage changes. Each module run counts as one operation on your Make plan.

Triggers

Which Cloze events can start a scenario?

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

Cloze1Watch Company Audit Changed

Watch Company Audit Changed

Instant trigger

In Make“Triggers on the major timeline audited changes like Segment, Stage or Step has been changed.”

Starts your scenario when a company in Cloze goes through a major tracked change on its timeline, such as a new segment, stage or step. The company arrives as a bundle, ready for the next module to use.

How it fires
instant, the app calls Make through a webhook as soon as it happens.
When to use it
an account reaches a new stage and finance, support or a shared sheet needs to know without anyone forwarding the news.
Watch out
the doc names segment, stage and step changes; test with one of those in Run once before you count on any other edit waking the scenario.
Cloze2Watch Person Audit Changed

Watch Person Audit Changed

Instant trigger

In Make“Triggers on the major timeline audited changes like Segment, Stage or Step has been changed.”

Hands you a contact the instant their record in Cloze moves on its timeline, for example into another stage or segment. It is the natural start for follow-up scenarios, because the person is right there in the bundle.

How it fires
instant, the app calls Make through a webhook as soon as it happens.
When to use it
a prospect becomes a customer and you want a welcome email sent, a to do created or a row added to a tracking sheet.
Watch out
the doc has you click Create a webhook before Create a connection on this module; follow that order the first time you add it.
Cloze3Watch Project Audit Changed

Watch Project Audit Changed

Instant trigger

In Make“Triggers on the major timeline audited changes like Segment, Stage or Step has been changed.”

Tells Make that a Cloze project just changed segment, stage or step, and passes the project along. You follow deals and projects from Make without refreshing the pipeline view.

How it fires
instant, the app calls Make through a webhook as soon as it happens.
When to use it
a project reaches the signature stage and the team chat, the invoicing tool or a delivery checklist should react right away.
Watch out
pair it with Get a Project when the next modules need more details than the trigger bundle carries, and check in Run once what the bundle actually holds.
Modules

What can Make do in Cloze?

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

Cloze1

Create a Communication Record

Action

In Make“Creates a new communication record.”

Writes a communication record into Cloze, so an exchange that happened in another tool still shows up in the contact history your team reads.

When to use it
your phone system, chat tool or form app captures an interaction that Cloze never saw, and you want the relationship view to stay complete.
Cloze2

Create a Company

Action

In Make“Creates a new company.”

Adds a new company to Cloze from data another module collected, a signup form or a row in a sheet, without anyone typing it by hand.

When to use it
a new account signs up on your site.
Watch out
run Find Companies first, otherwise every repeat signup gives you a duplicate company.
Cloze3

Create a Content

Action

In Make“Creates new note, event or external to do.”

Files a note, an event or an external to do in Cloze in one module. It is the broadest writer of the set, handy when the record type depends on what happened upstream.

When to use it
a meeting from your calendar tool should appear as an event, or a form comment as a note.
Watch out
for a plain task, Create a To Do is the more direct choice.
Cloze4

Create a Person

Action

In Make“Creates a new person.”

Turns a lead captured elsewhere into a contact in Cloze, so the relationship starts with a proper record instead of an email thread.

When to use it
a webinar signup, a demo request or a business card scan lands in another app and should reach your CRM.
Watch out
check with Find People first, then route to Update a Person when the contact already exists.
Cloze5

Create a Project

Action

In Make“Creates a new project.”

Opens a new project in Cloze, the place where a deal or a piece of work gets tracked through its stages.

When to use it
a quote is accepted in your invoicing tool and the delivery work needs its own project from day one.
Watch out
search with Find Projects first when the same quote could be accepted twice, so one deal never ends up with two projects.
Cloze6

Create a To Do

Action

In Make“Creates a new to do.”

Puts a task on someone's list in Cloze, the simplest way to make sure a follow-up happens after an event elsewhere.

When to use it
right after a stage change caught by a Watch trigger, or when a form asks for a callback.
Watch out
a Run once test creates a real to do, so clean it up after testing.
Cloze7

Delete a Company

Action

In Make“Deletes a company specified by unique identifier.”

Removes a company from Cloze using its unique identifier, which you usually get from Find Companies or from the trigger bundle.

When to use it
a cleanup scenario where accounts flagged in another system should disappear from the CRM too.
Watch out
treat a deletion as final and test it on a dummy company before pointing the scenario at real data.
Cloze8

Delete a Person

Action

In Make“Deletes a person specified by unique identifier.”

Takes a contact out of Cloze once you give it the person's unique identifier. It works well at the end of a chain that first finds the right record.

When to use it
someone asks to be forgotten and the request arrives through a form or a support ticket.
Watch out
a search can match several people; delete only after you have narrowed it to one.
Cloze9

Delete a Project

Action

In Make“Deletes a project specified by ID.”

Deletes a Cloze project by its ID, which keeps the pipeline free of test runs and abandoned deals.

When to use it
a deal gets cancelled in another tool and the matching project should not linger in Cloze.
Watch out
get the ID from Find Projects or from Watch Project Audit Changed, never from a hand-typed value, so the wrong project is not removed.
Cloze10

Get a Company

Action

In Make“Retrieves a details of a company specified by unique identifier.”

Fetches the full details of one company when you already hold its unique identifier. The next modules then have everything Cloze knows about that account.

When to use it
a trigger or a search gives you the company, and a report, an invoice or a message needs its details.
Watch out
without the identifier it cannot work; use Find Companies to look the account up instead.
Cloze11

Get a Person

Action

In Make“Retrieves a details of a person specified by unique identifier.”

Pulls one contact's details from Cloze by unique identifier, the quickest way to enrich a scenario that only carries a reference to the person.

When to use it
after Watch Person Audit Changed, when the email you send needs details the trigger bundle does not include.
Watch out
it reads one person only; for a list, start from Find People.
Cloze12

Get a Project

Action

In Make“Retrieves a project details specified by unique identifier.”

Reads the details of a single Cloze project from its unique identifier, so later modules can reuse what Cloze knows about it in their own fields.

When to use it
a project update must reach a client portal or a shared spreadsheet with the full picture.
Watch out
check in Run once which details come back before mapping them further down the scenario.
Cloze13

Make an API Call

Action

In Make“Performs an arbitrary API call.”

Calls any endpoint of the Cloze API with the connection you already set up. It covers whatever the ready-made Cloze modules leave out, without a second connection.

When to use it
the Cloze API documentation shows an action you need and no ready module does it.
Watch out
you shape the request yourself, so start from that documentation and test with Run once.
Cloze14

Update a Company

Action

In Make“Updates a company specified by ID.”

Changes an existing company in Cloze, found by its ID, so the CRM follows what happens in your billing or support tool.

When to use it
an account upgrades its subscription elsewhere and the company record should reflect it.
Watch out
map the ID from Find Companies or a trigger rather than typing it, so the right account gets the change.
Cloze15

Update a Person

Action

In Make“Updates a person specified by ID.”

Edits a contact that already exists in Cloze. It finds the person by ID, so you refresh one record instead of creating a second copy.

When to use it
a returning lead fills in a form again and brings newer details than the ones Cloze holds.
Watch out
it needs the ID, so place Find People before it and handle the case where the search returns nobody.
Cloze16

Update a Project

Action

In Make“Updates a project specified by name.”

Updates a Cloze project, and unlike the company and person updates, the doc says it finds the project by name. Keeping project names unique is what makes it reliable.

When to use it
a delivery milestone reached in your project tool should move the matching Cloze project forward.
Watch out
two projects with the same name make the target ambiguous.
Cloze17

Find Companies

Search

In Make“Searches companies.”

Searches your Cloze companies and returns zero, one or several bundles, one per match. It is the check that stops duplicates before a create.

When to use it
before Create a Company, or to fetch the ID that Update a Company and Delete a Company need.
Watch out
several matches mean the next module runs once per company.
Cloze18

Find People

Search

In Make“Searches people that match a search parameters.”

Looks for contacts in Cloze that match your search and sends each match on as its own bundle. That makes it the gatekeeper of any lead import.

When to use it
a new lead comes in and you need to know whether to create or update the person.
Watch out
zero results is a normal outcome; plan what the scenario does then.
Cloze19

Find Projects

Search

In Make“Searches projects.”

Retrieves the Cloze projects that match your search, one bundle each, so you can act on a batch or pick the right ID.

When to use it
before Get a Project or Delete a Project, or to build a list of open deals for a report.
Watch out
each returned project triggers its own run of the following modules, which counts in operations.
Need help

Need help automating Cloze with Make?

A person reads every message.

FAQ

Cloze and Make: common questions

01Is the Cloze Make integration free?
Yes. Cloze is a standard app in Make, so its modules work from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and lift the cap on active scenarios. Your Cloze subscription is separate, and the Cloze doc points to its own pricing page for that.
02What do you need to connect Cloze to Make?
An active Cloze account, API access and an API key. The Cloze doc asks you to request access by emailing support before anything else. Once access is granted, open Settings in Cloze, expand API Key under Accounts and Services, click Add, label the key and copy it. In Make, click Create a connection on any Cloze module and paste the key. With a Watch trigger, Make asks you to click Create a webhook first.
03Do the Cloze triggers in Make react in real time?
Yes. All 3 Cloze triggers are instant: Cloze calls Make through a webhook as soon as a company, a person or a project goes through a major audited change, such as a new segment, stage or step. There is no 15-minute polling to wait for, which is how scheduled triggers work by default. The limit is scope: the doc only describes those audited timeline changes, so confirm with Run once that the event you care about really starts the scenario.
04What if a Cloze module is missing in Make?
Use Make an API Call. It is one of the 22 Cloze modules and lets a scenario reach any endpoint of the Cloze API with the connection you already have, so no second setup is needed. You build the request yourself from the Cloze API documentation, which takes more care than a ready module. The doc lists no other limit for this app, but it warns that its content is AI-generated and may contain mistakes, so verify important details with Cloze.
05Should you use Make or n8n for Cloze?
It depends on your criteria more than on Cloze. On Make, the integration offers 22 ready modules: 3 instant triggers, 16 actions and 3 searches, with Make an API Call for anything missing. The same app often has an n8n node too, so the first check is whether n8n covers the Cloze events and records your scenario needs. No ranking fits every team. Compare what each side offers against the scenario you actually want, then choose. The n8n vs Make comparison on this site sets out the general criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations