Resources · n8n integration

Sendy n8n integrationAutomate Sendy with n8n.

Can a self-hosted newsletter tool run inside an automated workflow? The Sendy n8n integration covers 6 operations across 2 resources, campaigns and subscribers, so signups, unsubscribes and list counts stop being manual work. Sendy ships no trigger, the node that starts a workflow, so a schedule does it.

Try the Sendy integration on n8n See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Sendy n8n integration actually cover?

Sendy runs on a server you host yourself, and the n8n node talks to its API from any workflow. Six operations, spread over two resources, Campaign and Subscriber: create a campaign, add someone to a list, count a list, read a status, unsubscribe, delete. Point n8n at your Sendy URL once, save the API key, and list management stops being an export-and-paste job.

Take a lead magnet. Someone fills a form, the row lands in Google Sheets, and a Schedule Trigger picks up the new rows every morning. The node runs subscriber.add with the Email and the List ID, and the person is subscribed before anyone opens a browser tab. Switch GDPR on when the signup comes from the EU.

Second one: the newsletter itself. A workflow gathers the week's articles, assembles the HTML, then campaign.create writes it into Sendy under a Brand ID. Leave Send Campaign off and what you get is a draft to proofread, while a message to Slack tells the editor it is waiting for a read.

Third: list hygiene. A request to stop receiving emails arrives in Gmail, the workflow reads the address, calls subscriber.status to see where it stands, then subscriber.remove to unsubscribe it. Nobody logs into Sendy, and the reply goes out in the same run.

The node stops at what it exposes: 6 operations, 2 resources. For anything else in the Sendy API, the HTTP Request node calls the endpoint directly and reuses the same credential through predefined authentication, so the key still lives in one place and you only build that one step by hand.

Two practical points before you start. There is no Sendy trigger, so every workflow begins elsewhere, most often a Schedule Trigger or an n8n Webhook, which is a URL another service calls to wake the workflow up. And List ID is not the list name: Sendy shows a hashed identifier under View all lists, and that is the value the node wants. For the wider picture on the platform itself, the n8n review and the n8n training go further than this page does.

Connect

How do you connect Sendy to n8n?

01
Grab the API key inside Sendy
Sendy has to be hosted somewhere before any of this works, so start from a running install. Open your user profile, go to Settings, and copy the value shown under Your API Key. That single key authenticates every call the node makes, which is why it belongs in a credential and never in a field of the workflow itself.
02
Create the Sendy credential in n8n
In n8n, open the Credentials menu and add a Sendy credential. It asks for two things: a URL, the URL of your Sendy application, meaning the address where your own install answers, and an API Key, the value you just copied. A credential is saved once and reused by every workflow in the instance, so this step happens a single time.
03
Select it on the node and run a test
Drop the Sendy node into a workflow. Its credential dropdown lists what you saved, so pick it, choose the Subscriber resource and the Count operation, paste a List ID, and run the node alone. A number coming back means the URL and the key are both correct. Nothing coming back points at the connection, not at the logic around it.

Actions

What can the Sendy node do?

The Sendy node exposes 6 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
Resource	Create	Delete	Add	Remove	Count	Status
Campaign	✓
Subscriber		✓	✓	✓	✓	✓

Campaign

1 operation

Create a campaign

campaign.create

What you see in n8n

Notes & use cases

Writes a campaign into Sendy and, if you ask for it, sends it instead of leaving a draft behind.

Key parameters

Brand ID: the only required field, the brand the campaign belongs to, often {{ $json.brandId }} when an earlier node supplies it.
Subject and HTML Text: the subject line and the HTML version of the email.
List IDs: which lists receive it, single or comma-separated, with Exclude List IDs in the same format for the ones to leave out.
Send Campaign: false by default, so the run creates a draft; set it to true to send as well.

Use cases

a weekly digest built by the workflow lands as a draft that an editor proofreads before anything goes out.

Subscriber

5 operations

Add a subscriber

subscriber.add

What you see in n8n

Notes & use cases

Puts an address on one list, which is the operation behind every automated signup.

Key parameters

Email: the address to subscribe, usually {{ $json.email }} from the form or row that triggered the run.
List ID: the list to subscribe to, the encrypted and hashed identifier found under View all lists in the column named ID.
Name and Country: the person's name and a two letter country code, useful when the campaign is segmented later.
GDPR: signs EU users up in a GDPR compliant manner; Silent bypasses double opt-in and treats the signup as single opt-in.

