Resources · Make integration

eSIM Make integrationAutomate eSIM with Make.

Can Make run your eSIM reseller account while you sell? The eSIM Make integration gives you 13 modules: 1 scheduled trigger, 10 actions and 2 searches. This guide is for resellers who handle profiles by hand, and it walks you from the connection to a first working scenario.

Try the eSIM integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the eSIM Make integration do?

The eSIM Make integration links your eSIM reseller account to Make, so profile orders, top-ups and status changes can happen inside a scenario, the automation you build in Make as a chain of modules. Each module is one brick of that chain, and none of it needs code.

Profiles that follow your sales. A sale lands in your shop or your form tool, and Order a Profile places the eSIM order right away. Top Up a Profile follows the same logic when a returning customer pays for more.

Support that answers faster. A customer calls with a problem: Get an eSIM by ICCID or Get single eSIM by Order Number pulls the record, and Suspend a Profile or Revoke a Profile acts on it without opening the dashboard.

A reseller account you keep an eye on. Watch New Notifications picks up new eSIM notifications at each scheduled check, and Get the Account Balance tells you what is left before a batch of orders.

What Make does not give you: the Make documentation for eSIM lists the modules without describing their fields, so test each one with Run once before trusting it. For anything the list skips, Make an API Call reaches the rest of the API. Many apps also have an n8n node; the n8n vs Make comparison sets out the criteria, and the Make pricing page explains what an operation costs you. For a first build with guidance, the Make training walks you through it.

Connect

How do you connect eSIM to Make?

  1. 01

    Grab your API key

    You need an active eSIM reseller account. In the eSIM dashboard, open the Developer section and copy the API key shown on screen. Keep it in a safe place for the next step.

  2. 02

    Add an eSIM module

    In your scenario, click the +, search for eSIM and pick a module. Then click Create a connection. A connection is your eSIM account linked to Make once, and every eSIM module reuses it.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you run several accounts; this field is optional. Paste the API key you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario with eSIM

GoalWhen a new notification shows up in eSIM, Make texts it to your phone with Send a SMS, so you hear about it without opening the dashboard.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor to place the first module.

  2. 02

    Place the trigger

    Search for eSIM, choose Watch New Notifications, then pick your connection or click Create a connection with the API key from your dashboard.

  3. 03

    Add the text message

    Click the + on the right of the trigger and add Send a SMS. Map the notification data from the first module into the message, so the text carries what eSIM reported.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one notification.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; keep that or change it, then switch the scenario on.

Triggers

What starts an eSIM scenario

1 module starts a scenario when something happens in eSIM. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by eSIM as soon as it happens.

eSIM1Watch New Notifications

Watch New Notifications

triggerIn the docs only

This trigger picks up the notifications your eSIM account receives and hands each one to the rest of the scenario as its own bundle. It is the only way to start a scenario from eSIM itself.

How it fires
scheduled. Make checks the app on the scenario's schedule, which is every 15 minutes by default and never under 15 minutes on the Free plan, so nothing arrives the second it happens.
When to use it
you want a team channel, an SMS or a log to follow what eSIM reports without opening the dashboard.
Watch out
the doc does not describe the notification content, so run the scenario once and read the bundle before mapping anything.
Modules

Every eSIM module, and when to pick it

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

eSIM1

Cancel a Profile

ActionIn the docs only

Cancel a Profile ends a profile for good from inside a scenario, so a refund or a closed customer file no longer leaves a live eSIM behind. Pick it over Suspend a Profile when the line should not come back.

When to use it
a refund is approved in your shop and the matching profile must stop.
Watch out
the doc does not say whether it can be undone, so add a filter so only confirmed cancellations reach it.
eSIM2

Get an eSIM by ICCID

ActionIn the docs only

Get an eSIM by ICCID returns the record of one eSIM when you already hold its ICCID, the number that identifies the SIM. Your later modules then work with fresh data instead of a copy in a spreadsheet.

When to use it
a support ticket quotes the ICCID and you want the current record before replying.
Watch out
the doc does not list the returned fields, so check them with Run once.
eSIM3

Get single eSIM by Order Number

ActionIn the docs only

This module finds one eSIM from the order number, which is often the only reference a customer keeps after buying. It saves you from translating an order into an ICCID by hand.

When to use it
your shop or help desk stores the order number and you need the eSIM behind it to reply or act.
Watch out
it returns a single eSIM; for a wider view, List Allocated Profiles fits better.
eSIM4

Get the Account Balance

ActionIn the docs only

Get the Account Balance reads what is left on your eSIM reseller account, so a scenario can check funds before it spends them. It works on the account, not on any single profile.

When to use it
place it ahead of Order a Profile or Top Up a Profile and stop the run with a filter when the balance looks too low.
Watch out
the doc gives no threshold, so pick your own.
eSIM5

