Resources · Zapier integration

Enginemailer Zapier integrationAutomate Enginemailer with Zapier.

The Enginemailer Zapier integration gives you 16 triggers and 7 actions, no search step. Half of those triggers are instant, and every one of them watches your subscribers: new, tagged, updated, unsubscribed or deleted from your list.

See the 23 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Enginemailer Zapier integration actually does

It links your Enginemailer account to Zapier so that something happening to a subscriber starts an automation, and so that other tools can add, tag, email or remove subscribers without you opening Enginemailer. Everything here revolves around the subscriber: there is nothing about campaigns.

Three results people build first. A clean welcome path: New Subscriber - Webhook fires, Tag Subscriber to a Subcategory files the person where your onboarding sequence expects them. A hand-off when a sequence ends: Subscriber Completed Autoresponder - Webhook tells you someone received the last email of an autoresponder, so the next step (a personal email through Send Email, a new tag) happens without you checking reports. A tidy list: when a subscriber leaves, Untag Subscriber From Subcategory or Deactivate Subscriber keeps your segments honest.

The advice that matters most here: every event comes in two versions. The one ending in - Webhook is instant, the plain one is checked on a timer, every 15 minutes on the free plan. Unless you have a reason to cap how many records come back, pick the Webhook twin.

What Zapier does not do with Enginemailer: no action creates or sends a campaign, there is no search step in the editor (finding a subscriber is an ordinary action, Find Subscriber), and nothing that happened before you switch the Zap on gets picked up. If you want to see the same app on another platform, the Enginemailer Make integration page covers it, and Make vs Zapier puts the two side by side.

Vocabulary

Zapier in one minute

Eight words you will meet in the editor, in plain English. Once read, the rest of the page uses them without a reminder.

Zap
The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in Enginemailer that starts the Zap, such as a new subscriber. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that adds, tags, emails or removes a subscriber for you.
Task
The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer. It asks Enginemailer for recent items and keeps only the ones it has not seen yet.
Instant trigger
A trigger Enginemailer reports itself, calling Zapier the moment the event happens. Here, the names ending in - Webhook.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What it really costs you

Enginemailer is not a premium app on Zapier, so it works on the free plan. The bill is counted in tasks, and only actions make tasks.

  • Free plan100 tasks per month, unlimited Zaps
  • Zap length on FreeOne trigger, one action
  • Premium appNo, Enginemailer works on Free
  • Instant triggers8 of 16, no waiting on any plan

The trigger never costs a task, and neither does Zapier checking for new subscribers, however often it looks. Each action that succeeds counts once: a Zap that tags and then emails someone uses two tasks per subscriber. An action that fails is not counted. The free plan stops at two steps, one trigger and one action, so a filter or a second action pushes you onto a paid plan. The interval grid below only concerns polling triggers.

Connect

Connect Enginemailer to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps. A connection is your Enginemailer account linked once to Zapier, then reused by every Zap that touches it. You need an Enginemailer account before you start.

  2. 02

    Add the connection

    Click + Add connection, type Enginemailer in the search box of the dialog, pick it, then click Add connection. A new tab opens on the Enginemailer side.

  3. 03

    Sign in and grant access

    Sign in to Enginemailer in that tab and allow Zapier to use the account. If the subscribers you want to touch belong to someone else's account, you need read or write access to it first.

First Zap

Your first Zap: move people on when a sequence ends

GoalWhen someone receives the last email of an autoresponder, check they match your condition, then tag them into the subcategory of your next offer.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Enginemailer, then Subscriber Completed Autoresponder - Webhook. It is instant, so the follow-up starts as soon as the last email goes out, whatever your plan.

  2. 02

    Test the trigger

    Click Test. Zapier brings back the three most recent items from your account, so you map the next steps on a real subscriber rather than a made-up one.

  3. 03

    Add the filter

    From the plus icon, add Filter, then set the field to look at, the rule and the value. Remember: a text rule only works on text. The filter makes this a multi-step Zap, so a paid plan.

  4. 04

    Build: add the action

    Add Enginemailer's Tag Subscriber to a Subcategory. Map the Email field from the trigger and pick the subcategory of your next offer in Subcategories.

  5. 05

    Test, then Publish

    Test the action once and read what came back. When the tag lands on the right person, click Publish to switch the Zap on. From then on, each subscriber who finishes the sequence costs one task.

