Weave Code
Statamic Mailerlite Laravel Package
concept7/statamic-mailerlite
Statamic MailerLite integrates your site with MailerLite, letting you connect newsletter signups and manage subscribers from Statamic. A simple addon for syncing forms and audience data without extra glue code.
A Statamic addon that automatically subscribes form submissions to MailerLite, with per-form configuration for subscriber groups and field mapping manageable from the Control Panel.
Frequently asked questions about Statamic Mailerlite
- How do I install concept7/statamic-mailerlite in a Laravel Statamic project?
- Install it with Composer using composer require concept7/statamic-mailerlite; the addon's service provider is auto-discovered, so no manual registration is required. After installing, publish the addon's config and assets and add your MailerLite API token to the published configuration. Then configure the target subscriber groups and field mappings per form in the Statamic Control Panel. The setup is configuration-driven and should fit a standard form-to-list workflow within a single sprint.
- Does this package work with Laravel without Statamic?
- No. concept7/statamic-mailerlite is a Statamic v3/v4 addon that hooks into Statamic's form submission lifecycle, so a Statamic installation is a hard requirement. It is not a general-purpose Laravel MailerLite client and should not be evaluated as one. If Statamic is not your CMS layer, use the official MailerLite SDK or the API directly instead.
- Can one Statamic form submission subscribe a person to multiple MailerLite groups?
- Yes, as of release 0.0.5 the addon supports multi-group selection, so a single submission can place a subscriber into several MailerLite groups rather than just one. That covers segmentation cases such as newsletter plus product interest plus region without custom event listeners or duplicate submissions. On earlier 0.0.x releases you would have needed glue code to fan out into multiple groups.
- Which Statamic and Laravel versions does this MailerLite addon support?
- The package is described as a Statamic v3/v4 addon, so it targets those CMS majors on a compatible Laravel version. Because it is still pre-1.0, it likely tracks recent Statamic releases rather than the full range, so confirm compatibility with your pinned Statamic minor before upgrading. Test the install against your exact Laravel and Statamic versions in staging instead of assuming support.
- Is concept7/statamic-mailerlite safe to use in production?
- It can run in production, but treat it as pre-1.0 software: at 0.0.5 there is no semver contract, so minor bumps may carry breaking configuration changes. Pin the exact version in composer.json and upgrade deliberately on a branch rather than floating the constraint. Budget for the possibility of forking too, since it is a single-maintainer package with a small install base and no visible long-term support commitment.
- Does upgrading to 0.0.5 break my existing group configuration?
- Moving from a single group to multi-group selection almost certainly changes the stored value from a scalar group ID to an array, which can affect published YAML configs and any templates reading that value. Diff the published config file between 0.0.4 and 0.0.5 in staging to identify renamed or reshaped keys, such as group becoming groups. Then search your forms and content YAML for the old field and migrate scalar values to arrays if needed. It is not documented whether the old scalar form is still accepted, so verify before deploying.
- How do I map Statamic form fields to MailerLite subscriber fields?
- Field mapping is configured per form in the Statamic Control Panel, where you match your form's field handles to MailerLite subscriber fields alongside the target group or groups. That keeps mapping out of your templates and lets each form write a different shape of data to MailerLite. No extra glue code is needed for standard field-to-field mapping.
- Are MailerLite subscriptions sent synchronously during form submission?
- The addon is a thin wrapper over the MailerLite API, so request behaviour is bounded by MailerLite limits, rate limiting, and token lifecycle, with little resilience layered on top. It is not documented whether a multi-group write is a single API call or N sequential calls per submission, and that directly affects form latency and rate-limit exposure. Run a real submission against a MailerLite test account and measure the latency before going live.
- What happens if a MailerLite group is deleted or invalid?
- The failure behaviour is not documented, so it is unclear whether an invalid or deleted group causes partial success, a full rollback, or a silent skip. Because the package offers limited resilience over the API, assume a failed group write may not surface clearly to the visitor. Test the scenario explicitly against a MailerLite test account and add your own logging or error handling if losing a subscriber matters.
- Is concept7/statamic-mailerlite actively maintained and tested?
- It is a single-maintainer package from concept7 with one contributor, a small install base, and no visible long-term support commitment, so the bus factor is one. There is no clearly documented test coverage or CI, which means you should validate behaviour yourself in staging. Plan for the possibility of forking or vendoring the addon if it stalls.
Weaver
How can I help you explore Laravel packages today?