Torii Membership System

MailerLite

The MailerLite connector keeps subscribers, custom fields, and access in sync between your site and MailerLite.

MailerLite is an email marketing platform: subscribers, groups, custom fields, and automations. It has no notion of memberships, and it has no tags; it has groups. The connector bridges both gaps, and how it maps tags onto groups is the main thing to understand before designing your setup.

Tags are groups

Torii tags map to MailerLite groups, one for one. A local tag linked to a group works the same as a mapped tag with any other CRM: when the member gains the tag, they're added to the group; when they lose it, they're removed. Group changes flow back too, so a MailerLite automation that adds a subscriber to a group grants site access at the next sync.

That mapping is what makes MailerLite automations the access engine for your site. The usual recipe: an automation triggered by a purchase or a signup adds the subscriber to the "member" group, and a cancellation or refund removes them. Your site follows the groups without any further wiring.

The tight coupling of groups and automations is a two-edged sword. In MailerLite, groups are the audience machinery: automations key on them, campaigns send to them, and every group carries that weight. MailerLite has no equivalent of a lightweight tag, so a mapped group is always a "real" MailerLite object.

The answer is that mapping is optional. Torii tags don't have to map to MailerLite groups; an unmapped tag stays local, costs nothing in MailerLite, and still drives access rules on your site. Map the tags whose changes MailerLite needs to act on (purchases, cancellations, tier changes), and keep everything else, course-completion markers, internal flags, support notes, as local tags. The local-versus-mapped distinction is the same everywhere in Torii; see User Tags.

Custom fields and contacts

Contacts sync both ways. A member who registers on your site appears as a MailerLite subscriber with their name filled in; a member who updates their details on your site updates the subscriber record. Writes from your site are deliberately non-destructive: only the fields you send are touched, so a sync never wipes fields your MailerLite automations maintain on their own.

Custom fields map through the same local-field system as every other connector: create the local field, map it to the MailerLite field, and values sync in both directions. The name fields are managed for you and protected from mapping, since Torii writes those through its own path.

Webhooks

The connector subscribes to MailerLite's subscriber events: created, updated, unsubscribed, added to group, and removed from group. With webhooks enabled, changes in MailerLite reach your site in seconds instead of waiting for a member's next login. Enable and disable them from the connector's webhook settings; the general mechanics are covered in Webhooks.

Magic links and the new-member automation

Torii can write a member's magic login link into a MailerLite field, and that field is the recommended trigger for your new-member automation.

Set the Magic Link Sync Field in the connector settings to a text field on the MailerLite side. Whenever a magic link is generated for a member, it lands in that field on their subscriber record. Then build your welcome automation with a field-updated trigger on that field: when the link arrives, the automation sends the welcome email, merging the link into it. The member clicks, and they're in.

One MailerLite behavior to know before you build: an automation runs once per subscriber unless you set it to repeat. For the welcome automation that's exactly what you want, a member should get one welcome email. If you later reuse the same pattern for link regeneration, enable repeating on that automation or it will silently do nothing the second time.

Setup

  1. Generate an API token in your MailerLite account (Settings → API keys). MailerLite uses a single static token, no OAuth handshake.
  2. Paste the token into the MailerLite connector settings and click Save & Test Connection.
  3. Click Sync Tags to pull your MailerLite groups in as available tags, and Sync Custom Fields for the field list.
  4. Map your local tags to groups and your local fields to MailerLite fields, the same two-layer mapping as every connector.
  5. Enable webhooks if you want MailerLite changes to reach the site immediately.

The connection screen also shows account statistics (subscriber and group totals) so you can confirm at a glance that you connected the right account.

Shortcodes

[module-shortcodes: no shortcodes tagged mailerlite]