Automatic webhook setup

StackOne creates and manages the Campaign Monitor webhooks automatically when the account is connected, and removes them when the account is disconnected. Campaign Monitor webhooks belong to a single subscriber list, so StackOne registers one webhook on each list in the Webhook List IDs field. The only thing to do by hand is choosing those lists.

The Campaign Monitor Log In page with the Email field, Password field, and LOG IN button highlighted

Click Lists & subscribers in the top navigation.

The Campaign Monitor client overview with Lists & subscribers highlighted in the top navigation

On the Lists and subscribers page, click the name of a list you want webhook events from.

The Lists and subscribers table with one list name highlighted

Click Settings in the list's left menu.

A subscriber list page with Settings highlighted in the left menu

Scroll to Notifications and API. Under List API ID, click Copy beside the ID.

You can also get list IDs from the connector's actions. Run `list_clients` for the client IDs, then `list_client_lists` with a client ID.

Repeat the last three steps for every list you want events from.

The list Settings page with the List API ID value and its Copy button highlighted

When you link the account in StackOne Hub, paste the list IDs into Webhook List IDs, separated by commas.

Webhooks don't appear on a list's Settings page in Campaign Monitor. To check the webhook StackOne registered, run the `list_webhooks` action with the list ID. Leftover webhooks can be removed with `delete_webhook`.

Lists that are not in this field send no events.
Each registered webhook is paired with its list when it is created. Disconnect the account before you change the list IDs, then reconnect it, so every webhook is removed from the list it was created on.

In the StackOne dashboard, open the Campaign Monitor connector profile and enable the webhook events you want delivered. See Available webhook events below for the full list.

StackOne subscribes each list's webhook to the enabled events only, so Campaign Monitor does not send events that are not selected.

Available webhook events

The following Campaign Monitor list events can be enabled. Only events selected in StackOne are included in the subscription — Campaign Monitor will not deliver events that are not subscribed.

Events related to subscribers on a list. Each event carries the subscriber's `EmailAddress`, which StackOne uses as the event ID, and the `ListID` of the list it happened on.

List Subscribe (`Subscribe`) — Fired when a subscriber is added to a list, whether entered manually, imported from a file, added through a subscribe form or the API, moved from inactive back to active, or confirmed through the verification link on a confirmed opt-in list
Subscriber Update (`Update`) — Fired when a subscriber's details change, whether edited in Campaign Monitor, re-imported, updated through the preference center, or re-added or updated through the API
Subscriber Deactivate (`Deactivate`) — Fired when a subscriber becomes inactive, after clicking an unsubscribe link, unsubscribing through the preference center, reporting spam, hard bouncing, or being unsubscribed through the API

Delivery format

Details of how Campaign Monitor delivers events to StackOne, from the Campaign Monitor webhooks documentation.

Each request is a JSON object with an `Events` array and the `ListID` of the list. Campaign Monitor batches events into one request wherever possible, up to 1,000 events. StackOne routes each event in the batch to its matching event handler on its own.

Campaign Monitor deactivates a webhook automatically when requests to it keep failing for more than a week.