Use cases

a webinar registration adds the attendee to the follow-up list the moment the form is submitted.

Count a subscriber

subscriber.count

What you see in n8n

Notes & use cases

Returns how many subscribers a list currently holds, as a value the rest of the workflow can compare or store.

Key parameters

List ID: the list to count, that same encrypted and hashed identifier from View all lists. Point it at the wrong list and the number is still valid, just about something else.

Use cases

a Monday workflow reads the count, compares it with last week's value stored elsewhere, and posts the growth figure to the marketing channel. No parameters beyond the list, so it also works as a cheap connection test.

Delete a subscriber

subscriber.delete

What you see in n8n

Notes & use cases

Removes the subscriber record from a list entirely. The address is gone, not flagged, which makes this the operation for erasure requests.

Key parameters

Email: the address to delete, matched exactly as it was stored.
List ID: the list holding the record, since deletion applies to one list at a time.

Use cases

a privacy request comes in, the workflow deletes the record and logs the action, so the audit trail lives outside Sendy while the data itself does not.

Remove a subscriber

subscriber.remove

What you see in n8n

Notes & use cases

Unsubscribes someone from a list without erasing the record, exactly what an unsubscribe link does when a reader clicks it.

Key parameters

Email: the address to unsubscribe.
List ID: the list it should stop receiving. Other lists carry on, so a reader can leave the newsletter and keep the product updates.

Use cases

a support ticket asking to stop the emails is handled end to end, with the address unsubscribed and the requester answered in the same execution.

Get subscriber's status

subscriber.status

What you see in n8n

Notes & use cases

Reads back where an address stands on a list and returns the status, which gives the workflow something to branch on.

Key parameters

Email: the address to look up.
List ID: the list to check it against, because status is per list and not global.

Use cases

before adding a contact imported from a CRM, the workflow checks the status first and skips anyone already subscribed, which keeps a welcome sequence from firing twice at the same person.

Need help

Need help automating Sendy with n8n?

A person reads every message.

FAQ

Sendy and n8n: common questions

01Is the Sendy n8n integration free?

Yes on the n8n side. The Sendy node ships with n8n, so there is nothing to install and no extra cost, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves identically in both. What Sendy itself costs is a separate question, and this page does not answer it because the node documentation says nothing about pricing. In practice the integration adds no new bill of its own: you already host Sendy, and the node simply talks to it from workflows you were going to build anyway.

02What credentials does the Sendy node need?

An API key, plus the address of your install. The credential holds two fields: URL, the URL of your Sendy application, and API Key, which you find in your user profile under Settings and then Your API Key. There is no OAuth flow and no authentication selector on the node itself. Sendy has to be hosted before any of this is possible, so the install comes first and the credential second. Once saved in the Credentials menu, every Sendy node in every workflow picks it from a dropdown, which means the key gets typed once and never again.

03What are the limits of the Sendy node in n8n?

It covers 6 operations across 2 resources, Campaign and Subscriber, and that is the surface of the node. When what you need is not among those operations, the HTTP Request node calls the Sendy API endpoint directly and reuses the same credential through predefined authentication, so nothing is blocked, you just build that step by hand. The other thing worth planning for is identifiers. Fields like List ID and Brand ID expect the value Sendy assigns, not a human-readable name, and a required field left empty stops the node before it sends anything at all.

04Does Sendy have a trigger in n8n?

No. There is no Sendy trigger node, so a workflow touching Sendy has to start somewhere else, and three options cover almost every case. A Schedule Trigger runs the workflow at a fixed interval, which suits nightly syncs and weekly counts. An n8n Webhook gives you a URL that another service calls, so a form or your own app can push a signup the second it happens. Or another tool's trigger opens the chain and Sendy is simply the next node in it. Choose according to how fresh the data has to be when it reaches the list.

05n8n or Make for Sendy?

It depends on where you want the subscriber data to sit. Make is hosted by Make, with no self-hosting option, and it bills per operation, so a list you sync often costs more as it grows. n8n runs on Cloud or on a server you control, which pairs naturally with a tool you already host. Both give you a visual canvas and both do the job. The honest split: Make is faster to open and forget about, n8n costs less to run at volume and keeps addresses inside your own infrastructure, which is usually the reason people chose Sendy in the first place.

Grab the API key inside Sendy

Create the Sendy credential in n8n

Select it on the node and run a test

Need help automating Sendy with n8n?