MailerLite Connector

Connector status: In progress Being built. Not verified yet.

Illustration · sample data

Sync example

Review one record

Source

MailerLite

Connector status: In progress

Destination

Your other tool

Connector status: Custom tool

Source fieldDestination fieldSample value
record.id source_id record_1042
record.updated_at updated_at 2026-10-18T08:00:00Z
record.value value sample_value
  1. Draft
  2. Review one record
  3. Approve this version

Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.

Connector implementation

Build the MailerLite integration

Email marketing contacts, groups, campaigns, automations, and templates for migration into Brevo.

Migrate from
MailerLiteAPI / MCP / docsTajo connectorauth, mapping, syncretries, logs, checksBrevo activationcontacts, events, campaignsbackfill, webhooks, validation
MailerLite connector flow from source system to Tajo mapping and Brevo activation.

Implementation Overview

Build target

Implement a MailerLite connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.

Current status

Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.

Primary surface

developers.mailerlite.com/docs/

PropertyValue
Integration surfaceOpenAPI
StatusIn progress
CategoryMigrate from
Setup complexitymedium
Vendor documentationdevelopers.mailerlite.com/docs/
Allowed hostNot recorded
Base URLNot recorded
OpenAPI schemaNot recorded
MCP serverNot recorded
Last researched2026-05-10

Direct Brevo migration source from Claude marketplace list.

Authentication

  • Keep developers.mailerlite.com/docs/ linked from the connector runbook so operators can confirm vendor behavior during incidents.

  • Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.

  • Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.

Data To Sync

Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:

  • Contact and identity records
  • Campaign, messaging, or audience state

The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.

Sync Shape

ResourceDirectionConflict handling
subscribersbidirectionalsource_wins, loop guard none
groupsinboundn/a
fieldsinboundn/a

The account is the record of the subscriber’s consent; the write back (upsert_subscriber) states active only with a consent basis or unsubscribed to carry an opt-out, and never sends resubscribe, the reference’s only way to reactivate an unsubscribed subscriber.

Mapping To Tajo/Brevo

subscribers → Brevo contact

Requires: workspace api key.

Source fieldBrevo destinationViaNote
emailemail—
firstNameattributes.FIRSTNAME—
lastNameattributes.LASTNAME—
phoneattributes.PHONE—
companyattributes.COMPANY—
idattributes.MAILERLITE_ID—
createdAtattributes.MAILERLITE_CREATED_AT—
updatedAtattributes.MAILERLITE_UPDATED_AT—
statustajo_email_marketing_consent—active is consent; unsubscribed, bounced and junk are suppressions carried as such; unconfirmed is refused.

Read for context and not projected: groups, fields.

The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.

Sources

Request early access

Enter your first name and email address. We will email you a link to confirm your request for Tajo access.

AI Assistant

Hi! Ask me anything about the docs.

This page as Markdown: mailerlite.md

Loading Markdown…