Learn Mokapen

Main menu
Campaigns Forms
Documents Notes
Shifts Presences
App Integrations Common features Contact us

MailerLite

Connect MailerLite to your organization's contacts in Mokapen. Import subscribers and leads already in your lists, keep data aligned between email marketing and CRM, or export to MailerLite contacts created in Mokapen — according to sync direction, filters, and field mapping you configure.

General overview: Integrations.

 

Requirements

  • Active MailerLite account with at least one subscriber or group to sync.
  • API key MailerLite (Classic or new MailerLite platform) with sufficient permissions to read and manage subscribers.
  • Mokapen plan that includes the marketing integration (Premium 3 — medal icon on the page if unavailable).
  • Mokapen permissions on contacts in the org (see Roles and permissions).

 

Connect MailerLite

Unlike Google Contacts or MailChimp, MailerLite connects with an API key, not OAuth login on the MailerLite site.

  1. User menu → IntegrationsMailerLite.
  2. Click Sync MailerLite (Premium 3 required).
  3. Open the API key section.
  4. Retrieve the key from the MailerLite dashboard (guide link on the page).
  5. Choose the account type:
  • MailerLite Classic — account on the previous version; use the «classic» API key.
  • MailerLite — account on the current platform; use the API token from the new interface.

Wrong type = failed connection even with a valid key.

  1. Paste the key in the field and click Connect.
  2. If the key is correct, Connected account appears with the MailerLite account email and sync settings.

If the key is wrong or expired, Mokapen shows a red error message: fix the account type or generate a new API key in MailerLite, then disconnect and reconnect.

 

What the API key allows

The key authorizes Mokapen to communicate with MailerLite via API: read subscribers, groups, and custom fields, create or update subscribers when sync direction allows. It does not open a MailerLite web session in your browser — keep the key secure and do not share it outside the authorized team.

If you revoke or regenerate the key in MailerLite → sync in Mokapen stops working until you enter the new key (disconnect and reconnect).

 

Settings to configure

 

Sync direction

  • To Mokapen only — MailerLite → CRM (subscriber import).
  • To MailerLite only — CRM → MailerLite (contact export).
  • Both — alignment in both directions, with rules on duplicates and conflicts.

Changing direction shows or hides the «from MailerLite» and «from Mokapen» filter blocks: follow what you see on the page.

 

Import filters from MailerLite

Visible with sync to Mokapen or bidirectional. Choose which subscribers to import:

  • Active subscribers — only active subscribers in MailerLite (recommended for most cases).
  • All subscribers — also includes unsubscribed or non-active statuses, if present.
  • Groups — limit to a MailerLite group: «belongs to» or «does not belong to» the chosen group.
  • Fields — filter by a MailerLite custom field with operators (equals, contains, starts with, empty, has a value, etc.) and text value.

Changing filters shows a warning: after the change, it is best to re-run sync.

 

Export filters to MailerLite

Visible when sync direction is to MailerLite or both. These filters define which Mokapen contacts can be sent to MailerLite — not only on the first «Sync», but also every time you create or modify a contact in the CRM.

In practice: you save a contact in Mokapen → Mokapen checks whether it matches the type, tags and privacy consents you have set → only if it passes all filters is it created or updated in MailerLite. A contact that does not match stays in Mokapen but is not sent (and does not appear in the export preview). If you change the filters after having already synced, it is best to re-run sync: contacts that no longer match may stop being updated in MailerLite.

 

Type and Type 2 — restrict export to CRM contact categories (e.g. only «Customer» or «Qualified Lead»). Useful if you want only a commercial segment in MailerLite, not your entire address book.

 

Tags — one or more contact tags: exports only contacts that have them (e.g. tag «Newsletter» or «Event 2026»). Can be combined with Type/Type 2: all selected criteria must be satisfied.

 

Privacy / GDPR permissions — a list of checkboxes with the consents configured in your org (newsletter, data processing, marketing communications, etc.). Check only those that must already be recorded on the contact for the export to be lawful and GDPR-compliant.

Example: you check only «Newsletter consent» → Mokapen sends to MailerLite only contacts that have that consent recorded in their profile. A lead without marketing consent stays in the CRM but does not end up on MailerLite, even if they have the right email and tags. This is the most important filter to avoid subscribing people without a legal basis: configure it before enabling automatic sync to MailerLite.

 

The counter and preview link on the page show how many contacts match the filters right now, before syncing. Use them to verify you are not about to export thousands of records by mistake, or conversely, that the filters are not too tight (preview showing zero contacts).

 

