Resources · Make integration

Clust Make integrationAutomate Clust with Make.

Could your client applications in Clust move forward without anyone copying data by hand? The Clust Make integration gives you 21 modules: 12 triggers, 8 actions and 1 search. This guide is for ops teams that collect client files, and it walks you from the API key to a live scenario.

Try the Clust integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Clust Make integration do for you?

The Clust Make integration links your Clustdoc account to Make, a no-code tool where you build a scenario (the automation itself, a chain of bricks called modules). Make checks Clust for applications that were submitted, approved or closed, and Make can create, update or close applications for you in return.

Put the right reviewer on every new file. Start from Watch Submitted Applications, then let Add New Stakeholder On application bring a colleague onto the application. Nobody has to remember who handles which client.

Feed your other tools when a client does their part. Watch Documents Added By Clients and Watch Applications Updated By Clients notice client activity, so a later module in the same scenario can post a message or log the change somewhere else.

Open applications from outside Clust. A form, a CRM or a spreadsheet row can end in Create an Application, and Update Form Field In Application fills a field on the file you already have.

Limits: the Clust doc on the Make side is short and flagged as AI-generated, so check field behavior in your own account with a test before you rely on it. What the 21 modules do not cover can go through Make an API Call. If you are also weighing another tool, read n8n vs Make; to learn the editor properly, Make training starts from scratch, and Make pricing explains what each plan allows.

Connect

How do you connect Clust to Make?

  1. 01

    Generate an API token in Clust

    In Clust, open your team settings, then the Developer menu on the left and its API entry. Give the token a name, tick the abilities it needs, click Validate and copy the token shown on screen.

  2. 02

    Add a Clust module in Make

    In your Make scenario, add any Clust module and click Create a connection. A connection is your Clust account linked to Make once, then reused by every Clust module you add later.

  3. 03

    Paste the token and save

    The Connection name field is optional, but a clear name helps when you run several Clust teams. Paste the API token you copied, confirm, and Make can now read your applications.

First scenario

Your first scenario: a reviewer on every submitted application

GoalWhen a client submits an application in Clust, Make adds a colleague to it as a stakeholder.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Search for Clust, then pick Watch Submitted Applications: it becomes the first module, the one that opens every run.

  2. 02

    Link your account

    Click Create a connection and paste the API token from your Clust team settings. Once saved, Make can list what it is able to read in your account.

  3. 03

    Add the stakeholder action

    Click the + on the right of the trigger and choose Add New Stakeholder On application. Map the application from the trigger so each bundle (one submitted application) gets its own stakeholder.

  4. 04

    Test with Run once

    Submit a test application in Clust, then click Run once. Open the bubbles above each module to read the bundles they received and check the stakeholder landed on the right file.

  5. 05

    Schedule and switch on

    On the first module, set the schedule: a new scenario checks every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Switch the scenario on.

Triggers

Clust triggers: what starts a scenario

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

Clust1Watch Application Tasks Completed

Watch Application Tasks Completed

triggerIn the docs only

You get a new run each time Make spots a task on an application marked done, so the next step can start without someone checking the file. Nothing in the doc details what counts as a task, so read the first bundle before building on it.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when finishing a single task should notify the account manager or open work in another tool.
Watch out
tasks and steps are separate triggers here; pick Watch Step Task Completed if you care about one step only.
Clust2Watch Applications

Watch Applications

triggerIn the docs only

This is the broad one: it hands your scenario the applications Make finds in Clust, without filtering on a status. It suits a scenario that copies every file into a tracker, where later modules sort things out.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when you want one place, like a spreadsheet, that lists all applications whatever their state.
Watch out
each application is one bundle and costs operations downstream; if only one status matters, a narrower trigger below saves them.
Clust3Watch Applications Updated By Clients

Watch Applications Updated By Clients

triggerIn the docs only

Know the moment a client comes back and edits their file, instead of opening Clust to find out. The trigger is built around client changes, which makes it a natural start for a follow-up alert to the person handling the account.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when a client fixes a missing answer and your team should look again.
Watch out
the doc does not list what comes back; if the bundle lacks a detail, add Get an Application after it.
Clust4Watch Approved Applications

