- Home
- Resources
- Integrations
- Mailsoftly
Mailsoftly Zapier integrationAutomate Mailsoftly with Zapier.
Mailsoftly Zapier integration: 6 triggers, 9 actions and 3 searches to keep your Mailsoftly contacts, lists and tags in step with the rest of your tools. React to a form reply or an unsubscribe, then tag, list or enrol people without manual exports.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mailsoftly Zapier integration does for you
Mailsoftly is an email marketing platform built for growing companies, nonprofits, schools and public teams. Linked to Zapier, its contacts, lists, tags, forms and campaigns become events that can start an automation, and Zapier can write back into Mailsoftly: add a contact, tag it, list it, or start one of your automations for it.
Form replies that sort themselves. New Form Response hands each submission to the Zap, and Add Tag to Contact labels the person by what they answered, so your next campaign can target them without a manual pass.
Contacts that follow you everywhere. Create or Update Contact keeps Mailsoftly in line with another tool, updating the record that already has the same email address instead of making a duplicate.
Unsubscribes that travel. New Unsubscribe tells your other tools at Zapier's next check, and Add to Suppression List or Unsubscribe Contact do the reverse when someone opts out elsewhere.
What it will not do: none of the six triggers is instant, so each one waits for Zapier's next check. Nothing here sends a campaign, deletes a contact or edits a form; Start Automation for Contact only enrols someone who already exists in an active automation. If you are still comparing tools, read n8n vs Zapier or Make vs Zapier before building.
Zapier vocabulary in plain words
Eight terms carry the whole page. One line each, then they are used as is.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that creates, sends or moves something for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts these and nothing else.
- Polling or instant
- A polling trigger is checked by Zapier on a timer; an instant one is reported by the app the moment it happens. Mailsoftly's are all polling.
- Filter
- A step that lets the Zap continue only when the incoming item meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something already in an app, so the following steps can use what it found.
- Connection
- Your Mailsoftly account linked to Zapier once, then offered in every step that uses Mailsoftly.
What a Mailsoftly Zap really costs
Zapier checking Mailsoftly for new contacts or replies never costs anything. You pay in tasks, one per action that succeeds.
- Trigger checksFree, never a task
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, available on the free plan
A Zap that tags a contact and then enrols it in an automation uses two tasks per run, and a failed action is not counted. Mailsoftly is not a premium app, so the free plan works, as long as the Zap stays at one trigger and one action. Add a filter, a search step such as Find Contact, or a second action, and the Zap becomes multi-step: that needs a paid plan. All six triggers are polling, so the interval grid applies to every one.
Connect Mailsoftly to Zapier in three steps
- 01
Start from the Apps page
In your Zapier account, open Apps and click + Add connection. Type Mailsoftly in the search box of the dialog that opens and pick it from the list of results.
- 02
Sign in to Mailsoftly
Click Add connection. Mailsoftly opens in a new tab: sign in with the account that holds the contacts, lists and forms your Zaps will use. That account has to exist before this step.
- 03
Grant access
Allow Zapier into the account. The connection is then offered in every Mailsoftly step. If the Zap touches lists or forms you do not own, make sure your account has read or write rights on them.
Your first Zap: tag form replies that meet a condition
GoalWhen someone submits one of your Mailsoftly forms and their answer matches your condition, the contact gets a tag you can target later.
- 01
Create the Zap and pick the form
In the editor, choose Mailsoftly and New Form Response as the starting event, select your connection, then pick the form. The form field is mandatory.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent responses to that form; choose one, it becomes the real sample every later field is mapped from.
- 03
Add the filter
Click the plus icon, add Filter, then set its three boxes: the answer to look at, the rule, the value. Use a text rule on a text answer, or nothing ever passes.
- 04
Add the tag step
Add the action, map the email from the sample response, then choose a tag or type a new tag name. Both fields are mandatory, and a missing tag is created on the way.
- 05
Test, then publish
Run each step once and check what came back, then click Publish. With the filter, this is a multi-step Zap, so it needs a paid plan to stay switched on.
Mailsoftly triggers: what can start a Zap
6 events start a Zap when something happens in Mailsoftly. Zapier checks for them at the interval your plan allows.
Campaign Sent
Polling triggerIn Zapier“Triggers when an email campaign has been sent.”
Once one of your email campaigns has gone out, this trigger passes it to the Zap, so the rest of your tools learn that the send happened without anyone reporting it.
New Contact
Polling triggerIn Zapier“Triggers when a contact is added to your account.”
Starts the Zap for every person added to your Mailsoftly account, whichever way they came in, and hands their details to the next steps.
New Contact in List
Polling triggerIn Zapier“Triggers when a contact is added to a list.”
Narrower than New Contact: it watches one list you choose and starts the Zap only when someone joins that list.
New Form Response
Polling triggerIn Zapier“Triggers when someone submits one of your Mailsoftly forms.”
Every time someone submits one of your Mailsoftly forms, the answers reach the Zap and can be used by every step after it.
New Unsubscribe
Polling triggerIn Zapier“Triggers when a contact unsubscribes from your emails.”
Fires when a contact opts out of your emails, so the decision can be copied to the other places that hold that address.
Updated Contact
Polling triggerIn Zapier“Triggers when a contact is created or changed.”
Broader than it sounds: this one reacts both when a contact is created and when an existing one changes.
Mailsoftly actions: what a Zap can do there
Mailsoftly gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Contact to List
ActionIn Zapier“Adds a contact to a list by email address, creating the contact if needed.”
Places a person in the list you choose, identified by email address, and creates the contact on the way if Mailsoftly does not know it yet.
Add Tag to Contact
ActionIn Zapier“Tags a contact by email address, creating the contact and the tag if needed.”
Labels a contact found by email address. If the contact or the tag does not exist, both are created along the way.
Add to Suppression List
ActionIn Zapier“Adds an email address to your suppression list so it never receives email from your account.”
Puts an email address on your suppression list, so your account never sends it anything again.
Create List
ActionIn Zapier“Creates a new contact list.”
Opens a fresh contact list under the name you give it, ready for the steps that follow to fill.
Create or Update Contact
ActionIn Zapier“Adds a contact, or updates the contact that already has this email address.”
Writes a person into Mailsoftly from an email address: it adds them, or updates the contact that already has that address.
Create Tag
ActionIn Zapier“Creates a contact tag (or returns the tag if it already exists).”
Makes a contact tag with the name you set, or simply returns it when a tag of that name already exists.
Remove Tag From Contact
ActionIn Zapier“Removes tags from a contact found by email address.”
The reverse move: it takes one or more tags off a contact located by email address.
Start Automation for Contact
ActionIn Zapier“Enrols an existing contact in an active automation.”
Enrols an existing contact in one of your active Mailsoftly automations, which then runs its own sequence.
Unsubscribe Contact
ActionIn Zapier“Unsubscribes an email address from all your emails (global unsubscribe).”
Unsubscribes an email address from all of your Mailsoftly emails at once, not from a single list.
Mailsoftly searches: find before you write
3 search steps look for data that already exists in Mailsoftly, so a later step can use it.
A search step finds a contact, a list or a tag that already exists and passes it to the next steps. In the action-event list, the three searches sit at the bottom, under SEARCH. Each one also has a find-or-create version: the same search with one box ticked, not a separate operation.
Find Contact
SearchFind or createIn Zapier“Finds a contact by email address.”
Looks up a contact by email address, so a later step works on the right person.
Find List
SearchFind or createIn Zapier“Finds a contact list by name.”
Finds one of your contact lists by its name and hands it to the following steps.
Find Tag
SearchFind or createIn Zapier“Finds a contact tag by name.”
Locates a contact tag by name, ready for an action that applies or removes it.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that needed it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing item.
- If multiple search results are found?Three ways out when several items match: keep the first, which is the default, stop the Zap, or pass all of them on at once.
When a Mailsoftly Zap breaks
Zapier ties no help article to Mailsoftly, so the cases below are the limits every Zap shares, seen from this app.
Most of them start on the trigger side: what it sees, what it ignores, and what happens when the Zap writes into what it watches. For a Zap that misbehaves in other ways, see Zapier troubleshooting.
Old contacts are never picked up
A Zap reacts only to what happens after you switch it on. Contacts, replies and unsubscribes that already existed stay out of it; moving them is a separate job.Updated Contact restarting itself
A Zap built on Updated Contact that tags or edits that same contact sets itself off again on each run, and the task count drops fast.A bulk import held back
When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold the runs back instead of firing them all.No double run for the same contact
Zapier remembers what it has already seen on a polling trigger, so a contact already processed by New Contact does not start the Zap a second time.
Need help automating Mailsoftly with Zapier?
A person reads every message.