Triggers

The 16 Enginemailer triggers

16 events start a Zap when something happens in Enginemailer, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Subscriber Deleted

Polling trigger

In Zapier“Triggers when a subscriber is deleted.”

Spots subscribers that have been removed from your Enginemailer account and hands each one to the Zap, so your other records can follow the same clean-up.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you are on a paid plan, a short delay does not matter, and you want to control how many deletions come back per check, for instance during a list purge.
Watch out
the Limit field is mandatory and caps each check at 50 records at most.
2

Subscriber Deleted - Webhook

Instant trigger

In Zapier“Triggers instantly when a subscriber is deleted.”

The instant twin of the previous trigger: Enginemailer itself tells Zapier that a subscriber was deleted, with no timer in between.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a consultant who keeps a client list in a spreadsheet wants the matching row flagged the moment the contact disappears from the mailing tool.
Watch out
the Zap only sees deletions made after you publish it, so older removals stay invisible.
3

New Subscriber

Polling trigger

In Zapier“Triggers when a new subscriber is created.”

Catches every subscriber created in Enginemailer since the last check and starts the Zap once per person, never twice for the same one.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you import contacts in batches and prefer to receive them in controlled slices rather than all at once.
Watch out
Limit is required and goes up to 50; after a large import, Zapier's flood protection can still hold a huge batch back.
4

New Subscriber - Webhook

Instant trigger

In Zapier“Triggers instantly when a new subscriber is created.”

Enginemailer pings Zapier as soon as a subscriber is created, which makes this the natural starting point of a welcome flow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
someone signs up for your course waitlist and should be tagged into the right subcategory before your first sequence email even leaves.
Watch out
if the action adds subscribers back into the same account, test carefully so the Zap does not feed itself.
5

Subscriber Completed Autoresponder

Polling trigger

In Zapier“Triggers when a subscriber receives the last email in an autoresponder.”

Reports subscribers who have received the last email of an autoresponder, the moment a sequence is over for them.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a coach on a paid plan wants a list of graduates of the intro sequence, collected in slices, to review before any upsell goes out.
Watch out
fill the mandatory Limit field; it accepts up to 50 records per check.
6

Subscriber Completed Autoresponder - Webhook

Instant trigger

In Zapier“Triggers instantly when a subscriber receives the last email in an autoresponder.”

As soon as the final email of an autoresponder reaches a subscriber, Enginemailer passes that person straight to your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your onboarding sequence ends and you want the person moved into a sales subcategory with no gap, which is exactly the Zap drawn above.
Watch out
people who finished the sequence before you published the Zap are never sent to it.
7

Subscriber Triggered Autoresponder

Polling trigger

In Zapier“Triggers when a subscriber receives the first email in an autoresponder.”

Flags subscribers who have just received the first email of an autoresponder, in other words the people who entered a sequence.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you count who starts each sequence and a delay of a few minutes changes nothing to that tally.
Watch out
Limit must be filled, with 50 as the ceiling for each check.
8

Subscriber Triggered Autoresponder - Webhook

Instant trigger

In Zapier“Triggers instantly when a subscriber receives the first email in an autoresponder.”

The moment a subscriber gets the opening email of a sequence, Enginemailer notifies Zapier and your Zap takes over.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a webinar host wants a personal note sent through Send Email right after the first reminder of the series lands.
Watch out
sending another email on top of the sequence costs one task per subscriber, so count your volume against your plan.
9

Subscriber Tagged With a Subcategory

Polling trigger

In Zapier“Triggers when a subscriber is tagged with a subcategory.”

Returns subscribers who have been assigned to a subcategory, whoever or whatever did the tagging.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
your sales team tags qualified leads by hand during the day and only needs them gathered elsewhere at a steady pace.
Watch out
the Limit field is compulsory and stops at 50 records each time Zapier looks.
10

Subscriber Tagged With a Subcategory - Webhook

Instant trigger

In Zapier“Triggers instantly when a subscriber is tagged with a subcategory.”

Every time a subscriber lands in a subcategory, Enginemailer sends the event to Zapier on the spot.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a tag such as "demo requested" should set off an immediate reply, not one a quarter of an hour later.
Watch out
a Zap that tags the same subscriber again from this trigger can set itself off over and over.
11

Subscriber Unsubscribed

