MailerLite Automations
How to Unsubscribe a MailerLite Subscriber When a Contact Form 7 Form Is Submitted
Making it easy to leave keeps your list healthy and your sending reputation intact. Zapify can unsubscribe somebody the moment they submit a form on your site, with the A form is submitted trigger and the Unsubscribe a subscriber action. MailerLite is a Zapify PRO integration.
What this automation does
The automation is one trigger plus one action:
- Trigger: A form is submitted (
CF7_FORM_SUBMITTED, Contact Form 7) - Action: Unsubscribe a subscriber (
MAILERLITE_UNSUBSCRIBE, MailerLite)
Each time the form is submitted, Zapify marks that address as unsubscribed in MailerLite. They stay in MailerLite, with their history, but no longer receive campaigns.
Before you start
- Contact Form 7 installed and active, with a published form that has an email field.
- A MailerLite account (the current MailerLite, not MailerLite Classic).
- A MailerLite API key — create one in MailerLite under Integrations → API. MailerLite's own page for it is here.
PRO feature
MailerLite is a Zapify PRO integration and needs a Connection under Settings → Connections. The A form is submitted trigger used here is free.
How to build the automation
Step 1: Connect MailerLite
- Go to Settings → Connections and click Add New.
- Choose MailerLite, paste in your API key, and name the connection something like Newsletter MailerLite.
- Click Test. Zapify asks MailerLite to accept the key and answers MailerLite accepted the credentials. If the key is wrong it says MailerLite refused the credentials. instead, so you find out before building anything.
- Save.
See Connections for how this screen works generally.
Step 2: Create a new automation
- In the WordPress admin, go to Zapify → Automations.
- Click Add New to open the builder.
- Name it clearly, such as Unsubscribe from the website form.
Step 3: Add the "A form is submitted" trigger
- Click Add Trigger.
- Choose Contact Form 7 as the app.
- Select A form is submitted.
- In the Form field, pick your unsubscribe form. Choosing a form gives you a token for each of its fields.
Step 4: Add the "Unsubscribe a subscriber" action
- Click Add Action.
- Choose MailerLite as the app.
- Select Unsubscribe a subscriber.
Step 5: Configure the action
| Field | Required | What it does |
|---|---|---|
| Connection | Yes | The MailerLite connection from Step 1. |
| Email address | Yes | Insert the token for the form's email field. |
Step 6: 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 7: Test it
Submit the form with an address that is subscribed. Check its status in MailerLite, or Zapify → Logs, which shows … was unsubscribed.
Tokens you can use
| Token | What it holds |
|---|---|
| Form title / Submitted at | Which form asked, and when, for your records. |
| One token per form field | Appear once you choose the form. |
The action makes one token available to later actions: Subscriber ID.
Conclusion
With the A form is submitted trigger and the Unsubscribe a subscriber action, leaving your list takes one form. To remove a person completely instead, see deleting a MailerLite subscriber.
FAQs
Is this free in Zapify?
The trigger is free. The MailerLite actions need an active Zapify PRO licence and a Connection.
Can anyone unsubscribe someone else?
Anybody can type any address into a public form, so this form could be used to unsubscribe a stranger. For most lists that is low risk, but if it matters, ask for a confirmation step or use a logged-in form.
What if the address is not in MailerLite?
It is recorded as unsubscribed rather than failing, which is the right result for somebody who asked not to be emailed.
Is this the same as MailerLite's unsubscribe link?
No. MailerLite's own link in each campaign keeps working. This is an extra way to leave, from your own site.
Why is my new group or custom field not in the dropdown?
Zapify keeps the groups and fields it reads from MailerLite for a minute, so the builder does not call MailerLite on every dropdown. Wait a moment and reopen the field. If the dropdown stays empty, use Test on the connection, because an unreachable MailerLite gives an empty list.
Does this work with MailerLite Classic?
No. Zapify uses MailerLite's current API, and the older Classic API is not supported. Create the API key in the current MailerLite under Integrations → API.
Do I need to write any code?
No. The API key is the only thing you copy from outside Zapify.