Watch Approved Applications

triggerIn the docs only

Once an application reaches approval in Clust, this trigger passes it to Make, which makes it the cleanest starting point for whatever happens after a yes: a welcome email, a CRM update, an invoice drafted in another app.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
for onboarding work that must only begin after the client file is accepted.
Watch out
approval of a single step is a different trigger, Watch Step Approved; this one looks at the application.
Clust5Watch Closed Applications

Watch Closed Applications

triggerIn the docs only

Closing a file in Clust becomes the signal to tidy up elsewhere. Make receives each closed application as a bundle, and the modules you add after it can archive a record, update a deal or tell the team the case is done.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when a closed application should also end its life in your CRM or reporting sheet.
Watch out
if a scenario of yours closes files with Close application, this trigger picks those up too, so avoid sending the same alert twice.
Clust6Watch Documents Added By Clients

Watch Documents Added By Clients

triggerIn the docs only

Every document a client uploads to an application can start your scenario, which spares your team from refreshing the file to see if the payslip or contract finally arrived. Going by the name, expect one bundle per upload.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when an upload should ping a reviewer or be copied to a storage app.
Watch out
files on the Free plan are capped at 5 MB in Make, so large scans may need a paid plan before you copy them.
Clust7Watch Late Applications

Watch Late Applications

triggerIn the docs only

Catch applications that have fallen behind before the client does. As its name says, this trigger follows files Clust considers late; the doc does not define the rule, so it depends on how your Clust workspace sets due dates.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
for a reminder to the client or an escalation to a manager when a file stalls.
Watch out
run a test on a file you know is late, and confirm it comes through, before you trust the reminders.
Clust8Watch Pending Submission Applications

Watch Pending Submission Applications

triggerIn the docs only

Here the focus is on files a client has started but not yet sent. Pulling them into Make lets you nudge people who stopped halfway, which is often where onboarding slows down.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when a sales rep wants to call the prospects whose file is still open on their side.
Watch out
pair it with a filter or a record of who was already contacted, otherwise the same client can get several nudges.
Clust9Watch Progress Applications Stage

Watch Progress Applications Stage

triggerIn the docs only

Follow an application as it moves from one stage to the next, and react to the move itself rather than to the final result. It gives you a way to mirror the Clust pipeline in a board or a CRM.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when each stage change should update a deal stage or a project card elsewhere.
Watch out
the doc says nothing about which stage values come back, so run it once and map from the bundle you see.
Clust10Watch Step Task Completed

Watch Step Task Completed

triggerIn the docs only

Narrower than the application-wide task trigger, this one reacts to a task finished inside a step. That helps when only a specific part of the process, such as identity checks, should wake your scenario.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when a compliance officer should hear about one type of task and ignore the rest.
Watch out
use a filter after the trigger to keep only the step you care about, since the doc gives no setting for that.
Clust11Watch Submitted Applications

Watch Submitted Applications

triggerIn the docs only

The moment a client presses submit is often when your team needs to start. This trigger brings each submitted application into Make, ready for a review assignment, a notification or a copy in your CRM.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
as the start of a first scenario, because a submission is easy to reproduce for a test.
Watch out
with a schedule of 15 minutes, a submission can wait up to that long before Make sees it; paid plans go down to 1 minute.
Clust12Watch Step Approved

Watch Step Approved

triggerIn the docs only

Some processes need action as soon as one step is signed off, not the whole file. This trigger fires on step approval, so a partial yes can already unlock the next piece of work.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
when approving the KYC step should let finance prepare the contract while the rest stays under review.
Watch out
an application with several approved steps produces several bundles, and each one counts as operations further down the scenario.
Modules

Clust actions and search in Make

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

Clust1

Add New Stakeholder On application

ActionIn the docs only

Brings another person onto an existing application, so the right colleague or partner can follow the file without being added by hand in Clust.

When to use it
right after a submission trigger, to assign a reviewer per client type.
Watch out
map the application from the trigger, or the stakeholder may land on the wrong file.
Clust2

Close application

ActionIn the docs only

Marks an application as closed from your scenario, which lets another system decide when a file is finished instead of someone clicking in Clust.

