Campaign Monitor connector
Your Silux Chat bot verifies customers against Campaign Monitor, then answers questions about their subscriptions and plans from your live data.
Good to know: Subscribers are keyed by email within one list.
What your bot can do with Campaign Monitor
Recognise and verify customers
Finds the customer in Campaign Monitor by the email address or mobile number they give, checks their name and one more detail, then sends a one-time code to the contact details Campaign Monitor holds. Nothing personal is shared until the code is entered.
Customers ask: “I want to check my account — it’s Jane Smith, jane@example.com”
Subscriptions and plans
Reads the verified customer’s plans or memberships in Campaign Monitor — plan, status and next billing date.
Customers ask: “When does my plan renew?” · “Is my subscription still active?”
Set it up
Most businesses finish in under ten minutes. You need to be able to sign in to Campaign Monitor as an administrator to create the key.
Step 1 — in Campaign Monitor
- 1Campaign Monitor
- 2Account settings
- 3API keys
- 4copy the API key; the List API ID is on the list's Settings page.
Least access: grant only the read permissions named above (customers, orders, invoices, bookings or tickets — whichever this connector uses). Never use an owner or full-admin key where Campaign Monitor lets you create a restricted one.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “Campaign Monitor”.
- 2Fill in:
Field Example Stored List API ID a58ee1d3039b8bec838e6d1482a8a965 Setting API key •••••••• Encrypted - 3Press Connect & test. The platform makes a real, read-only call to Campaign Monitor with a made-up customer and shows a tick or a cross for each capability, with Campaign Monitor’s exact error if something is refused.
- 4If this is your first way of verifying customers it is switched on automatically; otherwise press Use to verify customers. The platform then runs its chained test (verify → code → account → orders → invoices) with the built-in test customer — no real person is contacted.
Campaign Monitor identifies API users with a key-and-secret (or username-and-key) pair, sent with HTTP Basic authentication over HTTPS.
How customer verification works
- STEP 1
Customer asks
They ask about their own account. The bot asks for their full name and their email or mobile, plus one more detail such as their postcode.
- STEP 2
Found in Campaign Monitor
The customer is looked up in Campaign Monitor by email, then mobile. The surname must match exactly and the first name must match or start with the same letter, plus one more detail.
- STEP 3
Code sent
A 6-digit code goes to the mobile Campaign Monitor holds (by text, when your plan has SMS) or otherwise to the email it holds. The chat never chooses where it goes.
- STEP 4
Verified
The customer types the code. It is valid for 10 minutes and five wrong attempts cancel it. The verified session lasts 30 minutes.
If the details don’t match, the customer is told only that they couldn’t be matched — never which detail was wrong. If Campaign Monitor can’t be reached, the bot says it can’t check accounts right now rather than “no account found”. The bot is blocked in code from reading orders, invoices or bookings until verification succeeds. Full details: Customer identity verification & OTP.
What the bot can and cannot see
Can see (after verification)
- Record ID
- Name
- Email address
- Phone / mobile
- Plan
- Status
- Since
Only these standard fields are mapped from Campaign Monitor’s responses. Everything else in the response is discarded before the bot sees it.
Never sees
- passwords, security answers or login details
- records belonging to anyone other than the verified customer
- anything outside the fields listed alongside
Security
Keys encrypted at rest
Credentials are stored encrypted, shown only masked after saving, and destroyed — not just hidden — when you disconnect.
Read-only look-ups
Every capability is a look-up. The connector cannot create, change or delete anything in Campaign Monitor.
HTTPS only
Calls go to the vendor’s HTTPS address, redirects are not followed, and private network addresses are refused.
Injection-safe
Values a customer types are cleaned before they are placed in Campaign Monitor’s search, and URL-encoded in addresses.
Other customers filtered out
A row that names a different customer’s email is dropped, whatever the vendor’s search returned.
Checked daily
Connections are re-tested every day, and the owner is emailed if a working connection starts failing.
More: Security & data protection.
Technical details
For developers and IT teams: the Campaign Monitor endpoints this connector reads, relative to https://api.createsend.com/api/v3.3. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Recognise and verify customers | GET/subscribers/{list_id}.json | id, name, email, phone |
| Subscriptions and plans | GET/subscribers/{list_id}.json | id, plan, status, since |
Test level: Documented-API tested. Each capability is run automatically against Campaign Monitor’s documented example responses and must produce the standard fields; your own connection is then tested with a real call when you connect. The bot receives these through the standard Account Connect endpoints, exactly as if you had built them yourself.
Troubleshooting
| What you see | Likely cause and fix |
|---|---|
| “the vendor refused the credentials (401)” or (403) | The key was revoked, has expired or was copied incompletely, or it lacks a read permission this connector needs. Create a fresh read-only key in Campaign Monitor and reconnect. |
| “That List API ID doesn’t look right” | Enter it in the form shown, e.g. a58ee1d3039b8bec838e6d1482a8a965 — without https:// or a trailing slash. |
| Customers are “not matched” although they exist | Customers are looked up by email or mobile, not postcode. Check the customer’s email or mobile is saved on their Campaign Monitor record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in Campaign Monitor, or your Campaign Monitor plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | Campaign Monitor returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as Campaign Monitor asks); if it persists, ask Campaign Monitor about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in Campaign Monitor, or none are recent. Check the customer’s record in Campaign Monitor directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the Campaign Monitor connection read-only?
Yes. Every request Silux Chat makes to Campaign Monitor is a look-up; none creates, changes or deletes anything in Campaign Monitor. Give the key or sign-in read-only permissions wherever Campaign Monitor offers them.
Do I need a developer to connect Campaign Monitor?
No. You paste the details listed in the set-up steps in Dashboard → Integrations → Connectors and press “Connect & test”. The platform makes a real call to Campaign Monitor straight away and shows exactly which features work.
How does the bot know it is really my customer?
It finds the customer in Campaign Monitor by the email or mobile they give, checks their name and one more detail, then sends a one-time code to the mobile or email held in Campaign Monitor — never to one typed in the chat. The code lasts 10 minutes, five wrong attempts cancel it, and a verified session lasts 30 minutes.
What happens if my Campaign Monitor key is revoked or expires?
The bot tells customers it can’t check their account right now — it never pretends there are “no orders”. Connections are re-tested daily and the account owner is emailed when a working connection starts failing. Reconnect it in Dashboard → Integrations → Connectors.
How has the Campaign Monitor connector been tested?
It is Documented-API tested: every capability is run automatically against Campaign Monitor’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own Campaign Monitor account before your bot uses it.
Other marketing connectors
ActiveCampaign
Recognise and verify customers
Brevo (Sendinblue)
Recognise and verify customers
Kit (ConvertKit)
Recognise and verify customers · Subscriptions and plans
Klaviyo
Recognise and verify customers · Subscriptions and plans
Mailchimp
Recognise and verify customers
MailerLite
Recognise and verify customers · Subscriptions and plans
Omnisend
Recognise and verify customers · Subscriptions and plans
Need help with your integration?
Our integration team can review your endpoints, help you choose the right connector and check a test run with you. Tell us which system you use and what you would like the bot to answer.