Resources · Zapier integration

Maildroppa Zapier integrationAutomate Maildroppa with Zapier.

The Maildroppa Zapier integration gives you 7 triggers, 47 actions and 23 searches. Every trigger is instant, which is rare. That covers subscribers, tags, custom fields, segments, RSS newsletters and shop events, as long as you know what each step costs and where it trips.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Maildroppa Zapier integration is for

The Maildroppa Zapier integration lets your Maildroppa account talk to the rest of your tools through Zapier. You build a Zap (the automation you set up on Zapier: one trigger, then one or more actions), and it carries what happens on one side to the other, every time, with nobody copying lists by hand.

Three results show up quickly. A clean confirmed list elsewhere: Subscriber Confirmed fires when someone completes double opt-in, and the Zap writes them into the sheet or CRM your team reads. Tags that follow what happens in other tools: Assign Subscriber Tag (By Email) or Remove Subscriber Tag (By Email) keep Maildroppa tags in line with what another app records about the same person. Shop activity feeding automations: Report Cart, Report Order and Send Custom Event push events into Maildroppa so its own automations can react.

Here is the part the app page leaves out. Zapier does not design or send your campaigns: there is no action to write an email or start a one-off send, only RSS newsletters can be steered. Several actions are destructive, including one that deletes every subscriber of the account. And a few report steps return totals rather than people, so they are useful for dashboards, less for moving contacts.

Weighing the platform itself? Start with our Zapier review, then Make vs Zapier if you are still choosing between the two.

Vocabulary

Zapier vocabulary in one minute

Seven words carry the whole page. Here they are once, in plain terms.

Zap
The automation itself: one trigger at the top, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts the Zap, here something happening to a Maildroppa subscriber. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or moves something for you, such as tagging a subscriber.
Task
The unit Zapier bills: one action that completes successfully. Your plan's number is a count of those, nothing else.
Polling vs instant
Polling: Zapier asks the app for new items at a fixed interval. Instant: the app tells Zapier the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, such as a subscriber by email, so the following steps can use it.
Cost

What a Maildroppa Zap really costs

Maildroppa is not a premium app, so it works from the free plan. The bill follows actions, never the trigger.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • BilledEach successful action
  • Triggers7 instant, no waiting interval

The trigger costs nothing, and neither does Zapier waiting for it. Each action that succeeds counts as one task, so a three-action Zap uses three times more than a one-action Zap. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps. Add a filter, a search or a second action and the Zap turns multi-step, which needs a paid plan. The interval grid below is the general rule for polling triggers; it does not apply to Maildroppa, whose seven triggers are all instant.

Connect

Connect your Maildroppa account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Maildroppa account linked once, then reused by every step that needs it.

  2. 02

    Pick Maildroppa

    Type Maildroppa in the search box of the dialog, select it, then click Add connection. You need a Maildroppa account that already exists before you begin.

  3. 03

    Sign in and allow access

    A tab opens on Maildroppa. Sign in, then grant Zapier access. If the Zap will touch data you do not own yourself, make sure you have read or write access on it first.

First Zap

Your first Zap: log confirmed subscribers in a sheet

GoalEach time someone completes double opt-in and passes a condition you choose, a row lands in your spreadsheet, so the confirmed list lives where the team already works.

  1. 01

    Create the Zap

    Create a new Zap. The editor opens with an empty trigger slot at the top and an action slot underneath, ready to fill. Give it a name you will recognise.

  2. 02

    Set the trigger

    Pick Maildroppa, then Subscriber Confirmed, then your Maildroppa connection. The editor shows a lightning bolt, the sign of an instant trigger.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent confirmations of the account, so you map from a real subscriber. Pick one whose email you know.

  4. 04

    Add the filter and the sheet

    Click the plus icon, pick Filter and fill its three boxes: field, rule, value. Then add your spreadsheet's new-row action and map the email. The filter makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Test, then publish

    Test the action, open the sheet to check the row arrived, then click Publish to switch the Zap on. From then on, it runs on its own.

Triggers

Maildroppa triggers on Zapier

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

1

Subscriber Confirmed

Instant trigger

In Zapier“Triggers when a subscriber completes Maildroppa double opt-in.”

Starts the Zap once a person finishes Maildroppa's double opt-in, the moment they click to confirm their address. You get the subscriber's details back, ready to pass to the next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when only people who really confirmed should reach your CRM, your sheet or a welcome flow in another tool.
Watch out
the source ties this trigger to double opt-in only, and Create Subscriber (Direct Add) skips that step; test one direct add before you count on this Zap to see those people.
2

Subscriber Created

Instant trigger

In Zapier“Triggers when a subscriber is added to Maildroppa.”

Fires as soon as a new subscriber appears in your Maildroppa account. It is the broadest entry point, before any confirmation.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when every new address should be logged or tagged at once, confirmed or not, for example to keep a count of sign-ups in another tool.
Watch out
a Zap that writes new subscribers into Maildroppa from this trigger writes where it watches, and can set itself off again and again.
3

Subscriber Deleted

Instant trigger

In Zapier“Triggers when a subscriber is permanently deleted from Maildroppa.”

Reacts when a subscriber is removed for good from Maildroppa. The Zap hears about it at once, so you can clean up the same person elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a deletion in Maildroppa must be mirrored in your CRM or spreadsheet, so no tool keeps a contact the others have dropped.
Watch out
a Zap only hears about deletions made after it is published, never older ones.
4

Tag Added to Subscriber

Instant trigger

In Zapier“Triggers when a tag is assigned to a Maildroppa subscriber.”

Kicks off the Zap whenever a tag lands on a Maildroppa subscriber. You can then filter on the tag name to keep only the one you care about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a tag marks a stage in your process and another tool should hear about it straight away.
Watch out
without a filter, every tag on every subscriber starts the Zap and uses tasks.
5

Tag Removed From Subscriber

Instant trigger

In Zapier“Triggers when a tag is removed from a Maildroppa subscriber.”

The mirror of the previous one: the Zap starts when a tag is taken off a subscriber. It tells you that someone left a group, not that they joined it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when losing a tag should undo something elsewhere, like moving a deal back a stage or removing a person from a shared list.
Watch out
without a filter on the tag name, every removal of every tag starts the Zap.
6

Subscriber Unsubscribed

Instant trigger

In Zapier“Triggers when a subscriber becomes unsubscribed in Maildroppa.”

Goes off when a subscriber switches to unsubscribed in Maildroppa. The record stays in the account; only the status changes, and your Zap hears about it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when other tools that email people must respect the opt-out too, so your CRM or support desk stops contacting them.
Watch out
this is not a deletion; use Subscriber Deleted if you need to react to records that disappear.
7

Subscriber Updated

Instant trigger

In Zapier“Triggers when a subscriber profile changes in Maildroppa.”

Catches any change to a subscriber's profile in Maildroppa, such as a new first name, a field value or a status. It is the widest watch on existing contacts.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when your CRM should always hold the latest version of each contact, without a periodic export.
Watch out
any Maildroppa action in the same Zap that edits the subscriber can restart it, so add a filter or write to another tool only.
Actions

Maildroppa actions on Zapier

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

1

Activate RSS Newsletter

Action

In Zapier“Creates a feed baseline and activates the newsletter. Future issues follow its release policy.”

Takes a snapshot of the feed as a starting point and switches the RSS newsletter on; later issues follow its release policy.

When to use it
when a new feed goes live and its newsletter should start at the same moment.
Watch out
RSS Newsletter is required.
2

Add Tags to Selected Subscribers

Action

In Zapier“Adds tags for explicit subscriber IDs and returns changed and skipped counts.”

Applies tags to a whole list of subscriber identifiers in one go, then tells you how many changed and how many were skipped.

When to use it
after a search that returned several people, when tagging them one by one would multiply the steps.
Watch out
it works on identifiers, not emails.
3

Archive Field

Action

In Zapier“Archives a custom subscriber field.”

Puts a custom subscriber field out of use without deleting it.

When to use it
when a field no longer serves but you may need its history later.
Watch out
Field is required; to bring it back, use Restore Field.
4

Archive RSS Newsletter

Action

In Zapier“Archives the newsletter and stops polling.”

Retires an RSS newsletter and stops reading its feed. Keep it for a feed that is finished; for a short break, Pause RSS Newsletter is enough.

When to use it
when a feed stops for good.
Watch out
RSS Newsletter is required; Restore RSS Newsletter can bring it back later.
5

Archive Tag

Action

In Zapier“Archives an active customer tag. Existing subscriber assignments remain.”

Retires an active tag so it stops being offered, while the subscribers who already carry it keep it.

When to use it
at the end of an event or a promotion, to tidy the tag list.
Watch out
Tag to Archive is required, and archiving does not untag anyone.
6

Assign Subscriber Tag (By Email)

Action

In Zapier“Assigns a tag to a subscriber using the email. If the subscriber already has this tag, nothing changes.”

Puts a tag on one subscriber, found through their email address. If the tag is already there, nothing changes.

When to use it
when the other tool knows the email but not Maildroppa's internal ID, which is the usual case with forms and shops.
Watch out
Subscriber Email is required, so map it from the trigger.
7

Assign Subscriber Tag (By Subscriber ID)

Action

In Zapier“Assigns a tag to a subscriber using the subscriber ID. If the subscriber already has this tag, nothing changes.”

Same result as the email version, but it targets the subscriber by Maildroppa's own identifier.

When to use it
after a Maildroppa trigger or a Find Subscriber by Email search, which already hand you that identifier.
Watch out
Subscriber ID is required; an email typed in that box will not match anyone.
8

Cancel RSS Issue

Action

In Zapier“Cancels the draft issue; its feed items stay consumed.”

Drops a draft issue before it is sent.

When to use it
when a post is pulled from the site and its issue should not go out.
Watch out
the feed items in that draft stay marked as used, so they will not reappear in the next issue; RSS Newsletter and RSS Issue are required.
9

Check RSS Newsletter Now

Action

In Zapier“Fetches the feed now; active newsletter rules can create or release an issue.”

Makes Maildroppa read the feed right away instead of waiting; the newsletter's rules may then create or release an issue.

When to use it
right after publishing a post, so the newsletter picks it up without delay.
Watch out
RSS Newsletter is required, and the check can send an issue if the rules allow it.
10

Clear Subscriber Field (By Email)

Action

In Zapier“Clears one custom field value using the subscriber email.”

Empties one custom field for a subscriber matched on their email. The field stays in your catalog; only this person's value goes.

When to use it
when a piece of data stops being true and should no longer drive segments.
Watch out
Subscriber Email and Custom Field are both required.
11

Clear Subscriber Field (By Subscriber ID)

Action

In Zapier“Clears one custom field value using the subscriber UUID.”

Blanks a single custom field value on a subscriber targeted by ID.

When to use it
in a Zap fed by a Maildroppa trigger, to reset a field once a step is done.
Watch out
Subscriber ID and Custom Field are required; the field itself stays in the catalog.
12

Create Field

Action

In Zapier“Creates a subscriber field.”

Sets up a new custom subscriber field, with its label and type, and can hide it from profiles and sign-up forms.

When to use it
when you start tracking a new piece of data and want the field ready before values arrive.
Watch out
Label and Field Type are required; a hidden field can still show up in emails if you insert it there.
13

Create Segment

Action

In Zapier“Create a segment with current AND condition groups joined by OR.”

Builds a saved segment from condition groups: conditions inside a group must all match, and any one group is enough.

When to use it
when a launch or a campaign in another tool needs a matching audience in Maildroppa.
Watch out
Segment Name and the way you define the filter are both required.
14

Create Subscriber (Direct Add)

Action

In Zapier“Creates a subscriber immediately without double opt-in. Maildroppa applies the account direct-add quota.”

Adds a person to Maildroppa straight away, with no confirmation email in between.

When to use it
when consent was already collected elsewhere, for instance at checkout, and asking again would be redundant.
Watch out
Topic Selection, Email and Status are required, and Maildroppa counts these adds against the account's direct-add quota.
15

Create Tag

Action

In Zapier“Creates a new tag.”

Adds a brand-new tag to your account, named by hand or from an earlier step.

When to use it
when a new product or event in another tool should get its own tag before subscribers are sorted into it.
Watch out
the Name field is required, and creating a tag does not assign it to anyone.
16

Delete Segment

Action

In Zapier“Deletes a segment by ID.”

Removes a saved segment by its identifier. The audience definition disappears from your list of segments. Get Segment by ID lets you check which segment an identifier points to before you remove it.

When to use it
when a campaign ends and its audience no longer needs to exist.
Watch out
Segment is required.
17

Delete All Subscribers (Optionally by Status)

Action

In Zapier“Starts an async deletion of all subscribers, optionally filtered by status.”

Launches the deletion of every subscriber in the account, or only those with a given status, and runs in the background.

When to use it
rarely, to wipe a test account or purge one status entirely.
Watch out
it is the most destructive step on this page; test it on a test account first.
18

Delete Subscribers (Bulk)

Action

In Zapier“Deletes multiple subscribers by ID.”

Erases several subscribers at once from a list of identifiers.

When to use it
after a filtered list search, to purge a batch of contacts that meet a condition.
Watch out
it works on identifiers only, so a search usually comes first.
19

Delete Subscriber by Email

Action

In Zapier“Deletes a single subscriber using the email address.”

Removes one subscriber, chosen by email from a list or typed in.

When to use it
when a removal request is recorded in another tool and must be applied in Maildroppa.
Watch out
the way you select the subscriber is required: from the list or typed by hand.
20

Delete Subscriber by ID

Action

In Zapier“Deletes a single subscriber by ID. Pick from a list or paste an ID.”

Deletes a single subscriber, picked from a list or targeted by pasted identifier. Pick it when the identifier is already in hand; Delete Subscriber by Email covers the case where only the address is known.

When to use it
after a search that already returned the right identifier.
Watch out
choosing how to select the subscriber is required.
21

Get Form Totals

Action

In Zapier“Returns all-time signup form totals and conversion rates.”

Returns the all-time totals and conversion rates of your sign-up forms.

When to use it
to feed a reporting sheet with the overall performance of your forms.
Watch out
the figures cover all time, not a period; for a date range, use the Get Form Report search.
22

Get RSS Attention Items

Action

In Zapier“Lists newsletters with an issue awaiting review or a retained feed failure.”

Lists the RSS newsletters that need you: an issue awaiting review or a feed failure still on record.

When to use it
as the first step of a reminder sent to whoever approves issues.
Watch out
it reads, it does not fix anything.
23

List Segment Subscriber Counts

Action

In Zapier“Returns current subscriber counts by segment ID.”

Gives the current number of subscribers in each segment.

When to use it
to track how your audiences grow in a dashboard outside Maildroppa.
Watch out
results come by segment identifier, so you may need List Segments to put names on them.
24

List Tag Subscriber Counts

Action

In Zapier“Returns current subscriber counts by tag ID.”

Returns how many subscribers carry each tag right now.

When to use it
to report on interests or stages that you track with tags.
Watch out
counts are keyed by tag identifier; pair it with List Tags for readable names.
25

Pause RSS Newsletter

Action

In Zapier“Pauses polling and new issues.”

Stops the feed checks and the creation of new issues until you resume. Resume RSS Newsletter switches it back on.

When to use it
during a break in publishing, or while a feed is being fixed.
Watch out
RSS Newsletter is required.
26

Release RSS Issue

Action

In Zapier“Releases an issue awaiting review for sending.”

Approves an issue waiting for review so it goes out. Pair it with List RSS Issues to find the right issue first.

When to use it
when the approval is recorded in another tool and should release the issue.
Watch out
RSS Newsletter and RSS Issue are both required.
27

Remove Subscriber Tag (By Email)

Action

In Zapier“Removes a tag from a subscriber using the subscriber email.”

Takes a tag off one subscriber, matched on their email.

When to use it
when a status changes in another tool and the matching tag should go.
Watch out
Subscriber Email is required, so map it from the trigger or an earlier step.
28

Remove Subscriber Tag (By Subscriber ID)

Action

In Zapier“Removes a tag from a subscriber using the subscriber ID.”

Strips a tag from a subscriber identified by Maildroppa's internal ID. The rest of the profile and the other tags stay as they were.

When to use it
inside a Zap that started from a Maildroppa trigger, where the identifier is already available to map.
Watch out
Subscriber ID is required.
29

Remove Tags From Selected Subscribers

Action

In Zapier“Removes tags for explicit subscriber IDs and returns changed and skipped counts.”

Removes tags from a batch of subscriber identifiers at once and returns the changed and skipped counts.

When to use it
to close a campaign phase and clear its tag from everyone a previous search returned.
Watch out
check the skipped count, it tells you who did not carry the tag in the first place.
30

Rename Tag

Action

In Zapier“Renames an active customer tag.”

Gives an active tag a new name without touching who carries it.

When to use it
when naming in your other tools changes and Maildroppa should follow.
Watch out
Tag to Rename and New Name are required; if no tag shows in the list, your account may not have any yet.
31

Replace Subscriber Field (By Email)

Action

In Zapier“Replaces one typed custom field value using the subscriber email.”

Writes a new value into one custom field of a subscriber, found by email.

When to use it
to store a value that another tool holds about the subscriber.
Watch out
Subscriber Email and Custom Field are required, and the value must match the field's type.
32

Replace Subscriber Field (By Subscriber ID)

Action

In Zapier“Replaces one typed custom field value using the subscriber UUID.”

Updates one typed custom field value for a subscriber identified by ID.

When to use it
right after a Maildroppa trigger, where the identifier is already in hand and no lookup is needed.
Watch out
Subscriber ID and Custom Field are required.
33

Replace Subscriber Profile

Action

In Zapier“Completely replaces first name, status, active custom field values, and tags without changing the email address.”

Overwrites the whole profile at once: first name, status, active custom field values and tags. The email address stays.

When to use it
when another tool is the reference and Maildroppa should be a faithful copy of it.
Watch out
anything you leave out is replaced too; Subscriber ID and Status are required.
34

Replace Subscriber Topics

Action

In Zapier“Replaces the complete active topic selection. Omitted topics are unsubscribed.”

Sets the full list of topics a subscriber follows; any topic missing from your list is unsubscribed.

When to use it
when another tool holds the person's topic choices.
Watch out
Subscriber ID is required, and Override Personal Opt-Outs should stay off unless you are explicitly allowed to resubscribe someone.
35

Report Cart

Action

In Zapier“Reports a cart event and returns the ingestion and automation decisions.”

Sends a cart event to Maildroppa and gets back what it decided to record and trigger.

When to use it
when your shop is not linked directly and abandoned-cart automations still need the data.
Watch out
keep the Stable Source Event ID unchanged on retries, and never generate a new one for the same cart event.
36

Report Order

Action

In Zapier“Reports an order to an enabled API source. Currently restricted to the shop review account.”

Passes an order to an enabled source in Maildroppa, with its status and dates.

When to use it
when post-purchase flows depend on orders placed in a shop Maildroppa does not read on its own.
Watch out
it is currently restricted to the shop review account, so check that yours qualifies before building on it.
37

Request Double Opt-In

Action

In Zapier“Records a signup attempt and queues confirmation mail. Subscriber profile data is applied only after confirmation.”

Logs a sign-up and sends the person a confirmation email; their profile data only applies once they confirm.

When to use it
when the address comes from a form outside Maildroppa and you want the same consent proof as a native sign-up.
Watch out
Topic Selection and Email are required; pair it with Subscriber Confirmed to react to the confirmation.
38

Restore Field

Action

In Zapier“Restores an archived custom subscriber field.”

Reactivates a custom field that was archived earlier.

When to use it
when a piece of data you stopped tracking is needed again.
Watch out
Archived Field is required; pick it or map its current identifier from a previous step.
39

Restore RSS Newsletter

Action

In Zapier“Restores an archived newsletter as paused. Does not start sending.”

Pulls an archived RSS newsletter out of the archive and leaves it paused.

When to use it
when an old feed comes back to life and you want its settings again.
Watch out
it does not start sending; follow it with Resume RSS Newsletter.
40

Restore Tag

Action

In Zapier“Restores an archived customer tag so it can be assigned again.”

Brings an archived tag back into use, so it can be assigned again.

When to use it
when a recurring event comes back and you prefer to reuse its old tag rather than create a duplicate.
Watch out
Archived Tag is required; pick it from the list or map its identifier.
41

Resume RSS Newsletter

Action

In Zapier“Resumes a paused newsletter. Rebaseline explicitly consumes pending items.”

Restarts a paused RSS newsletter.

When to use it
when publishing picks up again after a break.
Watch out
Consume Pending Feed Items is required: true throws away the items that piled up during the pause, false keeps them for the next issue.
42

Send Custom Event

Action

In Zapier“Records a customer event and optionally starts matching automations.”

Records an event for a subscriber in Maildroppa and, if you wish, starts the automations waiting for it.

When to use it
when something recorded in another tool should launch a Maildroppa automation you already built.
Watch out
Event Key must match the automation's trigger and use 1 to 100 letters, digits, dots, underscores or hyphens; Subscriber Email is required.
43

Update Field

Action

In Zapier“Updates the editable properties of a subscriber field.”

Edits the settings of an existing custom field, without creating a new one.

When to use it
when the way you describe a piece of data changes and the field should reflect it.
Watch out
Field is required, and only the editable properties can change.
44

Update Segment

Action

In Zapier“Update a segment’s name and/or filter expression.”

Changes the name of an existing segment, its filter, or both.

When to use it
when the audience definition moves with a campaign and you would rather adjust the segment than build a new one.
Watch out
Segment is required.
45

Update Subscriber Email

Action

In Zapier“Changes only the email address of a subscriber.”

Changes only the email address of a subscriber, leaving the rest of the profile as it is.

When to use it
when a customer updates their address in your shop or CRM and Maildroppa must keep up.
Watch out
Subscriber ID and New Email Address are required, and the new address must be valid and unique.
46

Update Subscriber First Name

Action

In Zapier“Changes or removes only the first name of one subscriber.”

Edits or clears the first name of a single subscriber and nothing else.

When to use it
when your CRM holds a better spelling and personalised emails should use it.
Watch out
Subscriber ID is required; inside a Zap started by Subscriber Updated, this step can restart the same Zap.
47

Update Subscriber Status

Action

In Zapier“Changes only the status of one subscriber.”

Switches one subscriber's status without editing their other data. Name, fields, tags and topics are left untouched.

When to use it
when an opt-out recorded in another tool should also apply in Maildroppa.
Watch out
Subscriber ID and Status are both required.
Searches

Maildroppa searches on Zapier

23 search steps look for data that already exists in Maildroppa, so a later step can use it.

Maildroppa offers 23 search steps. In the action list they sit at the bottom, under SEARCH. Each one counts as a step, so a Zap that uses one is multi-step and needs a paid plan. Three settings decide what happens when a search does not return exactly one result.

1

Count Subscribers (Filtered)

Search

In Zapier“Build a filter (or paste JSON) and return how many subscribers match.”

Builds a filter from conditions and tells you how many subscribers match it.

When to use it
to check the size of an audience before a send, or to report on a group without listing it.
Watch out
defining the filter is required, in simple mode with rows or in advanced mode.
2

Count Subscribers

Search

In Zapier“Returns the total number of subscribers, optionally filtered by status.”

Returns the total number of subscribers, optionally narrowed to one status. You get a single number back, ready to drop into a report.

When to use it
as a quick headcount for a dashboard or a growth report.
Watch out
no conditions beyond status; for anything finer, use the filtered version.
3

Find Subscriber by Email

Search

In Zapier“Finds an exact subscriber overview by current top-level email.”

Looks up one subscriber from their current email and hands back their overview, including the identifier.

When to use it
before any action that needs a Subscriber ID, when the other tool only knows the email.
Watch out
Email is required and the match is exact.
4

Get Form Report

Search

In Zapier“Returns signup form views and confirmations by period.”

Pulls the views and confirmations of your sign-up forms for a date range.

When to use it
to compare form performance from one period to the next in a report.
Watch out
From Date and To Date are both required and both included in the range.
5

Get RSS Newsletter

Search

In Zapier“Returns the current configuration and status of one RSS newsletter.”

Reads the current settings and status of one RSS newsletter. Later steps can then read that status and decide what to do.

When to use it
before an action on that newsletter, to check whether it is active, paused or archived.
Watch out
RSS Newsletter is required.
6

Get Segment by ID

Search

In Zapier“Fetches a segment by ID.”

Fetches a single segment from its identifier. Its name and conditions become available to the following steps.

When to use it
when an earlier step handed you a segment identifier and you need its name or definition.
Watch out
it needs the identifier, not the segment name.
7

Get Subscriber Activity

Search

In Zapier“Returns activity summary and a cursor page. Provider-event details are not exposed to API keys.”

Returns a summary of a subscriber's activity and one page of detail.

When to use it
to bring engagement history into a CRM record or a support ticket.
Watch out
provider event details are not part of what Zapier receives.
8

Get Subscriber by ID

Search

In Zapier“Fetches the current detailed subscriber DTO by UUID.”

Retrieves the full current record of one subscriber from their identifier. Every field of the profile is then available to map.

When to use it
after a trigger that only carries the identifier, when later steps need the complete profile.
Watch out
Subscriber ID is required.
9

Get Subscriber Field Values by Email

Search

In Zapier“Returns typed field values and option labels, preserving empty values.”

Reads a subscriber's custom field values, with their option labels, from their email. Empty values are kept.

When to use it
to copy those values into another tool that only knows the address.
Watch out
an empty field comes back empty, not missing, so plan your filters for it.
10

Get Subscriber Field Values by ID

Search

In Zapier“Returns typed field values and option labels, preserving empty values.”

Same reading of typed field values and option labels, this time from the subscriber identifier.

When to use it
in a Zap started by a Maildroppa trigger, where the identifier is already known.
Watch out
empty values are preserved, which can look like a failed lookup.
11

Get Subscriber Status Change Report

Search

In Zapier“Returns status transitions by period.”

Shows how subscribers moved between statuses over a period. You see the movements, not a snapshot of the list.

When to use it
to track how statuses change from one period to the next in a reporting tool.
Watch out
From Date and To Date are required, both included.
12

Get Subscriber Status Total Report

Search

In Zapier“Returns averaged status totals per period, not current contact counts.”

Gives averaged totals per status for each period of a range.

When to use it
for trend charts of your list's health over time.
Watch out
these are averages per period, not the current number of contacts; dates are required.
13

Get Subscriber Topics

Search

In Zapier“Returns topics, subscription state and personal opt-outs for a subscriber.”

Lists the topics of one subscriber with their subscription state and personal opt-outs. It shows both what the person follows and what they refused.

When to use it
before Replace Subscriber Topics, so you rebuild the list from what is already there.
Watch out
Subscriber ID is required.
14

List Fields

Search

In Zapier“Returns a page of the current subscriber field catalog.”

Returns one page of your subscriber field catalog, with options to hide built-in fields or keep only required ones.

When to use it
to document your fields or check one exists before writing to it.
Watch out
it returns a single page, not necessarily every field.
15

List Filtered Subscribers (Paged)

Search

In Zapier“Build a filter (or paste JSON) and return one page of matching subscribers as a single page object in an array.”

Applies a filter and returns one page of matching subscribers.

When to use it
to feed a bulk tag or bulk delete action with the people who meet a condition.
Watch out
defining the filter is required, and the result is a single page, so large audiences need several runs.
16

List RSS Checks

Search

In Zapier“Returns one page of RSS checks.”

Shows the history of feed reads for one RSS newsletter, one page at a time. Each run returns one page, so a long history takes several passes.

When to use it
to investigate why an issue did not appear when expected.
Watch out
RSS Newsletter is required.
17

List RSS Issues

Search

In Zapier“Returns one page of RSS issues.”

Gives one page of the issues an RSS newsletter has produced. Release RSS Issue and Cancel RSS Issue both need an issue chosen this way.

When to use it
to find the issue to release or cancel in a later step.
Watch out
RSS Newsletter is required, and only one page comes back.
18

List RSS Newsletters

Search

In Zapier“Lists active and paused newsletters, or only archived newsletters.”

Lists your active and paused RSS newsletters, or only the archived ones.

When to use it
as a first step when a Zap must act on every newsletter in turn.
Watch out
active and archived ones are not returned together.
19

List Segments (Paged)

Search

In Zapier“Returns a page of segments. The result is an array with exactly one page object.”

Lists your saved segments, one page per run, with their identifiers and names side by side.

When to use it
to put names on the identifiers returned by List Segment Subscriber Counts.
Watch out
a single page comes back, not the full list if you have many segments.
20

List Subscribers (Paged)

Search

In Zapier“Returns one current Maildroppa subscriber overview page.”

Brings back one page of subscriber overviews, without any filter.

When to use it
for a sample of the list, or a light export into a sheet.
Watch out
only one page per run; it is not a full export.
21

List Tags

Search

In Zapier“Returns active tags or the complete active and archived tag catalog.”

Returns your active tags, or the whole catalog including archived ones if you tick that option.

When to use it
to match tag names with the identifiers other steps return.
Watch out
archived tags only show with Include Archived Tags switched on.
22

List Topics

Search

In Zapier“Lists subscription topics and their enrollment state.”

Lists your subscription topics and their enrollment state.

When to use it
to check what another tool offers people against the topics Maildroppa holds.
Watch out
it describes topics, not who follows them; use Get Subscriber Topics for one person.
23

Preview Segment

Search

In Zapier“Returns matching, unknown and reachable counts, up to 25 contacts and purchase capture coverage.”

