Resources · Make integration

EleAPIs Make integrationAutomate EleAPIs with Make.

Can Make react to what happens in your EleAPIs account? Yes: the EleAPIs Make integration gives you 8 modules, 3 triggers and 5 actions, around contacts and messages. This guide shows how to link your account, build a first scenario and pick the right module.

Try the EleAPIs integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the EleAPIs Make integration do for you?

The EleAPIs Make integration links your EleAPIs account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or sends something. EleAPIs brings 3 triggers that start a scenario and 5 actions that act on contacts and messages.

A welcome message for every new contact. Watch New Contact Created picks up each contact added in EleAPIs, and Send Template Message answers right after. Nobody has to remember to say hello.

Incoming messages that land in your other tools. Watch New Incoming Message passes each new message to the next module, so you can copy it into a spreadsheet, a CRM or a team chat through another app of Make.

WhatsApp orders that reach your back office. Watch New WhatsApp Order Created hands each order to the rest of the scenario. Pair it with Update Contact Attributes to keep the buyer's record current in EleAPIs.

Know the limits before you start. Make's own documentation for EleAPIs is marked as limited: it lists the modules but explains neither their fields nor their behavior, so test each module with Run once before you rely on it. When a listed module does not cover your need, Make an API Call reaches the rest of the EleAPIs API with the same connection. If you are still choosing a tool, read our n8n vs Make comparison, and Make pricing tells you what each plan includes. The Make training is there if you want guided practice.

Connect

How do you connect EleAPIs to Make?

  1. 01

    Add an EleAPIs module

    In your scenario, click the +, search for EleAPIs and pick any module. Then click Create a connection. A connection is your EleAPIs account linked to Make once, then reused by every EleAPIs module.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the account or the brand it serves saves confusion later, when several people or several EleAPIs accounts share the same Make organization.

  3. 03

    Authorize and save

    Authorize Make on the EleAPIs page that opens, or paste the key EleAPIs gives you, depending on what the connection window asks for. Click Save, and the module can now read your account.

First scenario

Your first scenario with EleAPIs

GoalWhen a new contact is created in EleAPIs, Make sends that contact a template message.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor. That empty circle is where your first module goes.

  2. 02

    Place the trigger

    Search for EleAPIs, choose Watch New Contact Created and select your connection, or create it with Create a connection if this is your first EleAPIs module.

  3. 03

    Add the message

    Click the + on the right of the trigger and pick Send Template Message. Map the contact that the trigger returns into the fields Make shows, so each new person gets the message.

  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 from a module to the next, here one contact.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Set the schedule, then switch the scenario on.

Triggers

What starts an EleAPIs scenario

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

EleAPIs1Watch New Contact Created

Watch New Contact Created

triggerIn the docs only

Every contact that appears in EleAPIs becomes a bundle your scenario can work with, ready to be greeted, copied to another tool or enriched.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a contact shows up at the next check, not the second it is created.
When to use it
when the arrival of a contact should set something in motion, such as a welcome message or a record in your CRM.
Watch out
the documentation says nothing about which contact details the trigger returns, so read them in the Run once output first.
EleAPIs2Watch New Incoming Message

Watch New Incoming Message

triggerIn the docs only

This trigger turns each message your EleAPIs account receives into a bundle, so a reply from a customer can travel to the rest of your stack.

How it fires
scheduled. Make checks the app on the scenario's schedule and collects the messages that arrived since the last check.
When to use it
when a support or sales team wants every inbound message logged in a shared tool instead of read in one inbox only.
Watch out
each message is one bundle, and every module after the trigger counts one operation per bundle on your plan.
EleAPIs3Watch New WhatsApp Order Created

Watch New WhatsApp Order Created

triggerIn the docs only

Orders placed through WhatsApp in EleAPIs come out as bundles, one per order, that the next modules can pass to your order sheet, your stock tool or your team.

How it fires
scheduled. Make checks the app on the scenario's schedule, so an order waits for the next check before the scenario sees it.
When to use it
when an order taken in a chat must reach the people who prepare and ship it.
Watch out
the order content is undocumented, so check with Run once which details come through before you map them.
Modules

