Resources · Make integration

Enreach DialoX Make integrationAutomate Enreach DialoX with Make.

What happens after your DialoX bot closes a conversation? The Enreach DialoX Make integration gives you 9 modules: 3 triggers and 6 actions. This guide shows what each one is for, how to link your account and how to build a first scenario without code.

Try the Enreach DialoX integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Enreach DialoX Make integration do for you?

The Enreach DialoX Make integration links your DialoX account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: a trigger that notices something in DialoX, or an action that reads or changes data there. Make then moves the results to your other tools.

Follow up on every closed conversation. Watch Closed Conversations starts the scenario when DialoX shows a conversation as closed. Add Get a User to pull the person behind it, then pass the details to your CRM or your support inbox.

React to how conversations get labeled. Watch Conversation Tags picks up tags on conversations, so a tag can become the signal for another team. Send a Conversation Event can then push an event back into a DialoX conversation.

Keep notes and user data in step. Watch New Notes picks up new notes at each check, and Update User writes changes to a user record. For a message to a whole audience, Send a WhatApp Broadcast is the module to look at.

What Make does not give you here: the documentation lists these modules without describing them, and Make flags that page as AI-generated, so check important details with Enreach DialoX. When no listed module fits, Make an API Call reaches the rest of the API with the same connection. If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, and the Make review covers the editor in depth. Teams that want a hand can look at the Make training.

Connect

How do you connect Enreach DialoX to Make?

  1. 01

    Copy your API key and Bot ID

    In the Enreach DialoX studio, open the Channels section and click REST API. Copy the API key shown on screen, then the Bot ID just below. You need an active DialoX account with an API token for this to work.

  2. 02

    Add a DialoX module in Make

    In your scenario, add any Enreach DialoX module and click Create a connection. The connection is your DialoX account linked to Make once, then reused by every DialoX module. The Connection name field is optional but helps when you run several bots.

  3. 03

    Paste the credentials and save

    Enter the credentials you copied from DialoX, or follow the on-screen instructions Make displays, then save. The module can now read your DialoX data, and Make lists what it finds once the connection works.

First scenario

Your first scenario with Enreach DialoX

GoalWhen a conversation closes in Enreach DialoX, Make updates the matching user.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add your first module. Nothing runs yet, you are only drawing the flow.

  2. 02

    Add Watch Closed Conversations

    Search for Enreach DialoX, pick Watch Closed Conversations and click Create a connection with the API key and Bot ID you copied earlier. This trigger opens the flow.

  3. 03

    Add Update User

    Click the + on the right of the trigger and choose Update User. Map the data coming from the closed conversation into the fields Make shows, so the right user gets updated.

  4. 04

    Test with Run once

    Close a test conversation in DialoX, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the user record changed as planned.

  5. 05

    Schedule and switch on

    Open Scheduling on the first module. A new scenario checks every 15 minutes by default, the minimum on the Free plan. Pick your interval and switch the scenario on.

Triggers

What starts an Enreach DialoX scenario?

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

Enreach DialoX1Watch Closed Conversations

Watch Closed Conversations

triggerIn the docs only

This trigger hands your scenario the conversations DialoX marks as closed, one bundle (one item passed to the next module) per conversation. It is the natural starting point for anything that should happen once a chat is over.

How it fires
scheduled, Make checks the app on the scenario's schedule, shown by the clock badge on the module.
When to use it
after a support bot wraps up a chat and a person or another tool should take over the follow-up.
Watch out
the doc gives no description of this module, so run it once on a real closed conversation to see what it returns.
Enreach DialoX2Watch Conversation Tags

Watch Conversation Tags

triggerIn the docs only

Tags become signals with this one: the scenario receives conversation tags from DialoX and can route work based on them. It suits teams that already label conversations inside the studio and want those labels to mean something elsewhere.

How it fires
scheduled, Make checks the app on the scenario's schedule rather than being called by DialoX.
When to use it
when a tag such as a sales lead or a complaint should alert the right team in another tool.
Watch out
Make's documentation does not describe it, so use Run once to confirm which tag data comes through before building filters.
Enreach DialoX3Watch New Notes

Watch New Notes

triggerIn the docs only

Notes written in DialoX reach your scenario through this trigger, which is handy when agents or bots leave context you want stored somewhere else. Each new note becomes a bundle the next modules can read.

