MailerLite
Connect MailerLite as a data source: the API key it needs, how it imports your subscribers once and keeps them current in real time through webhooks, how MailerLite groups become lists you can segment on, and how its subscription status maps to consent.
MailerLite is a native connector for your email-marketing audience. Once connected, it imports your MailerLite subscribers, groups and custom fields into Instasent and keeps them current in real time, so your email audience can drive SMS campaigns and automations alongside the rest of your audience.
How to connect
MailerLite connects with an API key: you generate a token in MailerLite first and paste it into Instasent. There is a single key to copy.
Generate the API key in MailerLite
In MailerLite, go to Integrations > MailerLite API > Generate new token and copy the token it creates.
Add the data source
In Data sources, select Add data source and choose MailerLite from the Integrations section.
Enter the key and connect
On the Connect step, fill in the connection name and paste your API key, then connect.
Initial import
The connector imports your subscribers once, then keeps them current through webhooks.
After connecting, the wizard continues through Mapping, Merge and Tags, the same steps as a CSV import.
What it syncs
- Subscribers — your MailerLite contacts, with their custom fields.
- Groups — MailerLite group memberships become client lists you can segment on.
- Events — subscriber activity: new sign-ups, unsubscribes, profile changes, group moves and deletions.
The direction is one-way, from MailerLite into Instasent, and contacts unify by email and phone — see unification.
How it stays current
MailerLite works best with accounts of up to 200,000 subscribers and no more than 10 groups; larger accounts still import fine, but each group is read separately, so it takes longer.
- Subscribers are imported once, when you connect.
- From then on they stay current in real time through webhooks — sign-ups, unsubscribes, profile changes, group moves and deletions arrive as they happen, and can trigger your automations.
- The group, segment and custom-field catalogue refreshes periodically on its own.
- There is no periodic re-import of contacts. If your receiver was unreachable and webhooks were missed, a manual full re-import is the way to reconcile — run it from the data source's sync options.
Field mapping
MailerLite subscriber fields map to the matching Instasent attributes — email to
_email, phone to _phone_mobile, and so on — and events arrive with their parameters.
You confirm the mapping on setup; see
field mapping.
Consent mapping
MailerLite imports the real email consent of each subscriber. Its subscription
status maps to Instasent's marketing-preference attribute (_accepts_marketing_*)
following the consent golden rule:
| MailerLite status | Instasent value | Meaning |
|---|---|---|
| Active (subscribed) | true | Accepted marketing |
| Unconfirmed / no status | null | No preference |
| Unsubscribed | false | Actively declined marketing |
Only an active opt-out (unsubscribed) in MailerLite becomes false. A subscriber
who never confirmed maps to no preference (null), never to false. For what these
values mean for who receives a campaign, see
Consent.