Resources · Make integration

UseINBOX Make integrationAutomate UseINBOX with Make.

Can Make keep your UseINBOX contacts, lists and campaigns in sync without code? The UseINBOX Make integration gives you 11 modules: 5 triggers and 6 actions. This guide is for marketers who want to link the account, build a first scenario and pick the right module.

Try the UseINBOX integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the UseINBOX Make integration do?

The UseINBOX Make integration links your UseINBOX account to Make, so a scenario (the automation you build in Make, a chain of modules) can react to new contacts, tags or unsubscribes and then update contacts, fill lists or send a campaign. Each module is one brick of that chain, and you set it up without writing code.

Contacts that land in the right list. Watch New Contacts is instant: UseINBOX tells Make the moment a contact is added, and Add a Contact To a List files that person where your next newsletter will reach them.

Unsubscribes that travel. Watch Unsubscribed Contacts spots people who left a campaign, so another tool connected to Make, a CRM or a support desk, can stop writing to them too. In the other direction, Mark Contact as Unsubscribed records an opt-out collected somewhere else.

Tags that build lists. Watch Tags notices a new tag, and Create a Contact List prepares the list that goes with it, ready for Send a Campaign.

The official documentation gives no numeric limit and no prerequisite beyond a UseINBOX account. When a listed module stops short, Make an API Call reaches the rest of the UseINBOX API with the same connection. If you are weighing tools, read n8n vs Make; for costs, see Make pricing, and when a run fails, Make troubleshooting walks through the usual causes.

Connect

How do you connect UseINBOX to Make?

  1. 01

    Add a UseINBOX module

    In your scenario, pick any UseINBOX module and click Create a connection. A connection is your UseINBOX account linked to Make once and reused by every UseINBOX module. For Watch New Contacts, click Create a webhook first.

  2. 02

    Enter your UseINBOX login

    Give the connection a clear label in Connection name if you like, then type the username of your UseINBOX account in Username and its password in Password. Nothing else is asked.

  3. 03

    Save and confirm

    Click Save. If UseINBOX asks you to authenticate or approve access, confirm it. The connection then appears in the module, and Make can read your segments, tags, lists and contacts.

First scenario

Build your first UseINBOX scenario

GoalWhen a new tag is created in UseINBOX, Make creates a matching contact list.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for UseINBOX and choose Watch Tags, the module that notices each new tag.

  2. 02

    Link your account

    Click Create a connection, enter your UseINBOX username and password, then save. Once linked, Make can read the tags of the account and fill the module for you.

  3. 03

    Add the list action

    Click the + on the right of Watch Tags and pick Create a Contact List. Map data from the tag bundle, one item passed between modules, into the fields Make shows.

  4. 04

    Test with Run once

    Create a tag in UseINBOX, then click Run once. Open the bubble above each module to read the bundles it received and check that the new list looks right in UseINBOX.

  5. 05

    Schedule and switch on

    Click the clock on Watch Tags: a new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then flip the scenario switch on so it keeps running.

Triggers

UseINBOX triggers in Make

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

UseINBOX1Watch Segments

Watch Segments

Scheduled trigger

In Make“Triggers when a new segment created.”

You get a scenario that starts whenever someone creates a new segment in UseINBOX, so the audience your team just defined can be reported, shared or reused elsewhere without a copy and paste.

How it fires
scheduled, Make checks the app on the scenario's schedule and collects the segments created since the last check.
When to use it
a marketer defines a segment for a launch and the sales team should hear about it in their own tool.
Watch out
it reacts to new segments only; changes to an existing segment do not start anything.
UseINBOX2Watch Unsubscribed Contacts

Watch Unsubscribed Contacts

Scheduled trigger

In Make“Triggers when a contact unsubscribes from a campaign.”

This trigger hands you every contact who unsubscribed from a campaign, one bundle per person, so the opt-out can be respected beyond UseINBOX, in a CRM, a spreadsheet or a support desk.

How it fires
scheduled, Make checks the app on the scenario's schedule, so people who left since the previous run arrive together.
When to use it
your sales reps email from another tool and must stop contacting anyone who opted out of your newsletter.
Watch out
each contact returned costs an operation in every module after it.
UseINBOX3Watch Updated Contacts

Watch Updated Contacts

Scheduled trigger

In Make“Triggers when a contact is updated.”

Every time a contact record changes in UseINBOX, this module passes the updated contact to the rest of your scenario, which keeps a copy of your audience elsewhere current.

How it fires
scheduled, Make checks the app on the scenario's schedule and returns the contacts edited since the last check.
When to use it
a customer fixes their details in UseINBOX and your billing or CRM tool should show the same data.
Watch out
do not pair it with Update a Contact on the same account, since each update can start the scenario again.
UseINBOX4Watch Tags

Watch Tags

Scheduled trigger

In Make“Triggers when a new tag is created.”

Watch Tags lets a fresh tag in UseINBOX set things in motion, such as preparing a contact list or warning a colleague that a new label exists.

