- Home
- Resources
- Integrations
- Mail Blaze
Mail Blaze Zapier integrationAutomate Mail Blaze with Zapier.
The Mail Blaze Zapier integration gives you 0 triggers, 2 actions and 0 searches. Mail Blaze cannot start a Zap, but any other app can feed it: new people land on your mailing list, and people who change their address stay reachable.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mail Blaze Zapier integration is for
The Mail Blaze Zapier integration lets other apps write into Mail Blaze, the email marketing platform you use to build campaigns and send them to your subscribers. It works in one direction: something happens in another tool, and Zapier adds or updates a subscriber in Mail Blaze for you.
Three results people usually set up first. A list that grows on its own: every sign-up collected by a form goes through Add Subscriber, so nobody exports and imports files any more. Addresses that stay right: when a contact changes their email in your CRM, Update Subscriber swaps the old address for the new one, and your next campaign reaches the inbox they actually read. One list fed by several sources: a spreadsheet, a form and a sign-up page can all run Add Subscriber in separate Zaps.
What Zapier does not do with Mail Blaze: react to it. There is no trigger, so nothing that happens inside your Mail Blaze account can start a Zap, whatever it is. There is no search either, so a Zap cannot check whether someone is already on the list before acting. And nothing here sends a campaign: that stays in Mail Blaze.
If you are still weighing platforms, the n8n vs Zapier comparison is a fair place to start.
Zapier vocabulary in one minute
Seven words come back on this page. Here they are once, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event that starts the Zap. Mail Blaze has none, so the trigger of a Mail Blaze Zap always lives in another app.
- Action
- What the Zap does once started: the step that writes something. Here, adding a subscriber or updating one in Mail Blaze.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer; an instant one is reported by its app straight away. It depends on the app that starts the Zap.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
- Connection
- Your Mail Blaze account linked to Zapier once, then reused by every Zap that adds or updates subscribers.
What a Mail Blaze Zap costs you
Mail Blaze is not a premium app, so it works on the free plan. Each subscriber added or updated successfully counts as one task; the trigger in the other app costs nothing.
- Add or update one subscriber1 task
- Trigger in the other appFree, never counted
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
A Zap with one action uses one task per run, a Zap with two actions uses two. A failed action is not counted. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. Mail Blaze has no trigger: the interval grid below applies to the polling trigger of the app that starts your Zap.
Connect Mail Blaze to Zapier in three steps
- 01
Open your connections
Go to the Apps page of your Zapier account and click + Add connection. In the dialog that opens, type Mail Blaze and pick it from the list of apps shown.
- 02
Sign in to Mail Blaze
Click Add connection. Mail Blaze opens in a new tab: sign in with the account that owns the mailing list you want to feed. You need a Mail Blaze account of your own for this.
- 03
Grant access
Approve the access Zapier asks for. The connection then appears on the Apps page, and every Mail Blaze step reuses it. If the list belongs to a colleague, your account needs write access to it.
Your first Mail Blaze Zap
GoalEach person who fills in your website form is added to your Mail Blaze list, ready for the next campaign.
- 01
Start with the form
Create a Zap and pick your form tool as the first app, with its new entry event. Mail Blaze cannot start a Zap, so the trigger always comes from somewhere else.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent entries of the form; pick one that has an email address filled in.
- 03
Add Add Subscriber
Add Mail Blaze as the action app and choose Add Subscriber. Map the email from the form into the Email field, which is required.
- 04
Test the action
Run the action test and open your list in Mail Blaze: the person should be there. It is a real subscriber, so remove it if it was a test.
- 05
Publish
Click Publish to switch the Zap on. Entries sent before that moment are not added to Mail Blaze; only the ones that arrive after publishing are.
The 2 Mail Blaze actions
Mail Blaze gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Subscriber
ActionIn Zapier“Adds a new subscriber to your mailing list.”
Puts a new person on your Mail Blaze mailing list, using an address that arrived in another app.
Update Subscriber
ActionIn Zapier“Update an existing subscriber.”
Changes a subscriber who is already in Mail Blaze, typically to replace an address that is no longer used.
When a Mail Blaze Zap breaks
Zapier links no help article to Mail Blaze, so the cases below are the general ones, applied to a list you feed from other apps.
Most trouble with Mail Blaze comes from the source app: an empty email field, or a big import that sends far more entries than usual. If a Zap still misbehaves, the Zapier troubleshooting page is the next stop.
Old sign-ups are not added
A Zap only reacts to what happens after it is switched on. People already in your form or sheet are not sent over; moving them is a separate job.A sudden flood of entries
After a bulk import or a migration in the source app, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.A required email left empty
Add Subscriber needs Email and Update Subscriber needs Old Email. When the earlier step leaves one empty, that run does not go through.The same entry seen once
On a polling trigger, Zapier remembers what it has already seen, so the same form entry does not start the Zap twice.
Need help automating Mail Blaze with Zapier?
A person reads every message.



