Zagomail Make integrationAutomate Zagomail with Make.
Can your Zagomail list react on its own when people join, leave or get tagged? The Zagomail Make integration gives you 15 modules, including 4 instant triggers. This page is for marketers who run the list, and it walks you from the connection to a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Zagomail Make integration do for your list?
The Zagomail Make integration links your Zagomail account to Make, a no-code tool where you build a scenario: the automation itself, made of modules, where each module is one brick such as a trigger, an action or a search. Zagomail tells Make when a subscriber confirms, unsubscribes or gains or loses a tag, and Make can then tag, create or look up subscribers for you.
A welcome path that starts on confirmation. Watch Subscriber Confirmed fires as soon as a subscriber confirms, and Add a Tag marks that person so the right sequence picks them up. The tag becomes the switch for everything that follows.
Leads from other tools, straight into the list. A form or a CRM passes a new contact to Make, Get Subscriber By Email checks whether the address already exists, and Create a Subscriber adds it only when it does not. The same pattern works with the forms covered in the 123FormBuilder Make integration.
Clean exits that other systems respect. Watch Subscriber Unsubscribed tells Make when someone leaves, so your CRM or support tool can be updated too. In the other direction, Unsubscribe a Subscriber removes a contact from a list when a different system says they asked to stop.
Be aware of one limit: Make itself says its documentation for Zagomail is incomplete because little public information exists about the app. When a listed module does not cover your need, Make an API Call reaches the rest of the Zagomail API with the same connection. Zagomail may also exist as an n8n node; the n8n vs Make comparison lays out how the two tools differ, and the Make training covers scenario building from scratch.
How do you connect Zagomail to Make?
- 01
Add a Zagomail module
Inside a scenario, add any Zagomail module and click Create a connection. A connection is your Zagomail account linked to Make once, and every Zagomail module reuses it afterward.
- 02
Name it and authorize Make
Give the connection a name if you like, which helps when you manage several accounts. Then authorize Make on the Zagomail page that opens, or paste the key Zagomail gives you if the window asks for one.
- 03
Save and reuse
Click Save. The module can now read your Zagomail lists and tags, and the same connection appears in the dropdown of every other Zagomail module you add to this or any later scenario.
Your first scenario: tag every confirmed subscriber
GoalWhen a subscriber confirms in Zagomail, Make adds a tag to that subscriber.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.
- 02
Pick the trigger
Search for Zagomail, choose Watch Subscriber Confirmed and select your connection, or click Create a connection if this is your first Zagomail module.
- 03
Add the tag action
Click the + on the right of the trigger and add Add a Tag. Map the subscriber that the trigger passed along, then choose the tag you want applied.
- 04
Test with Run once
Click Run once, then confirm a test subscription in Zagomail. Open each module's bubble to read the bundle it received, meaning the single subscriber that flowed through.
- 05
Switch it on
Once the test looks right, switch the scenario on. Because this trigger is instant, the scenario runs whenever Zagomail sends a new confirmation, with no polling interval to set.
What can start a Zagomail scenario?
4 modules start a scenario when something happens in Zagomail. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Zagomail as soon as it happens.
Watch Subscriber Confirmed
Instant triggerIn Make“Event is triggered when subscriber new subscriber is confirmed”
This trigger starts your scenario as soon as a new subscriber finishes confirming, so you only act on people who really opted in. Each confirmation arrives in Make as one bundle, and every module after it works on that one person.
Watch Subscriber Unsubscribed
Instant triggerIn Make“Triggered when subscriber is unsubscribed”
Here the signal is a departure: the scenario runs when a subscriber leaves, which lets the rest of your stack hear about it instead of emailing someone who said no. The bundle carries the subscriber who just left.
Watch Tag Added
Instant triggerIn Make“Event is triggered when tag is added to subscriber”
If you use tags to mark what a subscriber cares about, this trigger turns each new tag into an event Make can act on. Whenever a subscriber receives a tag, your scenario gets that subscriber as a bundle.
Watch Tag Removed
Instant triggerIn Make“Event is triggered when a tag is removed from a subscriber”
The mirror of the previous trigger: your scenario wakes up when a tag disappears from a subscriber, which is useful when a tag stands for a status that has now ended. The subscriber concerned arrives as a single bundle.
What else can Make do in Zagomail?
Zagomail gives you 11 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Add a Tag
ActionIn Make“Adds a tag to subscriber”
Add a Tag puts a label on one subscriber, which is how you steer them into the right segment or sequence without touching Zagomail by hand.
Create a Subscriber
ActionIn Make“Creates new subscriber”
With Create a Subscriber, a contact captured anywhere else becomes a new entry in your Zagomail list, so leads stop waiting in exports.
Get Subscriber By Email
ActionIn Make“Returns details of the specified subscriber”
Give this module an email address and it returns the matching subscriber's details, which is the easiest way to know whether someone is already on your list.
Get Subscriber By UID
ActionIn Make“Returns details of the specified subscriber”
This lookup fetches one subscriber from the unique ID Zagomail assigns, so you land on the exact record without going through the address.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Make an API Call is the escape hatch: it lets you call any endpoint of the Zagomail API from the scenario while reusing your existing connection.
Remove a Tag
ActionIn Make“Remove tag from a subscriber”
Remove a Tag takes a label off a subscriber so they leave a segment or a sequence the moment their situation changes.
Unsubscribe a Subscriber
ActionIn Make“Unsubscribe Subscriber from list”
This action takes a subscriber out of a list, so a request to stop is honored even when it came through a channel other than Zagomail.
Get All Lists
SearchIn Make“Returns the list of all subscriber lists in account”
Get All Lists returns every subscriber list in your account, one bundle per list, so a scenario can loop through them or pick the right one.
Get All Subscribers from List
SearchIn Make“Returns the list of all subscribers from a specified subscriber list”
Point this search at one list and it hands back its subscribers, which is how you export or sync a whole audience into another tool.
Get All Tags
SearchIn Make“Returns the list of all tags in account”
This search lists every tag that exists in your Zagomail account, giving you the full vocabulary before you tag anyone.
Get Subscriber Tags
SearchIn Make“Returns the list of tags, of the specified subscriber”
Get Subscriber Tags shows which labels one subscriber carries, so the scenario can branch on what that person is already part of.
Need help automating Zagomail with Make?
A person reads every message.