Polling trigger

In Zapier“Triggers when a subscriber unsubscribes.”

Lists the people who unsubscribed from your Enginemailer emails since Zapier last looked, one run per person.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you keep a record of opt-outs for reporting and receiving them a little later is fine.
Watch out
Limit is mandatory, up to 50 records per check.
12

Subscriber Unsubscribed - Webhook

Instant trigger

In Zapier“Triggers instantly when a subscriber unsubscribes.”

When someone opts out, Enginemailer tells Zapier immediately, which is the version to pick whenever consent is involved.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a SaaS founder wants the person pulled out of every subcategory used for product announcements before the next send.
Watch out
opt-outs that happened before the Zap went live are not replayed.
13

Subscriber Untagged From a Subcategory

Polling trigger

In Zapier“Triggers when a subscriber is untagged from a subcategory.”

Picks up subscribers removed from a subcategory, whoever or whatever did the untagging.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you clean subcategories in bulk and want the changes to arrive in measured batches.
Watch out
set the required Limit field; Enginemailer returns 50 records at most per check.
14

Subscriber Untagged From a Subcategory - Webhook

Instant trigger

In Zapier“Triggers instantly when a subscriber is untagged from a subcategory.”

Enginemailer reports each removal from a subcategory to Zapier as it happens.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a customer leaves the "trial" subcategory and should be tagged into "customers" right away with Tag Subscriber to a Subcategory.
Watch out
pairing this trigger with Untag Subscriber From Subcategory on the same subscriber is the classic way to build a loop.
15

Subscriber Fields Updated

Polling trigger

In Zapier“Triggers when a subscriber's fields have been updated.”

Collects subscribers whose fields changed in Enginemailer, so another tool can catch up with the new values.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you sync profile changes to an internal sheet and a slight lag is acceptable.
Watch out
the Limit field is required, up to 50; and never answer it with Add or Update Subscriber on the same person, or the update starts the Zap again.
16

Subscriber Fields Updated - Webhook

Instant trigger

In Zapier“Triggers instantly when a subscriber's fields are updated.”

Each edit to a subscriber's fields is pushed by Enginemailer to Zapier without waiting for a check.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a subscriber updates their details through a preference form and your support team should see the change at once.
Watch out
any action that writes back to that subscriber counts as a fresh update and can set the Zap off again.
Actions

The 7 Enginemailer actions

Enginemailer gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add or Update Subscriber

Action

In Zapier“Create a new subscriber or update the subscriber if the data exists.”

Creates the subscriber if the address is new, or updates the existing one if it is already in your account, so you never end up with duplicates.

When to use it
leads from your forms or your CRM should land in Enginemailer with their latest details.
Watch out
Email is mandatory, and the step that feeds it must carry a real address.
2

Delete Subscriber

Action

In Zapier“Permanently delete the subscriber”

Removes a subscriber from Enginemailer for good, according to the official description of the action.

When to use it
a data-erasure request has to be applied in every tool you run.
Watch out
only Email is required, so one wrong mapping deletes the wrong person; test on a dummy contact first.
3

Find Subscriber

Action

In Zapier“Search for an existing subscriber in your account”

Looks up a subscriber who already exists in your account from their address, so later steps can use what it found.

When to use it
before tagging or emailing, check that the person is really on your list.
Watch out
it sits among the actions, not in a search section, and Email is required.
4

Send Email

Action

In Zapier“Sends an email to the specified email address.”

Sends an email to the address you map from an earlier step.

When to use it
a personal confirmation after a booking or a purchase, triggered by an event in another tool.
Watch out
both Email and Content Type are required, and each email sent counts as one task.
5

Tag Subscriber to a Subcategory

Action

In Zapier“Assign a subscriber to a specific subcategory”

Assigns a subscriber to a specific subcategory of your account.

When to use it
a buyer of your course should join the "students" subcategory and leave the prospects' flow.
Watch out
Email and Subcategories are both required, so the step before has to supply both.
6

Deactivate Subscriber

Action

In Zapier“Set subscriber status to inactive”

Switches a subscriber's status to inactive. For permanent removal, Delete Subscriber is the one.

When to use it
a customer cancels in your billing tool and their record should be set to inactive.
Watch out
Email is mandatory, and the editor shows it as Deactivate Subscriber, not Unsubscribe.
7

Untag Subscriber From Subcategory

