App integrations

email

Connect MailerLite to the platforms you already sell with

Use Plandalf to connect MailerLite with checkout pages, payment flows, email tools, CRM records, access systems, tax engines, and webhooks.

How it works

Plandalf is the commerce layer between apps

MailerLite keeps doing what it is best at. Plandalf handles the offer, checkout, buyer fields, payment context, invoice data, and post-purchase events that every other app needs.

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.

Search paths

Pages this hub can feed

Product surfaces to check before wiring MailerLite

A useful MailerLite integration page should show where the operator configures Offers, payment options, invoices, Automations, integrations, and API settings before a developer ships the flow.

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

Offer setup before anything syncs

MailerLite receives cleaner data when the offer, product, price, checkout mode, invoice, and automation path are defined first.

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

Follow-up starts from the purchase event

MailerLite should get buyer, product, coupon, invoice, and offer context from the purchase event instead of a disconnected form submit.

The Numi offer editor showing hosted checkout mode controls.

Checkout can live on the site or app

MailerLite can launch a hosted checkout, buy button, embedded flow, or SDK checkout depending on where the buyer starts.

Feature detail