Resources · Zapier integration

Clust Zapier integrationAutomate Clust with Zapier.

The Clust Zapier integration gives you 12 triggers and 4 actions, and no search step. Every trigger runs on a timer, the free plan is enough to start, and this page covers what each event does, what it costs and where it breaks.

See the 16 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Clust Zapier integration does for you

Clust collects applications from your clients through a branded portal. The integration lets Zapier notice what happens to those applications (created, submitted, late, closed, a step approved, a document added) and act on it, or open and manage applications in Clust when something happens elsewhere. It all runs in a Zap, the automation you set up once on Zapier.

Three results that make the connection worth it. A reviewer on every submitted file: New Application Submitted feeds Assign a New Stakeholder to Role, so nothing waits for someone to notice. Applications opened from your sales tool: Create Application starts a file on the right template when a deal is won elsewhere, and can email the client their invite. Files that close themselves: Close Application shuts an application once the last piece of work is done somewhere else.

What Zapier won't do with Clust is just as useful to know. None of the 12 triggers is instant, so Zapier has to ask Clust for news and there's always a wait. There's no search step, so a Zap can't look up an application by name before acting on it. And the 4 actions cover creating, assigning, updating a form field and closing: there's nothing to delete an application.

Comparing platforms? The Clust Make integration covers the same app on Make, and Make vs Zapier sets out the differences.

Vocabulary

The Zapier vocabulary, quickly

Seven words you'll see in the editor. They're explained once here, and the rest of the page uses them without a reminder.

Zap
An automation on Zapier: one starting event, then one or more steps that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier keeps waiting for that event.
Action
What the Zap does after it starts: the step that creates, sends or updates something in an app on your behalf.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a number of these.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment the event happens.
Filter
A step that only lets the Zap continue when what arrived meets your condition, and stops it there otherwise.
Multi-step Zap
Anything beyond one trigger and one action. A second action or a filter makes a Zap multi-step, and that needs a paid plan.
Cost

What a Clust Zap really costs

Clust isn't a premium app, so it runs on Zapier's free plan. The bill is counted in tasks.

  • Trigger checksNever billed
  • Successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo

Checking Clust for new applications costs nothing, however often Zapier looks. Each successful action costs one task, and a failed one isn't counted. A Zap that assigns a stakeholder and then updates a form field costs two tasks per application. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: a trigger and one action. A filter or a second action needs a paid plan.

Connect

Connect Clust to Zapier in three steps

  1. 01

    Go to your apps

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your Clust account linked once, then reused by every Zap step that works with Clust.

  2. 02

    Find Clust

    Search for Clust in the dialog, select it and click Add connection. You need a Clust account already: the connection links one, it doesn't create it.

  3. 03

    Log in and allow access

    Sign in to Clust in the tab that opens and grant Zapier access. If the Zap will handle applications you don't own, make sure that login can read them, and write to them for the actions.

First Zap

Your first Zap: assign a reviewer and log it on every submitted application

GoalWhen a client submits their application, a reviewer is attached to it and a form field records the handover. Two actions means a paid plan; on the free plan, keep the assignment only.

  1. 01

    Build: choose the trigger

    Start a Zap in Build. Pick Clust as the app and New Application Submitted as the event, then select the Clust connection you just added.

  2. 02

    Test with a real application

    Click Test. Zapier fetches the three most recent submitted applications from your account; pick one so the next steps are mapped on real data.

  3. 03

    Assign the reviewer

    Add a Clust step with Assign a New Stakeholder to Role. Map the application from the trigger, then fill the role and the reviewer's first name, last name and email.

  4. 04

    Record the handover

    Add Update Form Field. Map the same application, pick the form field to fill and type the new value. The Generate files setting is required, so choose it explicitly.

  5. 05

    Test, then publish

    Run Test on both actions and check the application in Clust. Then click Publish to switch the Zap on. For guided practice, see the Zapier training.

Triggers

Clust triggers on Zapier

12 events start a Zap when something happens in Clust. Zapier checks for them at the interval your plan allows.

1

New Application Created

Polling trigger

In Zapier“Triggers when a new application is created.”

Fires as soon as an application exists in Clust. It's the earliest point at which you can react to a new file.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a lender's onboarding team wants a welcome task opened on its side for every new loan file, even before documents arrive.
Watch out
a Zap that uses Create Application as its action will trigger itself again here.
2

