---
name: mailerlite-email-marketing
description: "Audit and operate MailerLite forms, subscribers, campaigns and multilingual nurture automations. Use for mailerlite email marketing tasks; select only the requested methods."
metadata:
  version: "1.0.0"
---

# MailerLite Email Marketing

Audit and operate MailerLite forms, subscribers, campaigns and multilingual nurture automations.

## OLLIE Runtime integration

Use relevant methods under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts, account identity, goals, permissions and required inputs. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for execution ownership and completion. This skill introduces no scheduler, independent permission policy or competing Runtime owner.

Discover the active Workspace’s approved capabilities before choosing API or browser access. Use Outloop for external service actions and the host’s supported tools for local artifacts. A product name in this package is not an access grant. Never import private account configuration or follow a source method that bypasses host restrictions. Apply the current task’s authorization; a library update does not grant permission to send, publish or activate a campaign.

## Required inputs

- Account and product edition
- Audience consent and suppression rules
- Form and automation objective
- Approved copy, sender and destinations

Use for MailerLite architecture, subscriber imports, form delivery, campaign drafts, automation diagnosis and reporting. Use the general email-marketing skill for cross-provider planning.

## Choose the requested mode

- **Audit:** inventory fields, groups, segments, forms, automations and sending-domain status from the actual account. Record IDs only in the private workspace. Identify Classic versus current MailerLite and verify plan-dependent controls before promising a feature.
- **Audience/import:** read [audience operations](references/audience.md). Define fields before mapping import data, reconcile group membership separately from subscriber status, and report partial failures.
- **Forms/nurture:** read [form and automation behavior](references/automations.md). Work backwards from whether the outcome should happen on first signup, each submission or a qualifying field change.
- **Campaign/translation:** read [content and localization](references/content.md). Build a draft, verify the saved version, then apply only the requested activation or delivery action.
- **Report:** compare recipient, delivered, click, bounce and unsubscribe counts over the same period; show denominators. Treat opens as an imperfect signal. A created campaign is not a sent campaign.

Read [official source links](references/sources.md) when confirming product behavior or API shapes. Prefer current account evidence over remembered UI paths. If the API cannot perform the required operation, discover whether an approved browser capability covers it; never infer access from another client’s setup.

## Completion

Verify findings against source evidence and read back every resulting artifact or authorized change. Distinguish a saved draft, queued job, active workflow and completed delivery. Return the requested outcome, evidence, output location and precise outstanding dependencies. Complete independent work when one dependency is unavailable. Package validation and synthetic fixtures do not establish real host import or provider execution.

Read [evaluation scenarios](references/evaluation.md) when testing this skill.