---
title: Clust
slug: clust
description: How to integrate Clust with Make.com
image: https://make-cxp-documentation.ams3.digitaloceanspaces.com/apps-center-icons/PREVIEW_clust.png
createdAt: 2025-02-03T13:29:04.396Z
---

| :inlineImage[]{src="https://make-cxp-documentation.ams3.digitaloceanspaces.com/apps-center-icons/clust.png" alt="Clust logo" caption size="50" width="512" height="512"} | Clustdoc is a client onboarding and document collection platform. Integrating Clustdoc with Make.com lets users automate client onboarding steps, trigger workflows based on document submissions, and manage client files across multiple business tools. |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

:::hint{type="warning"}
This is AI-generated content based on official Clust documentation. The content may contain mistakes. Please verify important information. If you have questions on vendor documentation, contact [Clust](https://support.clustdoc.com/en/) directly.
:::

# Requirements

To use the Clust app in Make, you must have an active Clustdoc account and an API Key, [create your account on Clust](https://clustdoc.com). For subscription, refer to the [Clust pricing page](https://clustdoc.com).

# Connect Clust and Make&#x20;

To get started, you must first create a connection between Clust and Make, allowing the two services to communicate.&#x20;

::::WorkflowBlock
:::WorkflowBlockItem
**Obtain your API Key in your Clust account**
:::

:::WorkflowBlockItem
**Create the connection in Make.**
:::
::::

## Obtain your API Key in your Clust account

Before you create the connection in Make, you should first obtain your **API Key** in your Clust account.

To obtain your **API Key&#x20;**:

::::WorkflowBlock
:::WorkflowBlockItem
Navigate to you&#x72;**&#x20;team settings page** after logging in.
:::

:::WorkflowBlockItem
Click th&#x65;**&#x20;Developer menu** on the left side.

![](https://make-cxp-documentation.ams3.cdn.digitaloceanspaces.com/apps-center-screenshots/clust_API_Key)
:::

:::WorkflowBlockItem
Click th&#x65;**&#x20;API menu** within th&#x65;**&#x20;Developer section**.
:::

:::WorkflowBlockItem
Enter a token name in the provided field.
:::

:::WorkflowBlockItem
Select the abilities you want to assign to you&#x72;**&#x20;API token**.
:::

:::WorkflowBlockItem
Click th&#x65;**&#x20;Validate button** to generate you&#x72;**&#x20;API token**.
:::

:::WorkflowBlockItem
Copy th&#x65;**&#x20;API token** displayed on screen.
:::
::::

You will use this value while creating a connection in Make.&#x20;

Because the UI might have changed, the steps you see on your screen might be different, [check the vendor documentation for updates.](https://clustdoc.docs.apiary.io/)

## Create the connection in Make&#x20;

:::::WorkflowBlock
::::WorkflowBlockItem
[[Log in in your Make](https://www.make.com/en/register) account](https://www.make.com/en/register), add the Clust module to your scenario, and click **Create a connection.&#x20;**

:::hint{type="info"}
If you add a module with an instant tag, click **Create a webhook**, then **Create a connection.**
:::
::::

:::WorkflowBlockItem
*Optional:&#x20;*&#x49;n the **Connection name** field, enter a name for the connection.
:::

:::WorkflowBlockItem
Enter the **authentication credentials** you copied from your Clust account or follow the on-screen instructions to create the connection.&#x20;
:::
:::::

For detailed information on connecting an application, see **[Connect an application](docId\:SO88FM6pkT0G-adKDDfzZ)** page.

# Clust modules

After connecting to the Clust app, you can choose from a list of available modules to build your scenarios.&#x20;

:::ExpandableHeading
### Add New Stakeholder On application

Assign an application to a different stakeholder for management or oversight.
:::

:::ExpandableHeading
### Close application

Terminate a running application.
:::

:::ExpandableHeading
### Create an Application

Creates a new application record in your account.
:::

:::ExpandableHeading
### Delete an Application

Removes a specific application from your account using its unique ID.
:::

:::ExpandableHeading
### Get an Application

Retrieves detailed information about a specific application using its unique ID.
:::

:::ExpandableHeading
### List Applications

Retrieves a complete list of all available applications in your account.
:::

:::ExpandableHeading
### Make an API Call

Executes a custom API request to the service using your authorized account.
:::

:::ExpandableHeading
### Update Form Field In Application

Updates the values of specific fields within a form in the application.
:::

:::ExpandableHeading
### Update an Application

Updates the details of a specific application using its unique ID.
:::

:::ExpandableHeading
### Watch Application Tasks Completed&#x20;

Triggers when a task within an application is marked as completed.
:::

:::ExpandableHeading
### Watch Applications

Triggers when a new application record is added to your account.
:::

:::ExpandableHeading
### Watch Applications Updated By Clients

Triggers when a client updates an existing application.
:::

:::ExpandableHeading
### Watch Approved Applications

Triggers when an application receives approval and its status changes to approved.
:::

:::ExpandableHeading
### Watch Closed Applications

Triggers when an application is closed and its status changes to "closed."
:::

:::ExpandableHeading
### Watch Documents Added By Clients

Triggers when a client uploads a new document to an application.
:::

:::ExpandableHeading
### Watch Late Applications

Triggers when a newly submitted application is marked as late.
:::

:::ExpandableHeading
### Watch Pending Submission Applications

Triggers when a new application is identified as ready for submission, meaning all required documents have been provided but the application has not yet been officially submitted.
:::

:::ExpandableHeading
### Watch Progress Applications Stage

Triggers when an application's stage is updated or moved to a different phase.
:::

:::ExpandableHeading
### Watch Step Task Completed

Triggers when a specific step within a task is marked as completed.
:::

:::ExpandableHeading
### Watch Submitted Applications

Triggers when a user submits a new application form.
:::

:::ExpandableHeading
### Watch Step Approved

Triggers when there is a change in the status of a specific dossier item.
:::

# Templates

You can look for more templates in [Make's template gallery](https://www.make.com/en/templates), where you'll find thousands of pre-created scenarios.

# Clust resources&#x20;

You can have access to more resources related to this app on the following links

- [Clust topics on Make community](https://community.make.com/search?q=Clust)
- [Clust website](https://clustdoc.com)
- [Clust API documentation](https://clustdoc.docs.apiary.io/#)
- [Clust page on make](https://www.make.com/en/integrations/clust)

***

:::CtaButton{label="Get started for free" externalHref="https://www.make.com/en/register" openInNewTab="true"}

:::