When to use it
when a deal marked lost in your CRM should also close the matching client file.
Watch out
closing will also fire Watch Closed Applications if you run that trigger elsewhere.
Clust3

Create an Application

ActionIn the docs only

Opens a new application in Clust from data that lives somewhere else, so a client file exists before anyone logs in to create it.

When to use it
when a signed quote or a web form should start the onboarding file on its own.
Watch out
a scenario that runs twice on the same source creates two files; check with List Applications first if duplicates matter.
Clust4

Delete an Application

ActionIn the docs only

Removes an application from Clust entirely. It is the cleanup tool for test files or entries created by mistake in a scenario, not a way to end a normal file.

When to use it
to wipe the test applications you created while building a scenario.
Watch out
a delete cannot be undone from Make; for a real file that is finished, prefer Close application.
Clust5

Get an Application

ActionIn the docs only

Reads one application you already know, and returns its full content to the next modules. If a trigger's bundle lacks a detail you need, this module fetches it.

When to use it
after a client update trigger, to fetch the whole file before writing it to a CRM.
Watch out
each call costs one operation, so skip it when the trigger already gives you what you need.
Clust6

List Applications

SearchIn the docs only

This search returns zero, one or several applications, each as its own bundle, so you can check what exists before acting on it.

When to use it
before Create an Application, to find out whether the client already has a file.
Watch out
many results mean many bundles, and each one multiplies the operations that follow.
Clust7

Make an API Call

ActionIn the docs only

When none of the other Clust modules does what you need, this one reaches any endpoint of the Clust API with the same connection you already set up.

When to use it
for an operation the ready-made modules skip, once you have found the endpoint in the Clust API documentation.
Watch out
the token abilities you chose in Clust still apply; a missing ability blocks the call.
Clust8

Update Form Field In Application

ActionIn the docs only

Writes a value into one form field of an application, which saves a client from typing information your team already holds in another tool.

When to use it
to pre-fill a company name or reference number pulled from your CRM.
Watch out
Make shows the fields it can read once the connection exists; pick from that list rather than typing a name.
Clust9

Update an Application

ActionIn the docs only

Changes an application as a whole, rather than a single form field, to keep the Clust file in step with what happened elsewhere.

When to use it
when a change in your CRM should be reflected on the matching client file.
Watch out
for one form answer, Update Form Field In Application is the more precise choice.
Need help

Need help automating Clust with Make?

A person reads every message.

FAQ

Clust and Make: frequent questions

01Is the Clust Make integration free?
Yes, on the Make side. Clust is a standard app, available from the Free plan. That plan allows 2 active scenarios, a gap of at least 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the gap to 1 minute and lift the cap on active scenarios. On the Clust side you still need an active Clustdoc subscription; the Clust pricing page covers that.
02What do you need to connect Clust to Make?
An active Clustdoc account and an API token. You generate the token in Clust from your team settings, under Developer then API: name it, select its abilities, click Validate and copy it. In Make, add a Clust module, click Create a connection, give it a name if you like and paste the token. The connection is then reused by every Clust module in your scenarios, so this setup happens once per account.
03Do Clust triggers in Make fire instantly?
No. All 12 Clust triggers are scheduled: Make checks Clust on the scenario's schedule instead of being called by Clust when something happens. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan. Paid plans can check as often as every 1 minute. For most onboarding flows, such as assigning a reviewer to a submitted file, that delay is acceptable; test with Run once to see the bundles.
04What if a Clust module you need is missing in Make?
Use Make an API Call. It is part of the 21 Clust modules and calls any endpoint of the Clust API with the same connection, so you can cover what the other Clust modules do not. Check that your API token has the abilities the endpoint needs. Keep in mind that the Clust page in the Make doc is marked as AI-generated and may contain mistakes, so verify details in the Clust documentation or with Clust directly.
05Should you use Make or n8n for Clust?
It depends on what you already run. In Make, Clust comes with 21 ready modules, including 12 triggers around applications, steps and client uploads, plus a generic API call for the rest. n8n often has a node for the same app, but check what it covers for Clust before choosing. Pick the tool your team already uses for its other automations, and compare the modules you actually need rather than the brand.
Same platform

Other docs you might need on this stack.

Browse all integrations