Resources · Make integration

eSIM NEXT Make integrationAutomate eSIM NEXT with Make.

Can Make place eSIM NEXT orders for you without anyone typing them in? The eSIM NEXT Make integration gives you 2 action modules and no trigger. This guide is for ops teams who sell or hand out eSIMs, and it walks you from the connection to a first scenario that runs.

Try the eSIM NEXT integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the eSIM NEXT Make integration do?

The eSIM NEXT Make integration links your eSIM NEXT account to Make, a no-code tool where you build a scenario (the automation itself, a chain of bricks called modules). It offers two actions: Create Order, and Make an API Call for anything the first one does not cover. Nothing inside eSIM NEXT can start a scenario on its own.

Orders that follow a sale. A travel shop can open its scenario with the module of its store or form app, then pass each new buyer to Create Order. The data flows as bundles, one item per module run, so each buyer becomes one order.

A batch placed on a schedule. A team that collects requests in a spreadsheet can let Make check it at the scenario's schedule, 15 minutes by default, and send each row to Create Order.

Calls the listed modules skip. Make an API Call reaches any endpoint of the eSIM NEXT API with the same connection, which is how you go past the single order action.

Be clear about the limits. Make itself says its documentation for this app is incomplete, because too little public information exists about eSIM NEXT, so field names and behavior are something you check in the editor. If a run fails, the Make troubleshooting guide covers the usual causes, and the Make pricing page explains how operations are counted.

The same app may also have an n8n node. The n8n vs Make comparison sets out the criteria if you are weighing the two tools.

Connect

How do you connect eSIM NEXT to Make?

  1. 01

    Open the connection window

    Add the Create Order module to a scenario and click Create a connection. A connection is your eSIM NEXT account linked to Make once; every module of the app then reuses it.

  2. 02

    Name it if you want

    Naming the connection is optional. A clear label helps later, for example when a client account and a test account sit side by side in the same Make workspace.

  3. 03

    Authorize and save

    Either approve Make on the eSIM NEXT page that opens, or paste the key eSIM NEXT gives you, depending on what the window asks. Then click Save and the module shows your account.

First scenario

Build your first scenario with eSIM NEXT

GoalWhen a new request lands in another app, Make places an order in eSIM NEXT.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since eSIM NEXT has no trigger, pick the app where requests arrive.

  2. 02

    Set up the starting module

    Search that app by name, choose its module, and link your account with Create a connection. Make then lists the sheets or objects it can read there.

  3. 03

    Add Create Order

    Click the + on the right of the first module, search eSIM NEXT and pick Create Order. Connect your account, then map the data from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received and confirm the order looks right.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What the eSIM NEXT modules do

eSIM NEXT gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

eSIM NEXT1

Create Order

ActionIn the docs only

This is the module that turns an event somewhere else into an order on the eSIM NEXT side, so nobody has to copy a customer's request by hand. It is an action: it acts on one item each time it runs.

When to use it
right after the module that brings in a paid purchase or an approved request, one order per incoming bundle.
Watch out
Make publishes no field description for it, so open the module and check each field before you switch the scenario on.
eSIM NEXT2

Make an API Call

ActionIn the docs only

You get a way to reach any endpoint of the eSIM NEXT API from your scenario, reusing the connection you already created, when Create Order alone does not answer your need.

When to use it
the task you have in mind is not an order, or needs data that the order module does not return.
Watch out
you write the request yourself and Make describes no endpoint for this app, so get them from eSIM NEXT and test the call with Run once.
Need help

Need help automating eSIM NEXT with Make?

A person reads every message.

FAQ

Questions about the eSIM NEXT Make integration

01Is the eSIM NEXT Make integration free?
Yes, eSIM NEXT is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month, one per module run on one bundle.
02What do you need to connect eSIM NEXT to Make?
An eSIM NEXT account and a Make account. The documentation lists no prerequisite and no dedicated connection steps, so you follow the generic path: add an eSIM NEXT module, click Create a connection, optionally give it a name, then authorize Make on the eSIM NEXT page or paste the key the app provides, and click Save. The connection is then shared by both modules of the app, so you set it up only once.
03Can an eSIM NEXT Make scenario start in real time?
Not from eSIM NEXT itself, because the app has no trigger module in Make. You start the scenario another way. The first option is a trigger from another app, such as the store or form where requests come in, followed by Create Order. The second is a schedule on the first module, every 15 minutes by default, or every minute on a paid plan. If that other app offers an instant trigger, it calls Make through a webhook as soon as something happens.
04What if the eSIM NEXT module you need is missing?
Use Make an API Call. It sends a request to any endpoint of the eSIM NEXT API with the connection you already have, which covers everything beyond Create Order. Make warns that its documentation for eSIM NEXT is limited, because there is not enough public information about the app, so ask eSIM NEXT which endpoints exist and what each one expects, then test each call with Run once before switching the scenario on.
05Should you use Make or n8n for eSIM NEXT?
It depends on the criteria that matter to your team. On Make, eSIM NEXT offers 2 modules: Create Order and Make an API Call, with no trigger. The same app often has an n8n node too, so compare what each tool offers for your case: the modules available, how you start a workflow without a trigger, and how usage is counted. Neither choice is better by default; check both catalogs before you build.
Same platform

Other docs you might need on this stack.

Browse all integrations