MailerLite integration

What it does

The MailerLite integration lets your agency run a client's email marketing operation without leaving TaskJuice. Connect a client's MailerLite account once and you can list, create, or upsert subscribers, update a subscriber by ID, list and create groups, and list or draft campaigns against the new MailerLite API at connect.mailerlite.com. Two webhook triggers turn MailerLite activity into workflow runs covering subscriber creation and subscriber updates.

Connect a MailerLite account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose MailerLite and click Connect.
3. Sign in to the MailerLite account you want to manage on behalf of your client, open Integrations, and choose MailerLite API.
4. Generate a new API token, copy it, and paste the value into TaskJuice.
5. Save the connection. The token is stored encrypted and is sent on every action as a Bearer credential on the Authorization header.

To revoke access, sign in to MailerLite, open Integrations, choose MailerLite API, and delete the token. TaskJuice surfaces the resulting 401 on the next workflow run so you can rotate the credential.

Triggers

• mailerlite/subscriber-created fires when a new subscriber is created in MailerLite, with the subscriber object attached.
• mailerlite/subscriber-updated fires when an existing subscriber is updated, including status changes, profile edits, and group membership changes.

Actions

• mailerlite/list-subscribers pages through subscribers with optional filters by status (active, unsubscribed, unconfirmed, bounced, junk) and a free-text search.
• mailerlite/create-subscriber creates a new subscriber or upserts an existing one by email, with optional fields and group assignments.
• mailerlite/update-subscriber updates a subscriber by ID. Only fields you pass are touched.
• mailerlite/list-groups pages through groups (lists) with an optional name filter.
• mailerlite/create-group creates a new group in the connected account.
• mailerlite/list-campaigns pages through campaigns, optionally filtered by status (draft, ready, sent).
• mailerlite/create-campaign creates a draft campaign. Scheduling and sending remain in MailerLite for safety, so the action returns the draft for review.

Known limitations

• MailerLite API tokens are scoped to a single account. Each client needs its own connection and its own token.
• The MailerLite API enforces per-account rate limits and returns 429 with a Retry-After header when exceeded. The action engine retries 429 responses with backoff; high-volume cycles should pace work with a downstream throttle.
• Webhooks are signed with HMAC-SHA256 over the raw request body, and the base64 digest is sent in the X-MailerLite-Signature header. Use the same signing secret you configured in the MailerLite webhook when you register the trigger so the platform can verify every inbound POST before activating the workflow.
• Campaign creation produces a draft campaign. Sending or scheduling is a follow-up step in the MailerLite UI; the API supports it through additional fields not exposed in this integration's initial action set.
• Pagination is cursor-based on the cursor query parameter and the meta.next_cursor response field. Stop paging when meta.next_cursor is null.