Resources · Make integration

Dext Make integrationAutomate Dext with Make.

Need your Dext client data somewhere other than Dext? The Dext Make integration gives you 4 modules: 3 actions and 1 search, all built around clients and their activity. This guide connects your account, then walks you through a first scenario you can test yourself.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Dext Make integration do for you?

The Dext Make integration lets a Make scenario, the automation you build in Make, read your Dext clients and their activity statistics with your own API key. Each brick of that scenario is called a module, and Dext brings four of them: three that fetch or call something, one that searches.

A client roster that stays in sync. Start with List Clients to pull every client from your account, then pass each one to a spreadsheet or a CRM module from another app. Each client travels as a bundle, one item handed from module to module.

An activity check per client. Chain Get a Client Activity after the list, and each client comes back with its activity statistics, ready to feed a report or an alert for the accountant who follows that file.

A single client on demand. When another app already gives you a client reference, Get a Client fetches that one record without listing the whole account. For anything the three named modules skip, Make an API Call reaches other endpoints of the Dext API through the same connection.

What Make does not offer here: Dext has no trigger, so nothing starts a scenario from inside Dext. You start it on a schedule or from another app. The documentation page itself warns that it is AI-generated from Dext's docs and may contain mistakes, so check anything critical with Dext. If you are weighing tools, read n8n vs Make; for plan details, see Make pricing; and to learn the editor properly, Make training covers the basics.

Connect

How do you connect Dext to Make?

  1. 01

    Copy your Dext API token

    In Dext, open Settings, click API and copy the token shown on screen. You need an active Dext account for this; the key is what lets Make read your data on your behalf.

  2. 02

    Add a Dext module and open the connection

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you manage several accounts. Paste the token you copied, or follow the on-screen instructions, then save.

First scenario

Build your first scenario with Dext

GoalWhen the scenario runs on its schedule, Make lists your Dext clients and fetches the activity statistics of each one.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to place the first module. Since Dext has no trigger, a Dext search will open the flow.

  2. 02

    Add List Clients and connect

    Search for Dext, pick List Clients and click Create a connection with your API token. Every client it finds becomes its own bundle for the next step.

  3. 03

    Chain Get a Client Activity

    Click the + to the right of List Clients, choose Get a Client Activity, and map the client from the previous module so each client gets its own lookup.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open the bubble above each module to read the bundles it received and confirm the activity data looks right.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module to set how often it runs (every 15 minutes by default), then switch the scenario on. Each module run on one bundle counts as an operation on your plan.

Modules

What each Dext module does

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

Dext1

Get a Client

Action

In MakeRetrieves an existing client.

Fetches one existing Dext client, so the rest of your scenario can reuse its details without searching the whole account. You get a single record back, not a list.

When to use it
another app already hands you the client reference, say a form or a CRM record, and you only need that one file.
Watch out
it needs the client identified up front; if you do not know which client yet, start with List Clients instead.
Dext2

Get a Client Activity

Action

In MakeRetrieves an activity statistics for a client.

Returns the activity statistics of one client, which turns a plain client list into something you can actually watch. Pair it with a sheet or a messaging module to share what moved.

When to use it
right after List Clients, to review how busy each client file is before you sit down with the team to discuss it.
Watch out
it runs once per client bundle, so a long client list means as many operations on your plan.
Dext3

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Sends a request of your choice to the Dext API with the connection you already set up. This is your way out when none of the three named modules covers the endpoint you need.

When to use it
you found an endpoint in the Dext API that Make has no dedicated module for, and you want it inside the same scenario.
Watch out
you build the request yourself, so keep the Dext API reference open and check the response with Run once first.
Dext4

List Clients

Search

In MakeRetrieves a list of clients from account.

Pulls the clients of your Dext account as separate bundles, which gives any scenario a clean starting point. Since Dext has no trigger, this search is often the module that opens the flow.

When to use it
to copy your client roster into a spreadsheet, or to loop over every client with another module.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per client it returns.
Need help

Need help automating Dext with Make?

A person reads every message.

FAQ

Dext and Make: common questions

01Is the Dext Make integration free?
Yes, on the Make side. Dext is a standard app, so it works on the Free plan, which gives you 2 active scenarios, a scheduled interval of 15 minutes at the shortest, 5 minutes of run time per execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations, one module run on one bundle. You still need your own active Dext account, which Dext bills separately.
02What do you need to connect Dext to Make?
Two things: an active Dext account and its API key. In Dext, go to Settings, then API, and copy the token shown on screen. In Make, add any Dext module, click Create a connection, give it a name if you like, and paste the token. That connection is then shared by every Dext module in your scenarios, so you only do this once per account. If the connection fails, check that the token was copied in full.
03Does the Dext Make integration have a trigger?
No. Dext has no trigger module in Make, scheduled or instant, so Dext itself cannot start a scenario. You have two ways around it. The simplest is to open the scenario with List Clients and set a schedule on that first module, every 15 minutes by default, or longer if you prefer. The other is to start from a trigger of another app, such as a new form entry, and call Get a Client from there. Either way, the scenario runs when Make decides, not when Dext changes.
04What if the Dext module you need is missing in Make?
Use Make an API Call. It is part of the Dext app in Make and sends any request to the Dext API with the connection you already have, so you are not limited to the three named modules. You write the request yourself, so keep the Dext API reference at hand and test with Run once before switching the scenario on. Also note that the Make documentation for Dext is flagged as AI-generated and may contain mistakes; confirm anything critical directly with Dext.
05Should you use Make or n8n for Dext?
It depends on the tool your team already works in. In Make, Dext offers 4 modules: 3 actions and 1 search, plus Make an API Call for the rest. Many apps also have an n8n node, so check whether one exists for Dext before deciding. Compare the actual operations each tool offers for your use case rather than general claims, and pick the one where you can build and maintain the scenario comfortably. Neither choice changes how Dext itself works.