What the EleAPIs modules can do

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

EleAPIs1

Add a Contact

ActionIn the docs only

You get a new contact in EleAPIs without typing it, built from data that another module of the scenario already holds, such as a form entry or a CRM row.

When to use it
when leads captured elsewhere must be reachable from EleAPIs before anyone messages them.
Watch out
run it on a person who already exists before you rely on it, since the documentation does not say how duplicates are handled.
EleAPIs2

Make an API Call

ActionIn the docs only

This module opens the rest of the EleAPIs API to your scenario, with the same connection as the other modules, for any request the listed modules do not cover.

When to use it
when you need an EleAPIs feature that has no module of its own in Make.
Watch out
you write the request yourself, so you need the EleAPIs API reference; Make's own documentation for this app is limited and does not describe the endpoints.
EleAPIs3

Send Session Message

ActionIn the docs only

With this action your scenario answers a contact in EleAPIs by itself, with a message built from the data of the previous modules.

When to use it
right after Watch New Incoming Message, when a received message should get a reply without waiting for someone to open the inbox.
Watch out
Make's documentation does not explain what separates a session message from a template message, so confirm with EleAPIs which one fits your case.
EleAPIs4

Send Template Message

ActionIn the docs only

Your scenario sends a template message through EleAPIs and fills it with the contact's details on each run.

When to use it
to greet a contact that Watch New Contact Created just picked up, or to confirm an order.
Watch out
the template itself lives in EleAPIs; the Make documentation lists this module without its fields, so test it with Run once on your own number first.
EleAPIs5

Update Contact Attributes

ActionIn the docs only

This action keeps a contact's attributes in EleAPIs current, changing what you store about the person instead of adding a second record.

When to use it
after a WhatsApp order or a message, to note on the buyer's record what just happened, so the next message can take it into account.
Watch out
it changes an existing contact, so map the right contact from the previous module and try it on a test record before you switch the scenario on.
Need help

Need help automating EleAPIs with Make?

A person reads every message.

FAQ

Questions about EleAPIs and Make

01Is the EleAPIs Make integration free?
Yes, EleAPIs is a standard app, so you can use it on the Free plan of Make. That 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 lower the interval to 1 minute and remove the cap on active scenarios. Make counts operations, one module running on one bundle, against your monthly credits. What EleAPIs itself charges is a separate question to ask EleAPIs.
02What do you need to connect EleAPIs to Make?
An EleAPIs account and a Make account are enough to begin, since the documentation lists no other prerequisite. You add any EleAPIs module, click Create a connection, give it a name if you like, then authorize Make on the EleAPIs page or paste the key EleAPIs provides, and click Save. The connection is then reused by every EleAPIs module in your scenarios. Because the official documentation for this app is limited, ask EleAPIs support if the authorization step asks for something you do not have.
03Do the EleAPIs triggers in Make fire in real time?
No, as far as the listing shows. The three EleAPIs triggers are typed as scheduled from their Watch names, since the documentation does not label them; the clock badge on the module confirms it. Make checks the app on the scenario's schedule and picks up the new contacts, messages or WhatsApp orders created since the previous check. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest interval; paid plans can go down to 1 minute. None of the three is an instant trigger, the kind an app calls through a webhook as soon as something happens, so plan for that short wait.
04What if an EleAPIs module is missing in Make?
Use Make an API Call. It reaches any endpoint of the EleAPIs API with the connection you already have, so you are not limited to the 8 listed modules. You will need the EleAPIs API reference to write the request, because Make's documentation for this app is marked as limited and does not describe fields or endpoints. For the same reason, test each module with Run once and read the bundles it returns before you build the rest of the scenario on top of them.
05Make or n8n for EleAPIs?
It depends on the tool your team already uses and on what each one offers for EleAPIs. On Make, you get 8 ready modules, 3 scheduled triggers and 5 actions, plus Make an API Call for anything they miss, and the app is available on the Free plan. EleAPIs may also have an n8n node, so check its page before you decide. Compare the modules you actually need on each side rather than general reputation, and read the comparison linked higher on this page.
Same platform

Other docs you might need on this stack.

Browse all integrations