Field mapping

In the Link fields section, match MailerLite fields (default and custom) to Mokapen columns. The primary email stays on the contact email field and is fixed.

Each Mokapen column can be used only once. Leave a MailerLite field empty if you do not need it in the CRM.

 

Duplicates and conflicts

When the same person exists in both MailerLite and Mokapen (same email), Mokapen must decide whether to merge, skip or update. Two options on the page:

 

Email comparison — always active and cannot be disabled. Before creating a contact from MailerLite, Mokapen searches the org for a contact with the same email: if found, it does not create a second one but updates the existing one (according to the conflict rules below). Avoids duplicate address books after the first bulk import.

 

Conflict handling — if the email matches but name, phone, company or other mapped fields do not match, choose who «wins»:

  • MailerLite — in case of discrepancy, MailerLite values overwrite those in Mokapen at sync.
  • Mokapen — the CRM takes precedence; MailerLite is updated with Mokapen data when sync direction allows.

Advice: for initial import from marketing lists, it often makes sense to let MailerLite prevail on contact fields; if the CRM is the commercial source of truth, choose Mokapen. Test on a sample before automatic sync on thousands of contacts.

 

Automatic or manual sync

Decides when Mokapen performs the alignment, not what to sync (that is defined by direction and filters).

 

Automatic sync — Mokapen propagates changes in the background: a new subscriber on MailerLite can appear in the CRM, a contact modification in Mokapen (if it passes the export filters) can update MailerLite without pressing the button each time. Convenient for teams that work every day on both systems.

 

Manual sync — no updates until you press Sync. Useful during setup (check mapping and filters), after major privacy consent changes, or if you want to approve each batch before it goes to MailerLite.

 

You can switch from manual to automatic at any time with Save; the choice does not delete data already synced.

 

Visibility

This concerns contacts imported from MailerLite into Mokapen (sync to CRM or bidirectional). It does not change who sees MailerLite — only who, inside Mokapen, can open the records created by this sync.

 

All members (public visibility) — every user in the org with contact permissions can see the imported records: suitable for a shared CRM, with sales and marketing on the same subscriber base.

 

Only selected members (private visibility) — limit access to yourself and/or users or teams you choose from the menu. Others in the org cannot see those records even if the sync is active. Useful if you connect a personal list or a restricted segment; combine with Mokapen roles: a user without contact permissions cannot manage them anyway.

 

If the org already has global privacy rules (mandatory Team Master), some options may be preset or locked on the page — follow what appears in the integration.

 

Share sync

With an appropriate plan, other members can use your MailerLite connection (same API key) without re-entering it. Who created the connection remains visible in Created by.

 

Mandatory authorization

Check «I authorize Mokapen to create a copy…» — without that checkbox, the Save and Sync buttons remain disabled.

Then click Sync. On large lists the operation may take several minutes.

 

Behavior in Mokapen

  • From the contacts list you can re-run sync from the integrations menu (if permitted).
  • With export active, creating or updating a contact in Mokapen that matches the filters may update the subscriber on MailerLite.
  • MailerLite groups do not automatically become Mokapen tags: use CRM tags and filters if you need internal segmentation.
  • This integration syncs contacts / subscribers, not email campaigns: a separate «MailerLite Campaigns» connection exists in Integrations.

 

Common issues

  • API key error — verify Classic vs current MailerLite; regenerate the key in the MailerLite dashboard.
  • No subscribers imported — check filters (active only, wrong group) and sync direction.
  • Too many duplicates — email comparison is fixed; use the Duplicates tool after the first import.
  • Empty export — type/tag/privacy filters too restrictive; use the contact count preview.
  • Sync blocked — verify the authorization checkbox; disconnect and reconnect with a valid key.

 

Disconnect

Click Disconnect: a window opens with the Keep section. There you decide what to do with data already imported into Mokapen with this sync.

Options in Mokapen (checked boxes = keep, default):

  • Contacts — if you leave the box checked, contacts imported from MailerLite remain in Mokapen but no longer sync. If you uncheck it, Mokapen removes from the org contacts linked to this MailerLite integration.
  • Companies — same logic for company records linked to the sync (keep or remove from Mokapen).

Disconnecting does not automatically delete subscribers on MailerLite: they remain in your account unless you delete them there. Mokapen does not revoke the API key in MailerLite — revoke it manually in the MailerLite dashboard if you will no longer use it.

After choosing, type the confirmation word and confirm Disconnect. Removing many contacts may take a few minutes.

Learn more: Contacts guide.

Need help?