How it fires
scheduled, Make checks the app on the scenario's schedule and picks up the tags created since the last run.
When to use it
your team tags contacts by interest and each new interest deserves its own list and campaign.
Watch out
it sees newly created tags, not a tag being added to a contact, so tagging an existing contact does not start this scenario.
UseINBOX5Watch New Contacts

Watch New Contacts

Instant trigger

In Make“Triggers when a new contact is added.”

The quickest way to greet new subscribers: as soon as a contact is added to UseINBOX, your scenario receives it and can welcome, sort or report that person.

How it fires
instant, the app calls Make through a webhook as soon as it happens, which is the lightning badge on the module.
When to use it
a signup should reach your sales team or your CRM while the lead is still warm.
Watch out
the webhook must be created before the connection, and the scenario must stay switched on to receive anything.
Modules

UseINBOX actions in Make

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

UseINBOX1

Add a Contact To a List

Action

In Make“Adds a new contact to the contact list.”

Puts a new contact into the UseINBOX list you choose, so leads gathered by another app become reachable by your next campaign.

When to use it
a form, a shop order or a webinar signup lands in Make and the person should join the matching mailing list.
Watch out
the list must exist first; create it by hand or with Create a Contact List earlier in the scenario.
UseINBOX2

Create a Contact List

Action

In Make“Creates a new contact list.”

Gives you a brand new contact list in UseINBOX, created by the scenario rather than by hand, ready to receive contacts and campaigns.

When to use it
each new event, product or tag calls for its own list, and you want it prepared the moment the trigger fires.
Watch out
run it once per list; placed after a trigger that returns many bundles, it creates one list for each bundle.
UseINBOX3

Send a Campaign

Action

In Make“Creates a campaign with the newsletter.”

Turns a newsletter into a campaign straight from your scenario, so a list built by Make can receive an email without anyone opening UseINBOX.

When to use it
a new list has been filled and the content is already written, for instance an announcement for a segment your team just created.
Watch out
test with Run once on a small list first; an email that has gone out cannot be recalled.
UseINBOX4

Update a Contact

Action

In Make“Updates a given contact.”

Changes an existing UseINBOX contact with data coming from elsewhere, which keeps your audience accurate without manual edits.

When to use it
a customer changes details in your CRM or shop, and your newsletter tool should hold the same information.
Watch out
in a scenario that starts with Watch Updated Contacts on the same account, this module can feed the trigger and make the scenario run in a loop.
UseINBOX5

Mark Contact as Unsubscribed

Action

In Make“Changes the contact status to unsubscribed.”

Records an opt-out in UseINBOX by switching the contact's status to unsubscribed, so a request made outside your newsletter is honored inside it too.

When to use it
someone asks your support desk or sales rep to stop receiving emails, and that wish should reach UseINBOX without a manual step.
Watch out
use it only on a clear request; check the contact first, since an unsubscribed person no longer receives your campaigns.
UseINBOX6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the UseINBOX API to your scenario: when the five triggers and five other actions do not cover a task, this module calls any endpoint with the connection you already have.

When to use it
you need something the listed modules skip, such as reading data they never return.
Watch out
you build the request yourself, so keep the UseINBOX API documentation open next to the module.
Need help

Need help automating UseINBOX with Make?

A person reads every message.

FAQ

UseINBOX and Make: common questions

01Is the UseINBOX Make integration free?
Yes. UseINBOX is a standard app in Make, so its modules work on the Free plan. That plan keeps you to 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle, so check your monthly credits before watching a large contact base.
02What do you need to connect UseINBOX to Make?
A UseINBOX account and its login details are enough; the documentation lists no other prerequisite. Add a UseINBOX module, click Create a connection, optionally name it, then type your UseINBOX username and password and save. If UseINBOX asks for confirmation, approve access. For the instant trigger Watch New Contacts, click Create a webhook before creating the connection, otherwise the scenario has no address to receive new contacts. Once saved, the same connection serves every UseINBOX module of your scenarios.
03Does the UseINBOX trigger in Make fire in real time?
It depends on the trigger. Watch New Contacts is instant: UseINBOX calls Make through a webhook as soon as a contact is added. The four others, Watch Segments, Watch Unsubscribed Contacts, Watch Updated Contacts and Watch Tags, are scheduled: Make checks UseINBOX on the scenario's schedule, every 15 minutes by default. On the Free plan that interval cannot go lower; paid plans can check every minute. Pick the instant trigger when a delay would hurt, a scheduled one otherwise.
04What if a UseINBOX module is missing in Make?
Use Make an API Call. It reaches any endpoint of the UseINBOX API with the connection you already set up, so a task that none of the ten other modules covers can still live in the same scenario. You write the request yourself from the UseINBOX API documentation. The Make documentation gives no numeric limit for this app, so the constraints you meet will usually come from your Make plan: interval, execution time and operations.
05Should you use Make or n8n for UseINBOX?
It depends on your criteria rather than on a winner. On Make, UseINBOX comes with 11 ready modules, one instant trigger and a visual editor where each step is a module you click together. Many apps also have an n8n node, so compare what each tool offers for UseINBOX: which events can start a workflow, which contact and campaign actions exist, and how you would call the API for the rest. Then choose the editor your team is most comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations