How to Add a MailerLite Subscriber When a Webhook Is Received

Not every signup happens on your WordPress site. A booking system, a landing page builder or a payment tool can often send a webhook instead. Zapify receives it with the free A webhook is received trigger and adds the person to MailerLite with the Add or update a subscriber action. MailerLite is a Zapify PRO integration.

What this automation does

The automation is one trigger plus one action:

• Trigger: A webhook is received (WEBHOOK_RECEIVED, Webhooks)
• Action: Add or update a subscriber (MAILERLITE_UPSERT_SUBSCRIBER, MailerLite)

When the outside service sends its webhook, Zapify reads the email and name from it and adds the person to MailerLite, or updates them if they are already there.

Before you start

• An outside tool that can send a webhook, and its documentation for what the webhook contains.
• 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.
• A group in MailerLite for these signups.

How to build the automation

Step 1: Connect MailerLite

1. Go to Settings → Connections and click Add New.

2. Choose MailerLite, paste in your API key, and name the connection something like Newsletter MailerLite.

3. 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.
4. Save.

See Connections for how this screen works generally.

Step 2: Create a new automation

1. In the WordPress admin, go to Zapify → Automations.
2. Click Add New to open the builder.
3. Name it clearly, such as Add webhook signups to MailerLite.

Step 3: Get the endpoint URL and capture a sample

1. Click Add Trigger.

2. Choose Webhooks as the app.

3. Select A webhook is received.

4. Copy the endpoint URL the builder shows and paste it into the sending service's webhook settings. Treat the URL as a credential — anyone who has it can send data to this automation.
5. Click Listen, then send one test delivery from the service. Zapify captures it and builds the token list from the real fields, so you pick them rather than guess.

See Webhooks for signatures, sources and event types.

Step 4: Add the "Add or update a subscriber" action

1. Click Add Action.

2. Choose MailerLite as the app.

3. Select Add or update 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 payload token that holds the person's email, such as email.
First name / Last name	No	Insert the matching payload tokens.
Groups	No	The group for people who arrive this way.
Status	No	Leave on Active. For an existing subscriber this leaves their status alone, and a new subscriber gets your MailerLite account's default.
Resubscribe	No	Leave off. Ticking it re-subscribes somebody who had unsubscribed — only do that where you have their fresh consent.

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.

1. Set the trigger and every action to Live.
2. Click Save.

Step 7: Test it

Send a test delivery from the outside service. Check the subscriber in MailerLite, or Zapify → Logs.

Tokens you can use

Token	What it holds
Received at / Raw body / Event type / External ID	Always available.
One token per payload field	Appear once you have captured a sample with Listen.

The action makes two tokens available to later actions: Subscriber ID and Subscriber status.

Conclusion

With the A webhook is received trigger and the Add or update a subscriber action, anything that can send a webhook can feed MailerLite. To send data the other way, see sending a webhook when a user registers.

FAQs

Is this free in Zapify?

The trigger is free. The MailerLite actions need an active Zapify PRO licence and a Connection.

Is the webhook safe to leave open?

The URL carries a long random key, and you can also require a signature on the trigger. See Webhooks.

What if the payload has no email?

The run fails and says the email address is empty, and nothing is sent to MailerLite.

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.