---
title: "Linkbreakers + MailerLite: sync QR code subscribers to MailerLite groups"
description: "Connect MailerLite with an API token and every person who scans your QR codes and gives their email becomes a MailerLite subscriber, added to the group you choose, with their name, phone and form answers in subscriber fields. Without consent they are kept unconfirmed, so campaigns skip them. Setup, what is synced, and the Assistant and MCP tools."
canonical: "https://linkbreakers.com/help/article/linkbreakers-mailerlite-integration-sync-qr-code-subscribers-to-groups"
last-updated: 2026-11-09
---

# Linkbreakers + MailerLite: sync QR code subscribers to MailerLite groups

> Connect MailerLite with an API token and every person who scans your QR codes and gives their email becomes a MailerLite subscriber, added to the group you choose, with their name, phone and form answers in subscriber fields. Without consent they are kept unconfirmed, so campaigns skip them. Setup, what is synced, and the Assistant and MCP tools.

:::try-ai-prompt {"prompt":"Connect MailerLite with my API token, add synced subscribers to my QR leads group, and use my form's Consent field as their marketing consent","description":"Connect MailerLite with the Assistant.","target":"assistant"}:::

## Short answer

Linkbreakers syncs the people who scan your QR codes to MailerLite directly. In the dashboard, open **Integrations**, pick **MailerLite**, paste a MailerLite API token and select **Connect**. From then on, every person who goes through one of your links or QR codes and whose email Linkbreakers knows, for example after a form, is created or updated as a MailerLite subscriber, with their name, last name, phone and form answers, and added to the MailerLite group you choose.

With a consent answer chosen, people who did not say yes are kept as unconfirmed subscribers, which MailerLite campaigns skip. No Zapier, Make or webhook is needed, and the integration is available on every plan.

## Quick summary

- Connect once per workspace with an API token from **Integrations > MailerLite API** (the new MailerLite, not Classic)
- Subscribers are created or updated, matched on email
- Name, last name and phone go to MailerLite's own fields
- Form answers go to subscriber fields with the same key (text, number or date)
- Optionally added to one group; groups are only added, never removed
- Marketing consent decides whether a new subscriber is active or unconfirmed
- Visitors known only by phone are not synced: MailerLite subscribers need an email
- Also set up from the Assistant, the MCP server or the REST API

## How it works

A subscriber is synced when a visitor goes through a step of a link's workflow and Linkbreakers knows their email. That is usually right after a [form](/help/article/how-to-create-a-form), but it can also come from the chat bot or any step that saves visitor data. Linkbreakers sends the subscriber to MailerLite from its servers, once per step, at the moments the connection covers (all of them by default).

MailerLite matches subscribers on email, so a returning visitor updates the same subscriber. Linkbreakers reads the subscriber's status first, so it knows whether they are new, unconfirmed, active or unsubscribed before writing anything.

## Connect MailerLite

1. In MailerLite, open **Integrations > MailerLite API** and select **Generate new token**. Keys from MailerLite Classic do not work.
2. In Linkbreakers, open **Integrations** in the dashboard and pick **MailerLite**.
3. Paste the token in **MailerLite API token** and select **Connect**. Linkbreakers checks it against MailerLite before storing it.
4. Under **Add contacts to a group**, choose the group subscribers join, or **No group: contacts only**.
5. Set the options and the delivery setting below, then save.

The token is encrypted when it is stored and never shown again; the page shows how many groups the account has, to tell accounts apart.

## What gets synced

| Linkbreakers | MailerLite |
|---|---|
| Email | Subscriber email (the match) |
| First name | `name` field |
| Last name | `last_name` field |
| Phone | `phone` field |
| Form answers and other visitor data | Subscriber fields with the same key, or the one you map them to |
| The group you chose | Added to the subscriber's groups |

MailerLite fields include its default ones (company, city and so on) and your custom fields. An answer goes to the field with the same key, when the field is text, number or date. Create fields in MailerLite under **Subscribers > Fields**, with the same keys as your form fields, or map an answer to a field on the MailerLite page. Text is cut to 255 characters. **Test connection** lists the field keys Linkbreakers can write to.

## Marketing consent in MailerLite

Choose the answer where people agree to hear from you under **Marketing consent**: the **Linkbreakers consent** (a Consent field on your form, or the marketing consent goal of the [chat bot](/help/article/how-to-add-an-ai-chat-bot-to-a-qr-code)), or any other answer, such as a checkbox of your own. Linkbreakers then sets the subscriber's status this way:

| Subscriber | Visitor said yes | Visitor did not say yes |
|---|---|---|
| New | MailerLite's default for new subscribers: active, or unconfirmed with a confirmation email if your account has double opt-in for API and integrations turned on | Unconfirmed, which campaigns skip |
| Unconfirmed | Active | Stays unconfirmed |
| Active | Stays active | Stays active |
| Unsubscribed, bounced or junk | Stays as it is | Stays as it is |

So a visitor first synced without consent is subscribed once they give it, and someone who unsubscribed is never subscribed again. Linkbreakers never marks anyone unsubscribed, which in MailerLite would be final.

With no consent answer chosen, Linkbreakers sets no status, and new subscribers get MailerLite's default (active, unless your account confirms subscriptions from the API by email).

You can also tick **Add to the group only those who consented**. Double opt-in in MailerLite is an account setting (**Double opt-in for API and integrations**), not something Linkbreakers can ask for per subscriber, so the Linkbreakers double opt-in option is not shown. MailerLite has groups and no tags, so the tags option is not shown either.

## Which visitors and which links

The MailerLite page has the same three settings as the other Linkbreakers integrations:

- **Where**: every link, or only some links, directories and tags
- **When**: the moments of a visit (Entry, Interaction, Routing, Exit), or specific steps
- **What is sent**: all visitor data, only some, or just the visit. Email and phone are always sent

Only visits by people are synced: bots, link previews and AI agents never become subscribers. Visits past your plan's tracked visits allowance are not synced.

## What is not synced

- Visitors without an email, including those known only by their phone. They are skipped, not counted as failures
- Answers with no matching MailerLite field, or for fields that are not text, number or date
- Removals: groups are only added
- Anything back from MailerLite

## Set it up from the Assistant, MCP or the API

**Assistant**: in the dashboard, ask "Connect MailerLite with my API token and add new subscribers to my QR leads group".

**MCP server**: an agent connected to the [Linkbreakers MCP server](/help/article/mcp-server-setup) has `contact_integration_connect`, `contact_integration_lists` (the groups), `contact_integration_fields`, `contact_integration_update`, `contact_integration_test`, `contact_integration_get`, `contact_integrations_list` and `contact_integration_disconnect`, with the tool `CONTACT_TOOL_MAILERLITE`.

**REST API**, with a token that has the `integrations:write` scope:

```bash
curl -X POST https://api.linkbreakers.com/v1/integrations/contacts/CONTACT_TOOL_MAILERLITE/connect \
  -H "Authorization: Bearer $LINKBREAKERS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"apiKey": "your-mailerlite-token"}'

curl -X PATCH https://api.linkbreakers.com/v1/integrations/contacts/CONTACT_TOOL_MAILERLITE \
  -H "Authorization: Bearer $LINKBREAKERS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"contactListId": "123456789", "options": {"consentAttributeKey": "$marketingConsent"}}'
```

## Limits and caveats

- **Email required.** Phone-only visitors are skipped
- **One MailerLite account and one group per workspace**
- **Double opt-in is MailerLite's account setting**, not a Linkbreakers option
- **No retries.** A subscriber MailerLite refuses is reported as the last error on the page, not sent again
- **One way.** Nothing is read back from MailerLite but groups, fields and the status of the subscriber being synced

## Frequently asked questions

### Does it work with MailerLite Classic?

No. Linkbreakers uses the API of the new MailerLite, and a Classic API key is refused when you connect.

### Will people who did not consent receive my campaigns?

Not when you choose a consent answer: new subscribers without consent are created as unconfirmed, and MailerLite campaigns only go to active subscribers.

### Will someone who unsubscribed be subscribed again?

No. Unsubscribed, bounced and junk subscribers keep their status.

### Can I send a confirmation email before subscribing people?

Yes, from MailerLite: turn on double opt-in for API and integrations in your MailerLite account, and new subscribers who consented get MailerLite's confirmation email.

### What happens when I disconnect MailerLite?

Visitors stop being synced and the stored token is deleted. Subscribers already in MailerLite stay there.

## Sources

- Linkbreakers MailerLite integration page, API and MCP tools, checked in the product on 2026-11-09.
- MailerLite API documentation: https://developers.mailerlite.com/docs/

## Last reviewed

2026-11-09 by Laurent Schaffner.