Integration

MailerLite

Plandalf integrates with MailerLite as a email, marketing, website, sdk platform.

email marketing website sdk

Visit MailerLite →

What it does

Sends emailEmail GIF promo Notifications
Runs automationsAutomation Purchase automations
Plandalf Automation IntegrationAutomation Purchase automations
Custom HTML blocksTotally custom checkout layouts Buy button
Per-recipient timer imagesEmail GIF promo Deadline campaigns
Webhook Customer CreatedAPI SDK
Open APIAPI SDK

Product surfaces

Where MailerLite fits in the buying workflow

Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before MailerLite receives checkout, payment, tax, or workflow context.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.

Offer configuration stays visible

Use Offers to decide what MailerLite receives: product, price, buyer, checkout mode, invoice, and automation context.

Offers Products Prices Checkout templates

The Numi checkout elements palette showing content, interactive, and selling blocks.

Checkout layout and selling blocks stay editable

Before MailerLite enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.

Checkout templates Order bumps Upsells Coupons

The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

MailerLite should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

Purchase automations Automations Sequences Webhooks

The Numi offer editor showing hosted checkout mode controls.

The buying surface can live where the buyer is

MailerLite can start the sale through a hosted checkout, embedded checkout, modal, inline flow, or buy button depending on the stack.

Hosted checkout Buy button SDK checkout API-first stack

Builder paths

Stack guides that use MailerLite

Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.

The Course CreatorEnrol each buyer into the right cohort sequence the moment they pay.The Kajabi Course LaunchSell a Kajabi course through a more flexible offer and send each buyer into the right follow-up path.

MailerLite stack recipes

Find full stack guides that pair MailerLite with checkout, payment, automation, fulfilment, records, and downstream integrations.

Offers overview

Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.

Hosted checkout

Use hosted checkout when MailerLite should hand the buyer to a branded Plandalf checkout page.

SDK checkout

Use SDK checkout when MailerLite belongs inside an app, custom site, or API-first stack.

Webhooks

Route checkout events, purchase events, payment state, invoices, and customer context into another tool.

Checkout completed fulfilment

Turn a completed checkout into access, receipts, CRM updates, support context, and records.

Overview

MailerLite is an email-marketing platform with a built-in workflow automations feature. Merchants running deadline promos on Plandalf typically use MailerLite to announce the offer, and want their subscribers to land on the promo’s tracking URL with their own countdown already running.

What Plandalf does here

Automation integration — app/Apps/Mailerlite/ contains a real handler with a SubscriberCreated trigger and actions for adding subscribers to groups, upserting them, and updating custom fields.
Promo email countdown — paste a small <img> tag into any MailerLite campaign; Plandalf serves a per-recipient animated GIF using MailerLite’s {$email} personalization tag as the participant reference.
Promo enrolment via workflow — a MailerLite automation can POST to the promo’s catch URL on subscriber-joins-group, starting each recipient’s deadline the moment they enter the list.

What Plandalf does not do

We do not replace MailerLite. There is no migrate.* template for MailerLite because Plandalf isn’t an ESP.
We do not claim trigger_on_form_submit — nothing in the integration handler consumes that path today.

Setup templates

Drop-in implementations

Copy-paste setups for the most common ways to wire MailerLite into Plandalf.

promo · email

Drop the Plandalf countdown image into a MailerLite campaign

Paste this <img> tag into any HTML block in your MailerLite campaign. {$email} is MailerLite's own personalization tag — when the email sends, MailerLite swaps it for the subscriber's address, which keeps each recipient on their own deadline.

<img
  src="{{ promo.countdown_url }}?ref={$email}"
  alt="Time remaining on this offer"
  border="0"
  style="display:block;border:0;outline:none;text-decoration:none;max-width:100%;height:auto;"
/>

promo · automation

Enrol MailerLite subscribers into this promo automatically

In MailerLite, open Automations → Create workflow.
Trigger: When subscriber joins a group, pick the group that should land in this promo.
Add step: Webhook / HTTP request.
URL:
```
{{ promo.catch_url }}
```
Method POST, content type application/json.

Body:

{"email": "{$email}", "ref": "{$email}"}

Save and turn the workflow on.

Automation graph

Connecting MailerLite

How MailerLite participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from MailerLite

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

mailerlite.subscriber_added: Fires when a new subscriber is added to MailerLite.
mailerlite.automation_step_reached: Fires when a contact reaches a designated step in a MailerLite automation.
mailerlite.webhook: Fires when MailerLite POSTs to a Plandalf webhook URL — use for anything not covered by a native trigger.

Actions on MailerLite

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

mailerlite.add_subscriber: Add a contact to a list or audience in MailerLite.
mailerlite.tag: Apply a tag or segment to an existing MailerLite contact.
mailerlite.send_email: Send a one-off transactional or broadcast email through MailerLite.
mailerlite.start_automation: Enrol a contact into a MailerLite automation.
mailerlite.custom_api_call: Hit any MailerLite REST endpoint with a templated payload.

Embeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution

Example sequence

trigger: stripe.payment_succeeded
actions:
  - mailerlite.add_subscriber:
      list: paying-customers
      tag: tier-${plan}
  - plandalf.grant_entitlement: ${product_slug}

Pair it with

Connect MailerLite with…

Platforms whose roles complement MailerLite inside a Plandalf sequence.

MailerLite + ActiveCampaign

Capture a lead on ActiveCampaign, nurture it through MailerLite.

MailerLite + beehiiv

Capture a lead on beehiiv, nurture it through MailerLite.

MailerLite + Kit (ConvertKit)

Capture a lead on Kit (ConvertKit), nurture it through MailerLite.

MailerLite + Customer.io

Capture a lead on Customer.io, nurture it through MailerLite.

MailerLite + Drip

Capture a lead on Drip, nurture it through MailerLite.

MailerLite + Flodesk

Capture a lead on Flodesk, nurture it through MailerLite.

See all integrations →

Integration methods

How MailerLite connects to Plandalf

Each method below is the minimum viable setup. Pick the one closest to how you already use MailerLite with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.

Method 1
Embed a Plandalf buy button
Drop the Plandalf embed script into a MailerLite HTML block and tag any element with `data-plandalf-present` to open the configured flow on click.
```
<script src="https://cdn.plandalf.com/embed.js" async></script>

<button data-plandalf-present="offer_abc123">
  Buy now
</button>
```
Method 2
Drop in a per-recipient countdown image
Add an HTML block to any MailerLite email and paste the Plandalf countdown URL. MailerLite's merge tag `{$email}` substitutes per recipient so each subscriber sees a timer pegged to their own deadline.
```
<img
  src="https://cdn.plandalf.com/timers/{TIMER_ID}.gif?ref={$email}"
  alt="Time remaining on this offer"
  width="600"
  height="120"
/>
```
Method 3
Enrol from an automation step
Inside MailerLite's automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror MailerLite journey logic into Plandalf without re-building the segmentation.
```
{
  "email": "{{ contact.email }}",
  "sequence": "post-signup-onboarding",
  "source": "mailerlite"
}
```
Method 4
REST API webhook
For anything not covered by a native trigger, configure a MailerLite webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.
```
curl -X POST https://api.plandalf.com/v1/webhooks/mailerlite \
  -H "Authorization: Bearer $PLANDALF_API_KEY" \
  -H "Content-Type: application/json" \
  -d @event.json
```

Official MailerLite docs and sign-up: www.mailerlite.com

FAQ

Common questions about the MailerLite integration

Do I need a paid plan to use MailerLite with Plandalf?

Plandalf itself is free to connect. MailerLite's native webhook step is on its paid tiers — on the free plan, route the trigger through Zapier instead, which still works end-to-end.

How long does setup take?

Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.

Can I disconnect MailerLite later without losing data?

Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and MailerLite's own records are untouched. You can reconnect any time and resume from the last seen event.

Does Plandalf store MailerLite data?

Plandalf stores the MailerLite contact ID and the events Plandalf fired against that contact. Email content stays in MailerLite; Plandalf doesn't mirror your audience or newsletter archive.

What if my email need isn't covered by the actions or triggers listed here?

Use the generic `mailerlite.custom_api_call` action or the inbound `mailerlite.webhook` trigger. Anything MailerLite's REST API can do, a Plandalf sequence can drive.

Is there a usage limit?

Plandalf respects MailerLite's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.

Where do I find MailerLite's own documentation?

MailerLite's homepage at https://www.mailerlite.com links to their developer docs. For Plandalf-side questions about the MailerLite integration, see the Plandalf docs.