New Application Closed

Polling trigger

In Zapier“Triggers when a new application is closed.”

Reports applications that have been closed in Clust. Use it as the finish line: the file is done and whatever comes after can start.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an accounting firm wants to hand a finished client file to the person who'll do the first engagement.
Watch out
pair it with the Close Application action in the same Zap and it can set itself off.
3

New Application Late

Polling trigger

In Zapier“Triggers when a new application is late”

Flags an application that has gone late in Clust. This is your overdue alarm, the one that keeps files from sitting forgotten.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a property manager wants a team lead added to any rental application that misses its deadline.
Watch out
files that were already late before you published the Zap won't come through.
4

New Application Pending Submission

Polling trigger

In Zapier“Triggers when a new application pending submission is detected (all mandatory documents provided but application not submitted)”

Catches the frustrating in-between: every mandatory document is in, but the client still hasn't hit submit. Zapier picks that state up on its next check.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an insurance broker wants a nudge sent to clients who did all the work and stopped one click short.
Watch out
applications already in that state before the Zap went live won't come through.
5

New Application Progress Stage Changed

Polling trigger

In Zapier“Triggers when the progress stage of an application changes”

Goes off when an application moves to another progress stage. It's the broadest way to follow a file through your process without picking one particular step.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an operations lead at a staffing agency wants a record of each stage move for candidate compliance files.
Watch out
with many applications moving at once, a large batch can arrive on a single check.
6

New Application Step Approved

Polling trigger

In Zapier“Trigger when a specific step in an application is approved”

Reacts when your team approves a specific step inside an application. Narrower than a stage change: you choose which template it listens to.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a coworking space unlocks a member's access once the identity check step is approved.
Watch out
the Process setting is required, so the trigger only covers steps from the template you pick.
7

New Application Step Submitted

Polling trigger

In Zapier“Trigger when a specific step in an application is submitted by a client”

Fires when a client submits one specific step of their application, ahead of the full file. Handy when a step needs checking the moment it lands.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a compliance officer wants to start reviewing the ownership details step before the rest is done.
Watch out
you must choose a Process, and steps from other templates are ignored.
8

Task Step Completed in Application

Polling trigger

In Zapier“Triggers when a task step is completed within a Clustdoc application”

The most targeted of the set: it fires when one task step is completed inside an application. You narrow it down to a template, its items and the task itself.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a solar installer wants to book the site visit once the roof photos task is marked done.
Watch out
Process, Process Items and Task are all required, so build the template in Clust first.
9

New Application Submitted

Polling trigger

In Zapier“Triggers when a new application is submitted”

Triggers once the client submits the whole application. For most teams this is the moment their own work begins.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a grants team wants a reviewer assigned to each funding request as soon as it's sent in.
Watch out
applications submitted before the Zap went live stay without a reviewer; assign those by hand.
10

New Application Task Completed

Polling trigger

In Zapier“Triggers when a task is marked as completed in an application”

Watches for a task being marked complete in an application. Unlike the task-step trigger above, you only point it at the task you care about.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a recruiter moves a candidate forward once the background check task is ticked.
Watch out
the Task setting is required, so one Zap follows one task.
11

New Application Updated by Client

Polling trigger

In Zapier“Triggers when an application is updated by client”

Fires when the client changes something in their application. It follows the client's edits, which is the signal you want when you're waiting on a correction.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a mortgage adviser wants to know when a client corrects their file after being asked to.
Watch out
corrections made before you published the Zap are never picked up.
12

New Document Added

Polling trigger

In Zapier“Triggers when a new document is added by client (File uploaded, form filled in …)”

Picks up each document a client adds, whether a file upload or a filled-in form.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a tax preparer wants a heads-up every time a client drops a new statement into the portal.
Watch out
a client sending lots of files at once can create a burst of runs, each with its own action cost.
Actions

Clust actions on Zapier

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

1

Assign a New Stakeholder to Role

Action

In Zapier“Assigns a stakeholder to a specific role within an existing application”

Adds a person to a role on an existing application. It needs the application, the role, and the person's first name, last name and email; notifying them is optional.

When to use it
every submitted file should land with a named reviewer.
2

Close Application

Action

In Zapier“Closes an existing application”

Closes an application that's already in Clust. Only the application is required, which makes this the simplest of the four.