List Allocated Profiles

SearchIn the docs only

List Allocated Profiles is a search that returns the profiles already assigned on your account, each one as a separate bundle. That gives you an inventory you can push to a sheet or compare with your customer list.

When to use it
an audit of who holds which profile, or a reconciliation after a busy sales period.
Watch out
a search can return zero, one or many bundles, and every later module runs once per bundle, which uses operations.
eSIM6

List Data Packages

SearchIn the docs only

List Data Packages pulls the packages your reseller account can sell, one bundle per package. Your catalog or order form can then follow the offer instead of being retyped by hand.

When to use it
you publish plans on a website or in a sheet and want them to match what eSIM offers.
Watch out
each package is a bundle, so a module placed after it runs as many times as there are packages.
eSIM7

Make an API Call

ActionIn the docs only

Make an API Call sends your own request to the eSIM API through the connection you already set up, with no second login. It covers any endpoint the ready-made modules skip.

When to use it
you need an eSIM feature that none of the other 12 modules handles.
Watch out
you write the request yourself from the eSIM developer documentation; start with a read request and check the answer with Run once.
eSIM8

Order a Profile

ActionIn the docs only

Order a Profile places an eSIM order from your reseller account inside a scenario, so the sale and the provisioning happen in one flow. This is the module that turns a paid order into a profile.

When to use it
a customer pays in your shop or fills a form, and the eSIM order should follow without anyone copying details.
Watch out
an order most likely draws on your balance (the doc does not say), so check Get the Account Balance first.
eSIM9

Revoke a Profile

ActionIn the docs only

Revoke a Profile withdraws a profile from its holder from a scenario, which keeps a security or fraud reaction in the same flow as the alert. The module sits next to Cancel and Suspend, and the doc does not explain how the three differ.

When to use it
your fraud check flags an order and the profile must be pulled back.
Watch out
confirm the eSIM behavior with the vendor before automating it.
eSIM10

Send a SMS

ActionIn the docs only

Send a SMS sends a text message through your eSIM account, so the customer hears from you at the right step of the flow. It is the only module of the app that talks to people rather than to profiles.

When to use it
right after Order a Profile or Top Up a Profile, to confirm the purchase to the buyer.
Watch out
test on your own number first with Run once.
eSIM11

Suspend a Profile

ActionIn the docs only

Suspend a Profile pauses a profile from a scenario, the softer choice when the line may be needed again. Your billing or support tool can then react to a problem without a trip to the dashboard.

When to use it
a payment fails or a customer reports a lost device and you want to freeze the eSIM while it gets sorted.
Watch out
the doc lists no resume module, so plan how the line comes back.
eSIM12

Top Up a Profile

ActionIn the docs only

Top Up a Profile adds credit to a profile a customer already holds, so a repeat purchase does not need a new eSIM. Choose it over Order a Profile whenever the customer keeps the same line.

When to use it
a customer buys an extra package in your shop and the top-up should follow straight after payment.
Watch out
a top-up most likely draws on your balance (the doc does not say), so pair it with Get the Account Balance.
Need help

Need help automating eSIM with Make?

A person reads every message.

FAQ

eSIM and Make: common questions

01Is the eSIM Make integration free?
Yes, on the Make side: eSIM is a standard app, available from the Free plan. The Free plan allows 2 active scenarios, a minimum of 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) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. The eSIM reseller account itself is a separate subscription, described on the eSIM pricing page.
02What is needed to connect eSIM to Make?
An active eSIM reseller account and its API key. In the eSIM dashboard, the Developer section shows the key; copy it. In Make, add any eSIM module, click Create a connection, give it a name if you want to tell several accounts apart, then paste the key. That connection is saved once and every eSIM module in your scenarios reuses it, so there is nothing to repeat when you add a second module or build a new scenario later.
03Does the eSIM trigger in Make fire in real time?
No. Watch New Notifications is a scheduled trigger: Make checks eSIM on the scenario's schedule rather than being called the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. The module carries the clock badge in the editor, which is how Make marks a scheduled trigger. If a notification must reach someone quickly, shorten the schedule on a paid plan.
04What if an eSIM module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the eSIM API with the same connection, so you reach features the 12 other modules do not cover without setting up a new login. You write the request from the eSIM developer documentation. Also keep in mind that the Make documentation for eSIM is AI-generated from the vendor's docs and may contain mistakes, so test each module with Run once and contact eSIM directly when a behavior is unclear.
05Make or n8n for eSIM?
It depends on the tool your team already runs. In Make, eSIM comes with 13 ready modules, one scheduled trigger and Make an API Call for the rest, all driven from a visual editor where you test with Run once. Many apps also have an n8n node, so check whether one exists for eSIM before you choose. The deciding criteria are where your other automations already live and who will maintain the scenarios, not a ranking between the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations