Resources · Zapier integration

Mailazy Zapier integrationAutomate Mailazy with Zapier.

The Mailazy Zapier integration gives you 0 triggers, 1 action and 0 searches. That action, Send Mail, lets any other app send a transactional email through Mailazy, the kind a person expects after a payment, a purchase or a sign-up.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mailazy Zapier integration is for

The Mailazy Zapier integration lets other apps send emails through Mailazy, an email service that only handles transactional messages: the one-to-one emails sent because someone did something. It works in one direction: an event happens elsewhere, and Zapier asks Mailazy to send the email you wrote.

Three results that match what Mailazy is built for. A payment confirmation that never gets forgotten: a new payment in your billing tool runs Send Mail, and the customer gets a receipt-style message from your own address. A purchase confirmation: each new order sends a short recap to the buyer. An onboarding email: each new sign-up gets a welcome message with the first steps, written once and reused for everyone.

What Zapier does not do with Mailazy: anything but sending. There is no trigger, so nothing that happens in your Mailazy account can start a Zap. There is no search either, and no way to manage contacts or lists from Zapier. Mailazy is not a newsletter tool, and this integration does not turn it into one: one run, one email to one recipient. Write the message once in the Zap, and every event sends its own copy with the right name and address.

If you want a second opinion on Zapier before you build on it, our Zapier review is a good place to start.

Vocabulary

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. Mailazy has none, so the trigger of a Mailazy Zap always comes from another app.
Action
What the Zap does once started: the step that writes or sends something. With Mailazy, that is sending one email.
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 Mailazy account linked to Zapier once, then reused by every Zap that sends email through it.
Cost

What a Mailazy Zap costs you

Mailazy is not a premium app, so it works on the free plan. Each email sent successfully through Send Mail counts as one task; the trigger in the other app never costs anything.

  • One email sent1 task
  • Trigger in the other appFree, never counted
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A Zap that only runs Send Mail uses one task per email. A send that fails is not counted. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. Add a filter, for example to email only some payments, or a second action, and the Zap becomes multi-step, which needs a paid plan. Mailazy has no trigger: the interval grid below applies to the polling trigger of the app that starts your Zap.

Connect

Connect Mailazy to Zapier in three steps

  1. 01

    Open your connections

    Go to the Apps page of your Zapier account and click + Add connection. In the dialog that opens, type Mailazy and pick it from the list of apps shown.

  2. 02

    Sign in to Mailazy

    Click Add connection. Mailazy opens in a new tab: sign in with the account that owns the sender address you will use. You need a Mailazy account of your own for this step.

  3. 03

    Grant access

    Approve the access Zapier asks for. The connection then appears on the Apps page, and every Mailazy step reuses it. If the account belongs to a colleague, make sure you are allowed to send from it.

First Zap

Your first Mailazy Zap

GoalEach new payment recorded in your billing tool sends the customer a confirmation email through Mailazy, from your own address.

  1. 01

    Start with the payment

    Create a Zap and pick your payment tool as the first app, with its new payment event. Mailazy cannot start a Zap, so the trigger always comes from another app.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent payments; pick a real one with the customer's email address in it.

  3. 03

    Add Send Mail

    Add Mailazy as the action app and choose Send Mail. Map the customer's email into To, type your sender address in From, then write a Subject and the body of the email in the HTML field.

  4. 04

    Test the action

    Run the action test with your own address in To first. The email is really sent, so check it lands and reads well before anyone else gets it.

  5. 05

    Publish

    Click Publish to switch the Zap on. Payments recorded before that moment get no email; only the ones that come in after publishing do.

Actions

The Mailazy action

Mailazy gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Send Mail

Action

In Zapier“Send a Mail with mailazy”

Sends one email through Mailazy to one recipient, with a subject and a body you build from the earlier steps.

When to use it
for a message a person expects after doing something, such as paying, buying or signing up.
Watch out
To, From, Subject and the HTML body are required, and From must be an address tied to your Mailazy account.
When it breaks

When a Mailazy Zap breaks

Zapier links no help article to Mailazy, so the cases below are the general ones, applied to emails sent from other apps.

With Mailazy, most trouble comes from the sender setting or from the source app: a From address the account does not recognise, a missing recipient, or a batch of old records arriving at once. If a Zap still misbehaves, the Zapier troubleshooting page is the next stop.

  • Past events get no email

    A Zap only reacts to what happens after it is switched on. Payments or sign-ups from before are never emailed; sending to them is a separate job.

  • A sudden flood of events

    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 field left empty

    Send Mail needs To, From, Subject and a body. If the earlier step leaves the recipient empty, that email is not sent and the run stops there.

  • The same event emailed once

    On a polling trigger, Zapier remembers what it has already seen, so the same payment does not start the Zap, and the email, twice.
Need help

Need help automating Mailazy with Zapier?

A person reads every message.

FAQ

Mailazy Zapier integration FAQ

01Is the Mailazy Zapier integration free?
Yes, for a simple Zap. Mailazy is not a premium app, so it works on the free plan: 100 tasks a month and Zaps made of one trigger and one action. A new payment followed by Send Mail fits exactly. The moment you add a filter, for example to email only some payments, or a second action such as logging the email in a sheet, the Zap becomes multi-step and needs a paid plan. For one confirmation email per event, the free plan is enough to start.
02How many tasks does a Mailazy Zap use?
One per email sent successfully. The trigger in the other app is free, and Zapier checking that app for new items costs nothing either. A Zap that only runs Send Mail uses one task for each email; if you add a second action, each run uses two. A send that fails, for instance because the From address is not tied to your account, is not counted. With 100 tasks a month on the free plan, that means up to 100 emails sent through Zapier.
03Can Mailazy send emails in real time?
Mailazy has no trigger on Zapier, so the timing depends on the app that starts the Zap. If that app has an instant trigger, it tells Zapier as soon as the payment or sign-up happens, and the email goes out right after. If it has a polling trigger, Zapier checks it at the interval of your plan: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. For a confirmation email, an instant trigger on the source side makes a visible difference.
04What does it take to connect Mailazy to Zapier?
A Mailazy account you can sign in to, a Zapier account, and a sender address already associated with your Mailazy account. On the Apps page of Zapier, click + Add connection, search for Mailazy, click Add connection, sign in to Mailazy in the tab that opens and grant access. Every Mailazy step then reuses that connection. If the account belongs to someone else, make sure you have the right to send from it before you publish a Zap.
05Why does Send Mail reject the sender address?
Because the From field only takes an address associated with your Mailazy account, and the field is required, so it cannot be left empty either. An address your account does not carry is not accepted as the sender. Before publishing, run the action test with your own address in To: you see at once whether the sender goes through. A failed send costs no task, but no customer gets a confirmation until From is fixed, so check it before the first real payment comes in.
06What if the Mailazy trigger or action you need is not there?
Then Zapier cannot provide it: the list of operations comes from the Mailazy integration itself and cannot be extended from the editor. Today that list is one action, Send Mail, with no trigger and no search. If your plan depends on reacting to what happens inside your Mailazy account, Zapier cannot do it, so look for a tool that offers that operation before you build. Moving to a paid Zapier plan does not add operations either, so check this list before you design a bigger flow around Mailazy.
07Zapier, Make or n8n for Mailazy?
Decide on what you need from Mailazy, not on the brand. On Zapier you get one action, enough to send a transactional email whenever another app reports an event, but nothing that reacts to what happens in Mailazy. If you need more than sending, check whether the other platform offers Mailazy at all and with which operations. Then weigh how many emails you expect each month, since each one is a task here, and who will maintain the setup over time.
Same platform

Other docs you might need on this stack.

Browse all integrations