When to use it
the final step of a file happens in another tool, and Clust should reflect that it's finished.
Watch out
don't run it in a Zap triggered by New Application Closed.
3

Create Application

Action

In Zapier“Creates an Application”

Opens a new application in Clust on the template you name, for a recipient whose first name, last name and email you supply. You must also say whether the recipient gets an email about it.

When to use it
a deal marked won in your CRM should open the onboarding file straight away.
4

Update Form Field

Action

In Zapier“Updates the value of a specific field in a form within an existing Clustdoc application”

Writes a new value into one field of a form inside an existing application. You pick the application, the field and the value, and set the required Generate files option.

When to use it
an internal status or reference number should be filled in by the Zap rather than by hand.
When it breaks

When a Clust Zap breaks

Zapier links no help article to Clust and no app-specific limit is documented. The problems you'll meet come from how Zapier works in general, and they show quickly with this many application triggers.

Four cases explain most surprises. Rule them out before you suspect the connection, and keep Zapier troubleshooting nearby for anything else.

  • Older applications never show up

    A Zap only reacts to what happens after you publish it. Applications created, submitted or closed earlier are ignored; catching up on them is a separate job.

  • The Zap triggers itself

    Create Application under New Application Created, or Close Application under New Application Closed: each run creates the event that starts the next and burns your tasks.

  • A bulk import gets held

    If a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of running every item.

  • The same item won't fire twice

    Zapier remembers what it has already seen on a polling trigger, so one application or document never starts the Zap a second time.
Need help

Need help automating Clust with Zapier?

A person reads every message.

FAQ

Clust Zapier integration: common questions

01Is the Clust Zapier integration free?
Yes, it works on Zapier's free plan, since Clust isn't a premium app. That plan includes 100 tasks a month and unlimited Zaps. The limit is size: each free Zap stops at two steps, one trigger and one action. Adding a second action or a filter makes it a multi-step Zap, which needs a paid plan. You also need your own Clust account, which isn't part of Zapier. Start small, then upgrade once a second step is worth it.
02How many tasks does a Clust Zap use?
One task for each action that succeeds, and nothing for the rest. The trigger is free, however many times Zapier checks Clust for new applications. A Zap with one Assign a New Stakeholder to Role action costs one task per application; add Update Form Field and it costs two. A failed action, for example one missing the reviewer's email, isn't counted. A few other apps charge more than one task per action, so check before you add them.
03Do Clust triggers work in real time?
No. All 12 Clust triggers are polling triggers: Zapier asks Clust for anything new at a fixed interval. That interval depends on your plan, 15 minutes on Free, 2 minutes on Professional, 1 minute on Team and Enterprise. Paid plans let you change how often it checks and run a check by hand from the editor. None of them is instant, and Zapier can't switch that: the app decides. Expect a delay between the client's move and your Zap.
04What do you need to connect Clust to Zapier?
A working Clust account and enough rights on the applications the Zap will touch. You connect once, from the Apps page of Zapier with Add connection, then sign in to Clust and grant access. For applications you don't own, the login must be able to read them for triggers and write to them for actions. Templates matter too: several triggers and Create Application refer to a Process that must already exist.
05Why doesn't a Clust step trigger fire for every template?
Because you told it which one to watch. New Application Step Approved and New Application Step Submitted require a Process, and Task Step Completed in Application also asks for Process Items and a Task. Steps from other templates are ignored by that Zap. To cover several templates, build one Zap per template, or use a broader trigger such as New Application Progress Stage Changed or New Application Submitted, which don't ask for a template.
06What if the Clust action you're after doesn't exist?
Then Zapier can't do it with Clust right now. This page lists everything the editor offers: 12 triggers, 4 actions, no search and no way to delete an application. Zapier showed this on 2026-10-01, version ClustCLIAPI@2.1.0. If what you need isn't there, rebuild the flow around what exists, for instance updating a form field instead of changing the application itself, or look at another platform. Checking this list first saves building a Zap around a step that isn't offered.
07Zapier, Make or n8n for Clust?
Choose on criteria rather than reputation. First, check the trigger and action you need exist for Clust on that platform: on Zapier, that's the 12 triggers and 4 actions on this page. Second, look at billing: Zapier counts one task per successful action, so a busy portal adds up. Third, think about who will maintain the automation and which editor they're at ease with. Those three questions, applied to your own process, decide better than a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations