Resources · Zapier integration

MAILINGWORK Zapier integrationAutomate MAILINGWORK with Zapier.

The MAILINGWORK Zapier integration gives you 2 triggers, 4 actions and 1 search. Both triggers are instant, the app runs on the free plan, and this page shows what each operation does, what it costs and where it trips up.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MAILINGWORK Zapier integration does for you

The MAILINGWORK Zapier integration links your MAILINGWORK account to the other apps you use, through Zapier. A Zap (the automation you build on Zapier) starts on an event in one app and then does something for you in another, every time that event happens, with no copy and paste in between.

Three results people build first. A log of consent: every New Opt-In lands as a fresh row in a spreadsheet, so the people outside MAILINGWORK see who said yes without a login. A clean list fed from elsewhere: a form or a shop sends its contacts to Create a Subscriber, and nobody types them twice. A welcome that follows the signup: a Zap finds the person with Find a Subscriber and hands them to Send an Email with a mailing you already prepared.

What Zapier does not do here matters just as much. It only listens for two events, opt-ins and opt-outs: a sent mailing, an open or a click starts nothing. It has no step to delete a subscriber. And a Zap never goes back in time, so the contacts already in the account stay where they are until you move them some other way.

Still choosing the tool itself? Start with our Zapier review, then n8n vs Zapier. Then come back here to build your first Zap.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the whole page. Each is explained once here, then used as is.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it and does nothing before.
Action
What the Zap does once started: the step that writes, sends or updates something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app itself, the moment the event occurs.
Filter
A step that lets the Zap continue only when what arrived matches the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, so the steps after it can reuse what it found.
Connection
Your MAILINGWORK account linked to Zapier once, then reused by every step of every Zap that touches it.
Cost

What MAILINGWORK costs you in Zapier tasks

MAILINGWORK is not a premium app, so it works from the free plan. The bill is counted in tasks, and only actions that succeed count.

  • Free plan100 tasks per month, unlimited Zaps
  • Free plan limitTwo steps: one trigger, one action
  • Premium appNo, MAILINGWORK runs on the free plan
  • MAILINGWORK triggers2 instant, 0 polling

The trigger never costs a task, and an action that fails is not counted. Each successful action counts on its own: a Zap with three actions uses three times what a one-action Zap uses. The free plan stops at two steps, one trigger and one action. Add a filter, a search or a second action and you have a multi-step Zap, which needs a paid plan. The interval grid below is for polling triggers: it does not apply to the two MAILINGWORK triggers, which are instant.

Connect

Connect MAILINGWORK to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a MAILINGWORK account first, plus access to anything in it you do not own yourself but want the Zap to touch.

  2. 02

    Pick MAILINGWORK

    Type MAILINGWORK in the search box of the dialog, select it, then click Add connection. A new tab opens on the MAILINGWORK side, where the sign-in happens.

  3. 03

    Sign in and grant access

    Log in to MAILINGWORK in that tab and allow Zapier to use the account. The connection then appears on the Apps page, and every later Zap reuses it without asking again.

First Zap

Your first MAILINGWORK Zap

GoalEach new opt-in in MAILINGWORK adds a row to a spreadsheet, so the consent log stays current without anyone exporting it.

  1. 01

    Create the Zap

    Start a new Zap and choose MAILINGWORK as the app that starts it. Pick New Opt-In as the event, then select the connection you added earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent opt-ins of the account, so you map the next step on a real one rather than on a blank example.

  3. 03

    Add the spreadsheet action

    Add the action in your spreadsheet app, choose the sheet, then drag the opt-in details from MAILINGWORK into the columns you want filled.

  4. 04

    Test the action

    Run the action test once and open the sheet. If the row is there with the right values in the right columns, the mapping is done.

  5. 05

    Publish

    Click Publish to switch the Zap on. From then on, every new opt-in writes its own row, and only that row counts as a task.

Triggers

MAILINGWORK triggers

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

1

New Opt-In

Instant trigger

In Zapier“Triggers when a new opt-in is received.”

Starts your Zap each time someone gives consent in MAILINGWORK, and hands the opt-in details to the steps that follow so they can log it, notify a colleague or feed another tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a record of every new consent outside MAILINGWORK, kept current without exports.
Watch out
a Zap that writes back into MAILINGWORK where its own trigger listens can set itself off again and again.
2

New Opt-Out

Instant trigger

In Zapier“Triggers when a new opt-out is received.”

Reacts when a subscriber withdraws consent in MAILINGWORK. The Zap receives who left, which is what you need to stop contacting that person in the other tools that hold their address.

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 contact list lives outside MAILINGWORK too, and it must hear about each unsubscribe as soon as it happens.
Watch out
only opt-outs recorded after the Zap is published reach it, so older ones need a separate cleanup.
Actions

MAILINGWORK actions

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

1

Send an Email

Action

In Zapier“Sends an email by subscriber id and email id.”

Sends one of your MAILINGWORK emails to one subscriber. The Zap chooses the email and the recipient; the content stays the one you built in MAILINGWORK.

When to use it
an event outside MAILINGWORK should be followed by a specific mailing to that person.
Watch out
both Email and Subscriber are required fields.
2

Opt-In a Subscriber

Action

In Zapier“Create an opt-in for subscriber data.”

Records consent for a subscriber through one of the opt-in setups of your account, so the person enters MAILINGWORK the way your consent process expects.

When to use it
people sign up elsewhere and you want MAILINGWORK to handle the opt-in.
Watch out
the Opt-in Setup field is required and must already exist in the account.
3

Create a Subscriber

Action

In Zapier“Create a subscriber with fields and lists.”

Adds a new person to MAILINGWORK with their field values and the lists they belong to, straight from whatever the trigger brought in.

When to use it
contacts collected in another tool should end up in MAILINGWORK without being typed again.
4

Update a Subscriber

Action

In Zapier“Updates a subscriber by subscriber id.”

Changes the data of a subscriber who is already in MAILINGWORK. You point it at the person, then fill only the values that should change.

When to use it
a detail moves in another tool and MAILINGWORK should follow.
Watch out
the Subscriber field is required, so a Find a Subscriber step usually comes first.
Searches

MAILINGWORK search

1 search step looks for data that already exists in MAILINGWORK, so a later step can use it.

A search step finds a subscriber who already exists, so an update or a send can target them. It sits at the bottom of the action list in the editor, under SEARCH. Three settings decide what happens next.

1

Find a Subscriber

SearchFind or create

In Zapier“Find a Subscriber by field id and field value.”

Looks up a subscriber by one field and the value it should hold, then passes the match to the next step, which is how Update a Subscriber or Send an Email gets its recipient.

When to use it
the trigger brings an address or an identifier, and you need the matching MAILINGWORK subscriber.
Watch out
the editor also lists Find or Create Subscriber; it is this same search with the create box ticked, not a separate operation.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nobody stops the Zap there. Switched on, the Zap carries on without a subscriber.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: a missing subscriber is created, and the setting above no longer applies.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass every match to the next steps at once.
When it breaks

When the MAILINGWORK Zap breaks

Zapier links no help article to MAILINGWORK and no app-specific limit is documented, so the traps below are the ones every Zap can hit.

Most surprises come from what the Zap cannot see, or from a Zap that feeds itself. If a Zap still misbehaves, open our Zapier troubleshooting page next.

  • Existing subscribers are ignored

    A Zap only reacts to what happens after it is switched on. Opt-ins and opt-outs from before are never picked up; moving that backlog is a separate job.

  • A Zap that triggers itself

    Writing into the place your own trigger watches starts the Zap again, then again, and the task count drains fast. Keep each Zap's actions away from what its trigger listens to.

  • A bulk import held back

    When a trigger suddenly receives a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back instead of firing them all.

  • A search that finds nobody

    With default settings, Find a Subscriber stops the Zap when no one matches, and the update or email after it is skipped without costing a task.
Need help

Need help automating MAILINGWORK with Zapier?

A person reads every message.

FAQ

MAILINGWORK Zapier integration FAQ

01Is the MAILINGWORK Zapier integration free?
Yes, it works on the free Zapier plan, because MAILINGWORK is not a premium app. The free plan gives 100 tasks per month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. As soon as you add a filter, a search such as Find a Subscriber, or a second action, the Zap becomes multi-step and needs a paid plan. That is the limit people discover late, usually when they try to find a subscriber before updating them.
02How many tasks does a MAILINGWORK Zap use?
One task per action that completes successfully, and nothing for the trigger. A Zap that waits for New Opt-In and then runs one action uses one task per opt-in. A Zap with three actions uses three tasks for the same event. An action that fails is not counted. A few apps and actions take more than one task, so keep your monthly allowance in mind every time you add a step to a Zap.
03Is MAILINGWORK on Zapier real time?
Yes for both triggers. New Opt-In and New Opt-Out are instant: MAILINGWORK tells Zapier the moment the event happens, and the Zap starts right away whatever your plan. The polling intervals of the plans, 15 minutes on Free for example, only apply to polling triggers, and MAILINGWORK has none. In the editor, an instant trigger shows a lightning bolt, which is the quickest way to confirm it. No setting to change on your side.
04What do you need to connect MAILINGWORK to Zapier?
A MAILINGWORK account you can sign in to, and access to anything in it you do not own but want the Zap to use. In Zapier, open Apps, click + Add connection, search for MAILINGWORK, click Add connection, then sign in to MAILINGWORK in the tab that opens and grant access. The connection is stored once and every Zap reuses it, so there is nothing to repeat when you build the next one.
05What does Opt-In a Subscriber need before it works?
An opt-in setup that already exists in your MAILINGWORK account. The Opt-in Setup field is required, and the Zap can only point to a setup the account already holds; Zapier does not create one for you. So build the opt-in process in MAILINGWORK first, then come back to the Zap and choose it. Send an Email follows the same logic: its Email field is required, so the mailing has to be prepared in MAILINGWORK before any Zap can send it.
06What if the MAILINGWORK operation isn't in the list?
The editor offers exactly what this page lists: two triggers, four actions and one search. A delete step or a trigger on opens and clicks does not exist. Often a combination covers the need, for example Find a Subscriber followed by Update a Subscriber to change a person found through one of their fields. If no combination fits, the honest answer is that Zapier cannot do it with MAILINGWORK today, and another route has to be studied before you build anything.
07Zapier, Make or n8n for MAILINGWORK?
It depends on three criteria rather than on a winner. First, the ready connector: Zapier offers MAILINGWORK with the seven operations listed here, so check whether the other tool offers it before comparing anything else. Second, billing: Zapier counts one task per successful action, which is easy to forecast on simple Zaps. Third, how many steps your flows need, since the free Zapier plan stops at two. Weigh those three against your own flows before you pick.
Same platform

Other docs you might need on this stack.

Browse all integrations