Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Campaign Monitor

Email marketing platform for delivering exceptional email campaigns.

CategoryMarketing
Authenticationcustom
Version0.1.8
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Campaign Monitor with Flows360

Email marketing platform for delivering exceptional email campaigns.

Use the Campaign Monitor connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 3 triggers.

Available actions

  • Add Subscriber
  • Update Subscriber
  • Unsubscribe Subscriber
  • Find Subscriber

Available triggers

  • New Subscriber Added
  • Subscriber Unsubscribed
  • New Client

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Campaign Monitor
  • Package: @activepieces/piece-campaign-monitor@0.1.8
  • Exact artifact digest: sha256:40ea255e7bc9b6aa3e1b6e1e634967fd6e251821f353dc4b5e588d81058257c4
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Subscriber (add_subscriber_to_list), Adds a new subscriber to a list. Classification: read.
  • Update Subscriber (update_subscriber_details), Update an existing subscriber in a list. Classification: read.
  • Unsubscribe Subscriber (unsubscribe_subscriber), Remove a subscriber from a list. Classification: read.
  • Find Subscriber (find_subscriber), Find a subscriber by email in a specific list. Classification: read.

Trigger contracts

  • New Subscriber Added, webhook.
  • Subscriber Unsubscribed, webhook.
  • New Client, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions4
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Add Subscriber Yes No Adds a new subscriber to a list.
Update Subscriber Yes No Update an existing subscriber in a list.
Unsubscribe Subscriber Yes No Remove a subscriber from a list.
Find Subscriber Yes No Find a subscriber by email in a specific list.
New Subscriber Added Yes No webhook trigger declared by the pinned package.
Subscriber Unsubscribed Yes No webhook trigger declared by the pinned package.
New Client Yes No polling trigger declared by the pinned package.

Supported actions

Add Subscriber · Read

Adds a new subscriber to a list.

add_subscriber_to_list · Risk: low · Retry: safe

Inputs

  • clientId · string · Required
  • listId · string · Required
  • email · string · Required
  • name · string · Optional
  • phone · string · Optional
  • consentToTrack · string · Required, Whether the subscriber has consented to tracking.
  • consentToSendSms · string · Optional, Whether the subscriber has consented to send SMS.
  • resubscribe · boolean · Optional, If true, the subscriber will be resubscribed if they previously unsubscribed.
  • fields · object · Required
Update Subscriber · Read

Update an existing subscriber in a list.

update_subscriber_details · Risk: low · Retry: safe

Inputs

  • clientId · string · Required
  • listId · string · Required
  • email · string · Required
  • name · string · Optional
  • phone · string · Optional
  • consentToTrack · string · Optional, Whether the subscriber has consented to tracking.
  • consentToSendSms · string · Optional, Whether the subscriber has consented to send SMS.
  • resubscribe · boolean · Optional, If true, the subscriber will be resubscribed if they previously unsubscribed.
  • fields · object · Required
Unsubscribe Subscriber · Read

Remove a subscriber from a list.

unsubscribe_subscriber · Risk: low · Retry: safe

Inputs

  • clientId · string · Required
  • listId · string · Required
  • email · string · Required, The email address of the subscriber to unsubscribe.
Find Subscriber · Read

Find a subscriber by email in a specific list.

find_subscriber · Risk: low · Retry: safe

Inputs

  • clientId · string · Required
  • listId · string · Required
  • email · string · Required, The email address of the subscriber to find

Triggers

New Subscriber Added · Webhook

Triggered when a new subscriber is added to a list.

Inputs

  • clientId · string
  • listId · string
Subscriber Unsubscribed · Webhook

Triggered when a subscriber unsubscribes from a list

Inputs

  • clientId · string
  • listId · string
New Client · Poll

Triggered when a new client is added to Campaign Monitor.

Setup

Setup

  1. Add the Campaign Monitor connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-campaign-monitor@0.1.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Campaign Monitor connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-campaign-monitor@0.1.8 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com