--- title: "Campaign Monitor Integration" description: "Manage Campaign Monitor audiences from your flows. Agents sync signups into subscriber lists with custom fields and consent tracking, update and unsubscribe subscribers as records change elsewhere, provision new lists, and review sent and draft campaigns." url: https://flowrunner.ai/integrations/campaign-monitor date_modified: 2026-08-01T02:40:32-07:00 --- # Campaign Monitor [Email Marketing](https://flowrunner.ai/integrations/category/email-marketing) Manage Campaign Monitor audiences from your flows. Agents sync signups into subscriber lists with custom fields and consent tracking, update and unsubscribe subscribers as records change elsewhere, provision new lists, and review sent and draft campaigns. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 10 actions · Basic auth · available [Campaign Monitor website](https://campaignmonitor.com/) · [Platform Documentation](https://www.campaignmonitor.com/api/v3-3/) · Capability data verified 2026-07-27 1. A new customer completes checkout in the storefront 2. List Lists resolves the client's marketing list for the right brand 3. Get Subscriber checks whether the address already exists and in what state 4. Agent reads the subscription state, because an address showing Unsubscribed is a recorded opt-out, not a data gap 5. The list owner rules on any add that would resubscribe a previously opted-out address, since overriding recorded consent is a compliance decision, not a sync step 6. Add Subscriber enrolls clean addresses with custom fields and consent-to-track set from the signup context 7. The day's enrollment log posts with adds, updates, and held addresses ## What This Integration Enables An email list is a set of permissions wearing the costume of a spreadsheet. Campaign Monitor tracks those permissions precisely, Active, Unconfirmed, Unsubscribed, Bounced, Deleted, and the platforms feeding it mostly ignore them, which is how compliant companies end up sending to people who said stop. This connector makes FlowRunner agents permission-aware audience clerks: they sync signups into lists with custom fields and GDPR consent-to-track, update records as source systems change, honor opt-outs immediately, provision lists with confirmed opt-in, and read send history for reporting. For agencies running multiple brands under one account, the client-scoped model means a single set of flows maintains every brand's audience to the same standard. - Enroll signups with custom fields and consent settings from the capture context - Check subscription state before any write that could override it - Update names, emails, and fields as records change elsewhere - Execute unsubscribes the moment an opt-out signal fires anywhere in the stack - Provision lists per brand or campaign, with double opt-in where policy requires - Report send history and draft inventory across clients ### Without FlowRunner **Lists grow by CSV import**: Signups pile up in forms and storefronts until someone runs the monthly upload **Consent state is guesswork**: Whether an address opted out, bounced, or was deleted lives in a column nobody checks before importing **Each brand's audience drifts separately**: Multi-client accounts mean multiplying manual list maintenance by every brand ### With FlowRunner **Lists grow in real time**: Every signup lands with custom fields and consent tracking the hour it happens **Consent is checked before writing**: Agents read subscription state first and route resubscribe decisions to a person **One flow serves every client**: Client-scoped operations handle each brand's lists from the same automation ## Use Case Scenarios ### Storefront to segmented list, consent intact A new order fires from [Shopify](https://flowrunner.ai/integrations/shopify). The agent resolves the brand's client with List Clients, finds the customer list, and calls Add Subscriber with the shopper's name, purchase-derived custom fields, and consent-to-track reflecting what the checkout actually captured. Addresses whose Get Subscriber state shows a prior opt-out are held for the list owner instead of silently re-added. The list grows daily, and every address on it can survive an audit. ### The opt-out that propagates in minutes A customer replies "unsubscribe" to a support thread, or toggles a preference in the account portal. The agent calls Unsubscribe Subscriber against the relevant list, and the client's suppression settings decide whether the address is blocked across all lists. The action logs to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with the source and timestamp, so the compliance trail shows the opt-out honored the same day it was voiced, wherever it was voiced. ### Send history without the screenshot ritual Monday morning, the agent runs List Sent Campaigns for each client, pulls subject lines, sent dates, and recipient counts, and posts the recap to [Slack](https://flowrunner.ai/integrations/slack) while archiving rows to the reporting sheet. List Draft Campaigns runs alongside so the team also sees what is staged but unsent, the campaign someone built and forgot. Agencies running multiple brands get one digest across every client, assembled by nobody. ## Human-in-Loop Highlight Add Subscriber with Resubscribe enabled will re-add an address whose state is Unsubscribed, which means a sync flow configured carelessly can convert a recorded opt-out back into a recipient, at scale, without anyone deciding to. That is the costliest write in this connector: not because it breaks data, but because it breaks a promise the law cares about. So FlowRunner enrollment flows never enable Resubscribe as a default. When a source system pushes an address whose Get Subscriber state shows Unsubscribed, the agent stops and presents the case: "jordan@example.com opted out of the Retail list in March; the POS now shows a new purchase with a marketing checkbox ticked. Resubscribe?" The list owner, who can weigh whether that checkbox constitutes fresh consent, decides. The same discipline applies to Unsubscribe Subscriber where client settings suppress across all lists: the agent names the blast radius before the call runs, so a one-list removal is never silently a five-list one. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 10 actions ### Clients 1 - **List Clients** Lists the account's clients, each a separate business or brand with its own lists and campaigns. Supplies the ClientID that scopes every other operation. ### Lists 3 - **List Lists** Lists a client's subscriber lists with IDs and names. The resolution step before subscriber operations. - **Create List** Creates a subscriber list for a client, optionally with confirmed double opt-in requiring a confirmation click. The provisioning step when onboarding a brand or campaign. - **Get List** Retrieves a list's full details: title, unsubscribe settings, confirmed opt-in configuration, and confirmation success page. ### Subscribers 4 - **Add Subscriber** Adds a subscriber with custom fields and GDPR consent-to-track, updating existing records when Resubscribe is enabled. Field keys must already exist on the list. The write FlowRunner gates when it would override a recorded opt-out. - **Get Subscriber** Retrieves a subscriber by email with name, subscription state (Active, Unconfirmed, Unsubscribed, Bounced, Deleted), join date, and custom field values. The consent check that fronts every write. - **Update Subscriber** Updates a subscriber identified by current email: name, custom fields, consent settings, or the email address itself. Only supplied fields change. - **Unsubscribe Subscriber** Unsubscribes an address from a list; client settings may suppress it across all of the client's lists. The opt-out executor, run the moment the signal fires. ### Campaigns 2 - **List Sent Campaigns** Lists a client's sent campaigns with name, subject, sent date, web version URL, and total recipients. The send-history read behind recaps and audits. - **List Draft Campaigns** Lists a client's unsent drafts with name, subject, and creation date. The staging inventory that surfaces prepared but forgotten campaigns. ## Frequently Asked Questions ### What can FlowRunner do with Campaign Monitor? FlowRunner agents can run List Clients, List Lists, and Create List in Campaign Monitor, plus 7 more actions. ### Does connecting Campaign Monitor to FlowRunner require OAuth? No. Campaign Monitor connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Campaign Monitor trigger a FlowRunner workflow automatically? Campaign Monitor doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Campaign Monitor?** This integration exposes Campaign Monitor to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/campaign-monitor. Site index: https://flowrunner.ai/llms.txt