> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MailerLite Webhook Setup Guide

> Configure MailerLite to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/mailerlite#getting-started) on the MailerLite connector page.

<section data-guide-section data-guide-scopes="">
  <h2>Automatic webhook setup</h2>

  <p>No manual configuration is required. When you connect your MailerLite account, StackOne automatically creates a webhook subscription in MailerLite that delivers the events listed below, and removes it again when you disconnect. Only the events you enable in StackOne are included in the subscription — MailerLite will not deliver events that are not subscribed.</p>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Available webhook events</h2>

  <p>The following MailerLite events can be enabled. Only events selected in StackOne are included in the subscription — MailerLite will not deliver events that are not subscribed.</p>

  <Steps>
    <Step title="Subscriber events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to subscribers on your account.</p>

        <ul>
          <li><strong>Subscriber Created</strong> (`subscriber.created`) — Fired when a new subscriber is added</li>
          <li><strong>Subscriber Updated</strong> (`subscriber.updated`) — Fired when an existing subscriber's data changes</li>
          <li><strong>Subscriber Unsubscribed</strong> (`subscriber.unsubscribed`) — Fired when a subscriber unsubscribes</li>
          <li><strong>Subscriber Added to Group</strong> (`subscriber.added_to_group`) — Fired when a subscriber is added to a group</li>
          <li><strong>Subscriber Removed from Group</strong> (`subscriber.removed_from_group`) — Fired when a subscriber is removed from a group</li>
          <li><strong>Subscriber Bounced</strong> (`subscriber.bounced`) — Fired when a subscriber's email address bounces</li>
          <li><strong>Subscriber Spam Reported</strong> (`subscriber.spam_reported`) — Fired when a subscriber marks a campaign as spam</li>
          <li><strong>Subscriber Automation Triggered</strong> (`subscriber.automation_triggered`) — Fired when a subscriber starts an automation</li>
          <li><strong>Subscriber Automation Completed</strong> (`subscriber.automation_completed`) — Fired when a subscriber finishes an automation</li>
          <li><strong>Subscriber Active</strong> (`subscriber.active`) — Fired when a subscriber's status is set to active</li>
        </ul>
      </div>
    </Step>

    <Step title="Campaign events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Events related to campaigns.</p>

        <ul>
          <li><strong>Campaign Sent</strong> (`campaign.sent`) — Fired when a campaign finishes sending</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

<section data-guide-section data-guide-scopes="">
  <h2>Delivery format</h2>

  <p>How MailerLite delivers events to StackOne.</p>

  <Steps>
    <Step title="Single and batched payloads">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>MailerLite delivers most events as a single JSON object. Some deliveries are batched — a payload containing an <strong>events</strong> array with a <strong>total</strong> count — in which case StackOne routes each event in the batch to its matching handler. Simple events carry the event name in an <strong>event</strong> field with the record at the root; group and automation events carry it in a <strong>type</strong> field with nested <strong>subscriber</strong> and related objects.</p>
      </div>
    </Step>

    <Step title="Events that require batch mode">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>The `subscriber.deleted`, `campaign.open`, and `campaign.click` events are not part of the default subscription — MailerLite only delivers them when a webhook is created in batch mode, which changes every payload into the batched `events` array format. StackOne still receives any such batched deliveries via its generic batch handler.</p>
      </div>
    </Step>
  </Steps>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.