Resources · Make integration

Sendy Make integrationAutomate Sendy with Make.

Your Sendy lists can fill and clean themselves. The Sendy Make integration gives you 6 action modules: add, check, unsubscribe or delete a subscriber, count a list, create a campaign. This guide connects your install and walks you through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sendy Make integration do for you?

The Sendy Make integration links your own Sendy installation to Make, a no-code tool where you build a scenario (the automation itself, a chain of bricks called modules). Other apps send people or data in, and Sendy updates your lists or prepares a campaign without you copying anything by hand.

Signups that land in the right list. A shop, a form or a CRM runs the first module, then Add Subscriber puts the new person in your Sendy list. No more CSV exports between tools.

Clean opt-outs everywhere. When someone cancels an account in another tool, Unsubscribe User takes them off the matching list, and Get Subscriber Status tells you where a contact stands before you act.

A campaign drafted from your data. Create Campaign builds a campaign from content held elsewhere, and can send it too. Get Active Subscriber Count gives you the size of a list to log in a report.

What it will not do: Sendy has no trigger in Make, so nothing starts on its own from Sendy. The scenario always opens on another app or on a schedule. There is also no generic API call module, so the six modules are the full toolbox. If you already work in n8n, the Sendy n8n integration covers the same app, and n8n vs Make helps you pick. New to the editor? The Make training starts from zero.

Connect

How do you connect Sendy to Make?

  1. 01

    Grab your Sendy credentials

    Sendy is installed on your own server, so Make needs to know where it lives. Open the settings section of your Sendy installation and copy two things: the Host URL and the API key. Keep them in a note for the next step.

  2. 02

    Add a Sendy module in Make

    In your scenario, add any Sendy module and click Create a connection. The connection is your Sendy install linked to Make once, then reused by all six modules. You can type a label in Connection name if you run several installs.

  3. 03

    Paste and save

    Paste the Host URL and the API key you copied from Sendy, or follow the on-screen instructions, then save. Make now lists what it can read from your install, such as your lists, when you fill a module.

First scenario

Your first scenario: send new signups to a Sendy list

GoalWhen someone signs up in another app, Make adds them to your Sendy list with Add Subscriber.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. That first module is the app where signups happen: your form tool, your shop or your CRM.

  2. 02

    Set up the starting app

    Pick that app's module for a new signup and connect its account. Each person it finds becomes a bundle, one item that flows to the next module with the details you will pass to Sendy.

  3. 03

    Add the Sendy step

    Click the + on the right, search for Sendy and choose Add Subscriber. Connect your install, pick the list, then map the contact details coming from the first module.

  4. 04

    Test with Run once

    Click Run once and create a test signup. Open the bubbles above each module to read the bundles they received, then check that the address now shows in your Sendy list.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. Each run of each module on a bundle counts as one operation on your Make plan.

Modules

The 6 Sendy modules, and when to pick each one

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

Sendy1

Add Subscriber

Action

In MakeAdds a new subscriber to a list.

This one drops a person into a Sendy list, with the details you map from an earlier module. It is the backbone of most Sendy scenarios, since it turns a signup elsewhere into a real contact you can mail.

When to use it
a checkout, a webinar registration or a lead form that should feed a newsletter list.
Watch out
pick the list carefully in the module, because the contact only joins the list you choose there.
Sendy2

Create Campaign

Action

In MakeCreates a campaign (with an option to send it too).

Here Make builds a Sendy campaign for you, and it can also send it straight away if you turn that option on. Handy when the content already lives in another tool, like a blog, a sheet or a product feed.

When to use it
a new article is published and you want a ready campaign waiting in Sendy.
Watch out
test with sending off first, since a sent campaign reaches real inboxes.
Sendy3

Delete Subscriber

Action

In MakeDeletes a subscriber off a list (only supported in Sendy version 2.1.1.4 and above).

Takes a subscriber out of a list for good. Reach for it when you are cleaning a list, not when someone simply asks to stop receiving emails: that is the job of Unsubscribe User.

When to use it
you clear test addresses or duplicates out of a list.
Watch out
it only works on Sendy 2.1.1.4 and later, and a deletion cannot be undone from Make, so run it once on a test address first.
Sendy4

Get Active Subscriber Count

Action

In MakeGets the total active subscriber count of a list.

Returns a single figure: how many active subscribers a list holds right now. It changes nothing in Sendy, so it is safe to drop anywhere in a scenario to read a number and send it on.

When to use it
writing the size of each list into a spreadsheet or a team chat whenever a report scenario runs.
Watch out
it counts active subscribers only, so do not report it as the full size of the list.
Sendy5

Get Subscriber Status

Action

In MakeGets the current status of a subscriber.

Looks up one subscriber and tells you where they currently stand in a list. Nothing gets written, you only read, which makes it the safe first step before any change to a contact.

When to use it
before re-adding someone, to check whether they chose to leave that list earlier.
Watch out
the answer is only useful if a later step reads it, so map the status into the next module rather than leaving it unused.
Sendy6

Unsubscribe User

Action

In MakeUnsubscribes a user from a list.

Takes a person off a list at their request, the everyday way to respect an opt-out coming from another tool. It is gentler than Delete Subscriber, since you are handling a preference, not cleaning the list.

When to use it
someone cancels their plan in your billing tool, or asks your support team to stop the newsletter.
Watch out
pick the right list in the module, since the opt-out applies to the list you select there.
Need help

Need help automating Sendy with Make?

A person reads every message.

FAQ

Sendy and Make: the questions that come next

01Is the Sendy Make integration free?
Yes, on the Make side. Sendy is a standard app, available from the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes and caps files at 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Your Sendy installation is a separate matter: you need your own active install and its API key.
02What does it take to connect Sendy to Make?
Two things from your own Sendy installation: the Host URL and the API key. Both sit on the settings page of your install, so copy them from there. In Make, add any Sendy module, click Create a connection, give it a name if you like, and paste both values. The same connection then serves all six modules, so you only do this once per install. Without an active Sendy installation and an API key, the connection cannot be created.
03Does a Sendy scenario start in real time?
Not from Sendy. The app has no trigger module in Make, only actions. A scenario therefore starts in one of two ways. Either another app opens it, for example a form or a shop reporting a new signup, then Sendy modules follow. Or you put the Sendy module first and let the schedule run it, every 15 minutes by default, 15 minutes at the shortest on the Free plan and 1 minute on paid plans. A webhook from Make can also start the scenario when another tool calls it.
04What if a Sendy action is missing in Make?
It depends on the action. The Sendy app in Make has six modules and no Make an API Call module, so you cannot reach other parts of Sendy through it. Check first whether one of the six covers the need once combined with another app, for example Get Subscriber Status feeding Add Subscriber. If the gap is real, another app in your scenario may hold the data or action you are after. Note that Make flags its Sendy documentation as AI-generated, so double-check details with Sendy.
05Make or n8n for Sendy: which one fits?
It depends on where your other automations already live. Sendy exists in both tools, and each has its own guide on this site. In Make, you get six action modules to add, check, unsubscribe or delete subscribers, count a list and create a campaign, with no Sendy trigger. If your forms, CRM and reports are already wired in Make, keeping Sendy there means one place to monitor. If your team already builds in n8n, look at the Sendy n8n page and compare the modules before choosing.