Resources · Make integration

SendX Make integrationAutomate SendX with Make.

Need new signups to land in SendX with the right tags, without copy and paste? The SendX Make integration gives you 5 modules: 1 instant trigger and 4 actions. This guide is for marketers who run SendX and want to link your account, then build and test a first scenario.

Try the SendX integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SendX Make integration do for your lists?

The SendX Make integration links your SendX account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules where each module is one brick, like a trigger or an action. Contacts and tags then move between SendX and your other apps on their own.

Every signup becomes a SendX contact. A form, a checkout or a booking tool sends the person to Create / Update a Contact, and your list stays current without imports.

Tags follow what people do. When someone buys, Add a Tag to a Contact marks them as a customer, and Remove a Tag from a Contact takes off the prospect label, so your campaigns talk to the right group.

SendX events reach your other tools. Universal Trigger starts a scenario as soon as SendX runs the entity you attached the webhook to, and the next module can write that data to a CRM or a sheet.

Keep the limits in mind: this app has no search module and no scheduled trigger, and Make flags its SendX documentation as AI-generated content to double-check against SendX. For anything the listed modules skip, Make an API Call reaches the SendX API directly. SendX may also exist as an n8n node; the n8n vs Make comparison lays out the criteria. To learn the editor step by step, see the Make training, and check Make pricing before you scale up.

Connect

How do you connect your SendX account to Make?

  1. 01

    Copy your Team ID and API key

    In your SendX dashboard, open Settings, then API and Webhooks. Copy the Team ID and the API key shown on that screen. You need an active SendX account for this page to be there.

  2. 02

    Open a SendX module in Make

    Add any SendX module to your scenario and click Create a connection. A connection is your SendX account linked to Make once, then reused by every SendX module. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Enter the Team ID and API key you copied, or follow the on-screen instructions, and confirm. Make then lists SendX data in the module fields, which tells you the link works.

First scenario

Your first scenario: new signup to tagged SendX contact

GoalWhen someone fills in a form in another app, Make creates or updates the contact in SendX and adds a tag.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the trigger of the app that collects your signups, such as your form tool, and connect it.

  2. 02

    Add Create / Update a Contact

    Click the + on the right of the first module, search SendX and choose Create / Update a Contact. Link your connection, then map the email and name from the form bundle, one item passed from module to module.

  3. 03

    Tag the contact

    Add Add a Tag to a Contact after it. Map the contact from the previous module and type the tag that tells you where the person came from, for example the name of the form.

  4. 04

    Test with Run once

    Click Run once, then submit a test entry in your form. Open each module to read the bundle it received, and check in SendX that the contact now carries the tag.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Switch the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan.

Triggers

What starts a SendX scenario

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

SendX1Universal Trigger

Universal Trigger

Instant trigger

In Make“Triggers when the entity to which you attached the webhook is executed.”

Universal Trigger gets your scenario going the moment SendX runs the entity you attached a webhook to, so what happens in SendX can reach your other tools without anyone copying it over. It is the only trigger this app offers, which makes it the entry point for any flow that starts in SendX.

How it fires
instant: SendX calls Make through a webhook as soon as it happens.
When to use it
a SendX event should push data into a CRM, a shared sheet or a team chat handled by the next module.
Watch out
click Create a webhook before Create a connection, and check in SendX which entity carries the webhook, since the Make doc does not list them.
Modules

What the SendX modules do

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

SendX1

Add a Tag to a Contact

Action

In Make“Adds a tag to a contact.”

Put a label on one SendX contact, so the person is sorted by what they just did somewhere else, like paying or registering. Your SendX lists then reflect real behavior instead of a manual update.

When to use it
an order is paid in your shop and the buyer should now be tagged as a customer in SendX.
Watch out
it acts on one contact per bundle, and each run counts as one operation on your Make plan.
SendX2

Create / Update a Contact

Action

In Make“Creates or updates a contact.”

Get every new lead into SendX from a single module: it creates the contact or updates it, so you do not build one path for new people and another for known ones.

When to use it
right after a form, a checkout or a webinar signup, as the step that feeds your SendX list.
Watch out
the doc does not say which field decides between create and update, so test with Run once on a contact you already have.
SendX3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reach any endpoint of the SendX API from your scenario, with the connection you already set up, whenever the ready-made modules stop short of what you need.

When to use it
you need a SendX feature that has no module of its own in Make, and the other three actions cannot cover it.
Watch out
you write the request yourself from the SendX API documentation, and Make warns its SendX doc is AI-generated, so verify each detail with SendX.
SendX4

Remove a Tag from a Contact

Action

In Make“Removes a tag from a contact.”

Take a label off one SendX contact, so the tags on that person keep matching where they stand today rather than where they stood when they joined.

When to use it
a trial user becomes a paying customer, and the trial tag has to go while Add a Tag to a Contact sets the new one.
Watch out
map the exact tag name you want gone; this action changes one contact per bundle and uses one operation each time.
Need help

Need help automating SendX with Make?

A person reads every message.

FAQ

SendX and Make: common questions

01Is the SendX Make integration free?
Yes, on the Make side. SendX is a standard app, available from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans drop the minimum interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. You still need an active SendX account with its own subscription, which Make does not cover.
02What do you need to connect SendX to Make?
An active SendX account and its API credentials. In SendX, open Settings, then API and Webhooks, and copy the Team ID and the API key shown there. In Make, add a SendX module, click Create a connection, optionally give it a name, and paste what you copied. If you start with Universal Trigger, the order is different: click Create a webhook first, then Create a connection. The same connection then serves every SendX module in your scenarios.
03Does the SendX trigger react in real time?
Yes. Universal Trigger is an instant trigger: SendX calls Make through a webhook as soon as the entity you attached it to is executed, so the scenario does not wait for a scheduled check. It is the only trigger SendX has in Make; the other 4 modules are actions. If your flow starts in another app instead, that app's trigger sets the pace, with a default schedule of 15 minutes on a new scenario.
04What if the SendX module you need is missing?
Use Make an API Call. It sends any request to the SendX API with the connection you already have, which covers what the tag and contact modules leave out. You build the request from the SendX API documentation. Also note that Make labels its SendX doc as AI-generated content that may contain mistakes, so confirm important details with SendX. SendX has no search module in Make, so an API call is also the route when you need to look contacts up.
05Should you use Make or n8n for SendX?
It depends on which tool you already run. In Make, SendX comes with 5 modules, including an instant trigger and a way to call the whole SendX API, and it works from the Free plan. SendX may also exist as an n8n node, so compare the actions each side offers for your exact case before you decide. Neither choice changes what SendX itself can do; the difference sits in the editor and the plan you already use.
Same platform

Other docs you might need on this stack.

Browse all integrations