How it fires
scheduled, Make checks the app on the scenario's schedule; a note written just after a check waits for the next one.
When to use it
to copy notes into a CRM record or a shared document so the whole team sees them.
Watch out
no official description exists for this module; a test with Run once shows exactly what a note bundle holds.
Modules

What can Make do in Enreach DialoX?

Enreach DialoX gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Enreach DialoX1

Get a Bot

ActionIn the docs only

Going by its name, this one pulls the details of a DialoX bot into your scenario, so later modules can use them. Useful when you run more than one bot and the flow must know which one it deals with.

When to use it
before sending a message or a report that should mention the bot involved.
Watch out
the doc does not describe this module; test it with Run once to see the data returned.
Enreach DialoX2

Get a User

ActionIn the docs only

As its name says, it fetches one user from DialoX so the rest of the scenario knows who it is dealing with. A read like this is a calm first action to try on a new connection.

When to use it
right after a trigger, to enrich a closed conversation or a new note with the person behind it.
Watch out
check the returned bundle with Run once, since the doc lists no fields.
Enreach DialoX3

Make an API Call

ActionIn the docs only

Opens the rest of the Enreach DialoX API to your scenario, with the same connection as the other modules. It covers what the eight named modules leave out.

When to use it
when you need a DialoX endpoint that no listed module reaches.
Watch out
you write the request yourself, so keep the DialoX API documentation open while you set it up.
Enreach DialoX4

Send a Conversation Event

ActionIn the docs only

Judging by its name, it pushes an event into a DialoX conversation from Make, which lets something that happened in another tool show up on the DialoX side. It is the way back from your stack into the conversation.

When to use it
when an order, a ticket or a form in another app should be reflected in an ongoing conversation.
Watch out
the doc gives no detail on event types, so test on a demo conversation first.
Enreach DialoX5

Send a WhatApp Broadcast

ActionIn the docs only

Sends a broadcast from DialoX, the module name as Make spells it. Pick it when one message should go to a group rather than answering a single conversation.

When to use it
when a product update or a service notice has to reach an audience you already manage in DialoX.
Watch out
treat a broadcast as final once it leaves, so run the scenario once on a test audience before switching it on.
Enreach DialoX6

Update User

ActionIn the docs only

Its name points to one job: writing changes to a DialoX user record, so the profile stays current without anyone editing it by hand. It is the action that closes the loop after a trigger has found something new.

When to use it
after a closed conversation or a tag, to record what was learned about that person.
Watch out
map only the fields you mean to change, and check the result with Run once before going live.
Need help

Need help automating Enreach DialoX with Make?

A person reads every message.

FAQ

Questions about Enreach DialoX and Make

01Is the Enreach DialoX Make integration free?
Yes, on the Make side. Enreach DialoX is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Make counts operations, one module running on one bundle, against your plan. Your Enreach DialoX subscription is separate and depends on the vendor.
02What do you need to connect Enreach DialoX to Make?
An active Enreach DialoX account with an API token. In the DialoX studio, the Channels section has a REST API entry that shows both the API key and the Bot ID; copy the two values. Then add any Enreach DialoX module in Make, click Create a connection, give it a name if you like and paste the credentials. The connection is created once and every DialoX module in your scenarios reuses it, so there is nothing to repeat when you add more modules later.
03Does Enreach DialoX start a Make scenario instantly?
No. All three triggers, Watch Closed Conversations, Watch Conversation Tags and Watch New Notes, are scheduled: Make checks DialoX on the scenario's schedule instead of DialoX calling Make. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan. Paid plans let you go down to 1 minute. So a conversation that closes just after a check is picked up at the next one, and the scenario then handles every new item found since the previous check.
04What if the Enreach DialoX module you need is missing in Make?
Use Make an API Call. With it, any endpoint of the Enreach DialoX API can be called from your scenario, using the same connection as the other modules, so no second login is needed. It asks you to build the request yourself, so keep the vendor's API documentation at hand. One more point: Make marks its DialoX documentation as AI-generated and advises checking important details with Enreach DialoX directly, which is worth doing before you rely on a module in production.
05Should you use Make or n8n for Enreach DialoX?
It depends on your criteria rather than on a winner. On Make, Enreach DialoX offers 9 modules, a guided connection and a visual editor where Run once shows each bundle, which suits people starting out. Whether n8n has a node for this specific app is not covered on this page, so check its node list before comparing. Then weigh the tool your team already uses, the modules you need and how you prefer to test flows. The comparison page linked above goes through these criteria one by one.
Same platform

Other docs you might need on this stack.

Browse all integrations