MailPoet Automations
How to Send an Email When a MailPoet Form Is Submitted
A MailPoet sign-up form quietly adds people to a list, and nobody on your team hears about it. Zapify can email you the moment the form is submitted, using the A form is submitted MailPoet trigger and the Send an email action. MailPoet is a Zapify PRO integration.
What this automation does
The automation is one trigger plus one action:
- Trigger: A form is submitted (
MAILPOET_FORM_SUBMITTED, MailPoet) - Action: Send an email (
WP_SEND_EMAIL, WordPress)
Whenever somebody submits the MailPoet form you choose, Zapify sends the email, filled with what they entered: name, email address, the lists they chose and any custom fields on the form.
Visitors and logged-in users
The trigger works for everyone who submits the form, logged in or not. If the submitted email belongs to a WordPress account, the run is attributed to that user; otherwise it runs anonymously and still sends the email.
When exactly does it run?
Zapify listens to MailPoet's "before subscribe" signal, so the email goes out as MailPoet is about to save the subscriber. That means it fires even if the person has not yet confirmed their subscription. To act only once they are confirmed, use a trigger on a subscriber being added to a list instead.
PRO feature
MailPoet is a Zapify PRO integration. The MailPoet trigger used in this automation needs an active Zapify PRO licence.
No Connection needed
MailPoet runs on your own site rather than somebody else's server. There is no API key to paste and nothing to set up under Settings → Connections — the integration only needs MailPoet installed and active.
Before you start
- MailPoet installed and active, with at least one form (MailPoet → Forms) shown on your site.
- A working mail setup so WordPress can send email.
- Know where the email should go, such as
marketing@example.com.
How to build the automation
Step 1: Create a new automation
- In the WordPress admin, go to Zapify → Automations.
- Click Add New to open the builder.
- Name it clearly, such as Alert the team about new MailPoet sign-ups.
Step 2: Add the "A form is submitted" trigger
- Click Add Trigger.
- Choose MailPoet as the app.
- Select the trigger A form is submitted.
Configure the trigger:
| Field | Required | What it does |
|---|---|---|
| Form | Yes | Pick the MailPoet form to watch, or leave it on Any form to run for every MailPoet form on the site. Choosing a specific form adds a token for each of its custom fields. |
Step 3: Add the "Send an email" action
- Click Add Action.
- Choose WordPress as the app.
- Select Send an email.
Step 4: Configure the email
In the To field, type your team's address. To reply straight to the subscriber, put the Email token in Reply to.
For example:
- Subject:
New sign-up: {Email} - Body:
{First name} {Last name} ({Email}) just signed up to {List names} through {Form name}. - Format: HTML or Plain text
Use the {} token button beside a field to insert the values — Zapify fills them in for each run.
Step 5: Set the steps Live and save
Each trigger and action has its own Live / Off / Draft switch. A new automation starts as a Draft and does nothing until its steps are Live.
- Set the trigger and every action to Live.
- Click Save.
Step 6: Test it
Open a page that shows the form and submit it with a test email address. Check the recipient inbox, or open Zapify → Logs to confirm the run.
Tokens you can use
| Token | What it holds |
|---|---|
| Form ID / Form name | The form that was submitted. |
| The email address entered. | |
| First name / Last name | The name parts, if the form asks for them. |
| List IDs / List names | The lists the person is being subscribed to, comma separated. |
| One token per custom field | The value entered in each custom field on the form. Available once you choose a specific form in the trigger — each field becomes a token named after its label, such as Phone. |
Multi-value fields such as checkbox groups are joined into a comma-separated list. With Any form selected only the general tokens are listed, but custom-field values are still filled in when the automation runs.
Conclusion
With the A form is submitted trigger and the Send an email action, every MailPoet sign-up reaches your team straight away. To put those sign-ups into another list or tag them, see adding a WooCommerce customer to MailPoet.
FAQs
Is this free in Zapify?
The Send an email action is free, but the MailPoet trigger is part of the MailPoet PRO integration and needs an active Zapify PRO licence.
Does it run for spam or failed sign-ups?
Captcha and MailPoet's sign-up throttling are checked before the signal Zapify listens to, so blocked attempts do not start the automation. A sign-up that MailPoet accepts at that point but then fails on later — for example the confirmation email cannot be sent — can still start it.
Can I send a thank-you to the subscriber too?
Yes. Add a second Send an email action and put the Email token in its To field. MailPoet's own confirmation and welcome emails are separate and unaffected.
Why do I not see my custom fields as tokens?
Choose a specific form in the trigger's Form field. With Any form selected, Zapify cannot know the fields in advance.
Can I get this for only some forms?
Yes. Pick the form in the trigger, or build one automation per form with its own email.
Do I need to write any code?
No. Everything is configured visually.