Action

In Zapier“Remove a subscriber from a specific subcategory.”

The reverse move: takes a subscriber out of a specific subcategory of your account, the one you name in the Subcategories field.

When to use it
a trial user converts and should stop receiving the trial reminders.
Watch out
Email and Subcategories are compulsory, exactly as for tagging.
When it breaks

When it breaks

Zapier attaches no help article to Enginemailer, so the traps below are the general ones of Zapier, applied to a subscriber list.

Four situations to know before you rely on this integration. If a Zap stops working for a reason not listed here, the Zapier troubleshooting page is the next stop.

  • Your existing list is not replayed

    A Zap reacts only to what happens after you publish it. Subscribers who signed up last month will never start it; moving them is a separate job.

  • The Zap that sets itself off

    Subscriber Fields Updated feeding Add or Update Subscriber on the same person is a loop: each write is a new update, and your task count drains fast.

  • Bulk imports get held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of running the Zap for each row.

  • The same subscriber, only once

    On polling triggers Zapier remembers what it has already seen, so a subscriber does not start the Zap twice. A filter waiting for a later change will never pass.
Need help

Need help automating Enginemailer with Zapier?

A person reads every message.

FAQ

Enginemailer Zapier integration: FAQ

01Is the Enginemailer Zapier integration free?
Yes, as long as your Zap stays at two steps. Enginemailer is not a premium app, so the free plan accepts it, with 100 tasks per month and unlimited Zaps. The catch is the length of the Zap: the free plan allows one trigger and one action, nothing more. As soon as you add a filter, a second action or Find Subscriber in front of a tag, the Zap becomes multi-step and needs a paid plan. On Free, polling triggers are also checked every 15 minutes, which is a good reason to prefer the Webhook versions.
02How many tasks does an Enginemailer Zap use?
One per successful action, per subscriber. The trigger itself costs nothing, and Zapier checking for new subscribers costs nothing either, however often it looks. A Zap that tags a subscriber and then sends them an email uses two tasks every time it runs. An action that fails is not counted against your plan. With 100 tasks on the free plan, those 100 tasks cover 100 runs of a one-action Zap, so estimate your sign-up volume before you rely on it.
03Is the Enginemailer integration real time?
Half of it. Eight of the 16 triggers are instant: their names end in - Webhook, and Enginemailer calls Zapier the moment the event happens, whatever your plan. The other eight are polling triggers, which Zapier checks on a timer: every 15 minutes on Free, 2 minutes on Professional, 1 minute on Team and Enterprise. The type is set by the app and cannot be changed in the editor. Every event exists in both versions, so you can almost always pick the instant one.
04What do you need to connect Enginemailer to Zapier?
An Enginemailer account, and access to the subscribers you want the Zap to touch. In Zapier you open Apps, click + Add connection, search for Enginemailer, click Add connection, then sign in to Enginemailer in the tab that opens and grant access. The connection is created once and reused by every Zap. If the list belongs to a colleague's or client's account, you need read or write access to it before connecting, otherwise your steps will not reach those subscribers.
05What does the Limit field on Enginemailer triggers do?
It caps how many records a polling trigger brings back per check, and it is mandatory. You will find it on the eight triggers without - Webhook in their name, and it accepts up to 50 records. The instant versions do not ask for it. If you expect bursts of activity, such as a bulk tag on hundreds of contacts, keep in mind that Zapier's flood protection can also hold back an unusually large batch.
06What if the Enginemailer trigger or action you need is not there?
Then Zapier cannot do it with this app today. The editor offers 16 triggers and 7 actions, all centred on subscribers: nothing creates or sends a campaign, and there is no search section. Two workarounds often help. A filter after an existing trigger narrows a broad event down to the case you care about. Find Subscriber, placed before another action, can check a person exists first. Both make the Zap multi-step, so a paid plan. Beyond that, compare what the other automation platforms offer for Enginemailer.
07Zapier, Make or n8n for Enginemailer?
It depends on three criteria rather than on a winner. First, the event: check that the platform exposes the exact trigger or action you want, since each one maintains its own list. Second, the length of your scenario: on Zapier, anything beyond one trigger and one action needs a paid plan. Third, the billing unit: Zapier counts each successful action as a task, so a long Zap multiplies the cost per subscriber. Compare those three points on your own use case before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations