MailerLite Classic
Overview
AFI subscribes contacts to MailerLite Classic — the legacy MailerLite product (sometimes labelled MailerLite v1). If you’re on the new MailerLite (2024+), use the MailerLite doc instead. The two products run on different APIs and groups don’t sync between them.
Supported actions
- Subscribe to Group
- Update Subscriber
- Unsubscribe
Authentication
- Log in to MailerLite Classic.
- Click Integrations > Developer API.
- Copy the API key (it starts with the classic v1 format).
- In AFI go to Settings > MailerLite Classic and paste the key.
How to create the integration
- In WordPress admin, go to AFI > New Integration.
- Pick your Sender (Contact Form 7, WPForms, WooCommerce, etc.) and the form / event to listen on.
- Pick MailerLite Classic as the Receiver, then pick the Task you want to run.
- Map sender fields onto MailerLite Classic’s fields. Email is required. Custom fields must exist on the Classic side before mapping.
- Optional: add Conditional Logic so the action only fires on matching submissions.
- Save and run a test submission. Check AFI > Log if anything looks off.
Notes & caveats
- Classic vs new MailerLite. If MailerLite has migrated you to the new platform, the Classic API key will stop working — switch to the MailerLite integration.
- Groups, not lists. MailerLite Classic uses Groups as its segmentation primitive — pick the right Group ID when mapping.
- Confirmation emails. If your Classic account has double opt-in enabled, the subscriber will receive a confirmation email; only confirmed subscribers count toward your sending limits.