Resources · Make integration

mission‹one› dialog+ Make integrationAutomate mission‹one› dialog+ with Make.

Can Make keep your mission‹one› dialog+ subscriber list up to date for you? The mission‹one› dialog+ Make integration gives you 5 modules: 4 actions and 1 search, all about subscribers. This page is for marketers who know the app and are new to Make, and it walks you from the connection to a working first scenario.

Try the mission‹one› dialog+ integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the mission‹one› dialog+ Make integration do for you?

The mission‹one› dialog+ Make integration links your mission‹one› dialog+ account to Make, a no-code tool where you build a scenario, meaning an automation made of modules chained one after another. Each module is one brick of that chain. Here, the bricks let you add a subscription, look up subscribers and change their details without typing anything by hand.

Fewer duplicates in your list. Before touching anything, a scenario can run Search Subscribers to check whether a contact is already there, then use Update a Subscriber when it finds a match. The search step is what keeps a second copy of the same person out of your base.

Sign-ups that arrive on their own. Pair a form or a shop from another app with Create a subscription, and every new entry ends up in mission‹one› dialog+. Tools such as the 123FormBuilder Make integration can play the role of that first step.

A clean read before you act. Get a Subscriber(s) pulls a record into the scenario so the next modules work with what mission‹one› dialog+ actually holds.

One honest limit: Make says itself that the public documentation for this app is incomplete, so the page only covers the five listed modules. When you need something else from the API, Make an API Call is the way in. The same app often has an n8n node too; the n8n vs Make comparison helps you pick, and Make pricing explains what counts against your plan.

Connect

How do you connect mission‹one› dialog+ to Make?

  1. 01

    Add a module and open the connection

    In your scenario, add any mission‹one› dialog+ module, then click Create a connection. A connection is your account linked to Make once and reused by every module of the app.

  2. 02

    Give it a clear name

    Naming the connection is optional, but a label such as the account or the client it belongs to saves you guesswork later, especially when several people share the same Make team.

  3. 03

    Authorize and save

    Depending on what the app offers, approve Make on the mission‹one› dialog+ page or paste the key the app gives you, then click Save. Every module of the app can now use this connection.

First scenario

Your first scenario with mission‹one› dialog+

GoalWhen a contact comes in from another app, Make looks for them in mission‹one› dialog+ and updates their record.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since mission‹one› dialog+ has no trigger, start with the app that produces your contacts, such as a form tool.

  2. 02

    Search the subscriber

    Click the + on the right and search mission‹one› dialog+. Pick Search Subscribers, then create the connection when Make asks for it. Map the contact details coming from the first module into the search.

  3. 03

    Update the record

    Add Update a Subscriber after the search and map the subscriber it found. Then fill the fields you want to change with data from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item, here one contact, passed from module to module.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run on one bundle is an operation, which is what Make counts on your plan.

Modules

What each mission‹one› dialog+ module does

mission‹one› dialog+ gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

mission‹one› dialog+1

Create a subscription

ActionIn the docs only

Adds a new subscription in mission‹one› dialog+ from data your scenario already has, so a sign-up collected elsewhere lands in your base without a copy and paste.

When to use it
right after a form, a shop or another app hands over a new contact who agreed to hear from you.
Watch out
nothing says it checks for an existing subscriber, so for people already in your list use Update a Subscriber instead.
mission‹one› dialog+2

Get a Subscriber(s)

ActionIn the docs only

Brings the stored details of subscribers into your scenario, so later modules decide on what mission‹one› dialog+ really contains instead of on a guess.

When to use it
you already know which subscriber you want and need their current record before a decision or an update.
Watch out
the name hints it may return one or several subscribers; check the bundles after Run once.
mission‹one› dialog+3

Make an API Call

ActionIn the docs only

Opens any endpoint of the mission‹one› dialog+ API from your scenario, with the connection you already set up, for everything the four other modules do not cover.

When to use it
the task you have in mind has no ready-made module in the list above.
Watch out
this module expects you to know the app's API, and Make's documentation for this app is incomplete, so ask the vendor for the reference.
mission‹one› dialog+4

Search Subscribers

SearchIn the docs only

Looks through your subscribers and returns what matches, which lets a scenario tell a known contact from a new one before it writes anything.

When to use it
as the check that sits in front of Update a Subscriber, so the change lands on the right record.
Watch out
a search can return zero, one or several bundles, and each following module then runs once per result, which costs operations.
mission‹one› dialog+5

Update a Subscriber

ActionIn the docs only

Changes the details of a subscriber who already exists, so the record in mission‹one› dialog+ follows what happened in your other tools.

When to use it
a contact changed something upstream, a new email or a new preference, and your list should reflect it.
Watch out
the module needs to know which subscriber to change, so feed it the result of Search Subscribers or Get a Subscriber(s).
Need help

Need help automating mission‹one› dialog+ with Make?

A person reads every message.

FAQ

Questions about the mission‹one› dialog+ Make integration

01Is the mission‹one› dialog+ Make integration free?
Yes, on the Make side. mission‹one› dialog+ is a standard app, so you can use it from the Free plan. That plan allows 2 active scenarios, a scheduled run no more often than every 15 minutes, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits each month. Your own mission‹one› dialog+ subscription is a separate matter that this page does not cover.
02What does the mission‹one› dialog+ Make integration need to connect?
An active mission‹one› dialog+ account and a Make account. Make's documentation lists no specific prerequisite for this app. You add a module, click Create a connection, optionally name it, then either approve Make on the app's page or paste the key the app provides, and click Save. The connection is then reused by all five modules, so you set it up only once per account. If several accounts are involved, create one connection for each.
03Does mission‹one› dialog+ trigger a Make scenario in real time?
No, because the app has no trigger module at all. Its five modules are four actions and one search. To start a scenario, open it with a module from another app, such as a form or a shop that reports new entries, and put mission‹one› dialog+ after it. You can also set a schedule on the first module: every 15 minutes by default, 15 minutes at minimum on the Free plan and 1 minute on paid plans.
04What if a mission‹one› dialog+ module is missing in Make?
Use Make an API Call. It reaches any endpoint of the mission‹one› dialog+ API through the same connection, so one scenario can mix the listed modules and custom requests. Keep in mind that Make describes its documentation for this app as limited for lack of public information, so the details of each endpoint have to come from the vendor. If the API does not offer the feature either, another app in your scenario may handle that part instead.
05Make or n8n for mission‹one› dialog+?
It depends on the tool you already run. With Make you get five ready modules focused on subscribers, including a search that guards against duplicates, and Make an API Call for the rest. The same app often has an n8n node as well, so check whether one exists before deciding. Pick the platform where your other automations already live, since keeping all your scenarios in one place makes them easier to follow and to fix.
Same platform

Other docs you might need on this stack.

Browse all integrations