Tests a segment definition and returns matching, unknown and reachable counts, up to 25 contacts and the purchase capture coverage.

When to use it
before Create Segment, to check the audience is the right size.
Watch out
Filter Mode is required, and the sample stops at 25 contacts.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and the steps that relied on it are skipped. Switch it on and the Zap goes on without a result.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. None of Maildroppa's searches offers it, so pair a search with a create action and a filter instead.
  3. If multiple search results are found?
    Three choices when several items match: keep the first one, which is the default, stop the Zap, or pass them all on together.
When it breaks

When a Maildroppa Zap breaks

Zapier ties no help article to Maildroppa, so the traps below are the ones every Zap shares. With seven instant triggers and bulk actions, they show up fast.

Most surprises come from what a Zap does not do rather than from an error message. Keep these three in mind before you publish, and see Zapier troubleshooting when a run goes wrong.

  • Old subscribers are never picked up

    A Zap only reacts to what happens after you switch it on. Subscribers who confirmed or changed before that stay out; moving that backlog is a separate job.
  • A Zap that sets itself off

    A Zap that writes where its own trigger watches can restart itself. Subscriber Updated followed by a step that edits that same subscriber is the classic case, and it burns tasks.
  • A mass import gets held back

    After a bulk import or a bulk delete, a trigger can suddenly send a huge batch at once, and Zapier's flood protection may hold those runs back.
Need help

Need help automating Maildroppa with Zapier?

A person reads every message.

FAQ

Maildroppa and Zapier: frequent questions

01Is the Maildroppa Zapier integration free?
On the Zapier side, yes: Maildroppa is not a premium app, so it runs on the free plan. That plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. A filter, a search or a second action makes the Zap multi-step, and that needs a paid plan. Even on that plan, all seven Maildroppa triggers stay instant, so a two-step Zap reacts the moment a subscriber changes.
02How many tasks does a Maildroppa Zap use?
One task for each action that succeeds, nothing for the trigger. A Zap that tags every new subscriber costs one task per subscriber, and a three-action Zap costs three times more. Adding Find Subscriber by Email before the tag makes the Zap multi-step. Failed steps are not billed. The bulk actions are worth a look: tagging a whole batch with Add Tags to Selected Subscribers is a single action, where tagging people one by one costs one task each.
03Is Maildroppa on Zapier real time?
Yes, for all seven triggers. Each one is instant: Maildroppa tells Zapier the moment a subscriber is created, confirmed, updated, tagged, untagged, unsubscribed or deleted, and the Zap starts right away. The plan's checking interval, 15 minutes on Free, does not apply to them. That is the main advantage of this app on a free plan: the speed you get does not depend on what you pay. In the editor, a Zap built on one of them shows a lightning bolt.
04What does it take to connect Maildroppa to Zapier?
A Maildroppa account that already exists and a Zapier account. From the Apps page, click + Add connection, search for Maildroppa, sign in on the tab that opens and grant access. If the Zap must touch data you do not own, you also need read or write access on it. For Report Cart or Report Order, set up an enabled source in your Maildroppa shop connection first, since both ask for its Source ID.
05Can a Zap delete every Maildroppa subscriber by mistake?
It can, and that is why the step deserves care. Delete All Subscribers (Optionally by Status) starts the deletion of every subscriber in the account, or of a whole status if you set one. It runs in the background once launched. Before you publish a Zap that contains it, test it on a test account, add a filter in front of it, and never map its status option from data you do not control.
06What if the Maildroppa operation you need is not on Zapier?
Then the integration does not cover it. The most common gap is sending: there is no action to write or send a one-off campaign, only RSS newsletters can be steered. Often the answer is Send Custom Event, which starts a Maildroppa automation you have already built, so the email itself is set up inside Maildroppa. Otherwise, do the step by hand and automate what sits around it. That way the content stays where your team already edits it.
07Zapier, Make or n8n for Maildroppa?
There is no single winner, only criteria. Coverage: on Zapier, Maildroppa exposes 77 operations and all seven triggers are instant, so check whether Make or n8n covers the steps you actually need. Cost: Zapier bills each successful action and never the trigger, and the bulk tag actions treat a whole batch as one action. Free plan: two-step Zaps cost nothing, but any filter, search or second action needs a paid plan. Weigh those points against the size of your own list.