Integration
Connect Campaign Monitor to Clerk
When something happens in Campaign Monitor, your agent does the next thing in Clerk. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Campaign Monitor and Clerk to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Campaign Monitor can start in Clerk
When New client in Campaign Monitor
then Create Invitation in Clerk
When New list in Campaign Monitor
then Create User in Clerk
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Campaign Monitor and Clerk
Triggers and actions 3 triggers · 21 actions
Trigger
New clientPolling trigger. Fires when a new client is added to the account.
Trigger
New listPolling trigger. Fires when a new list is added to the specified client.
Trigger
New subscriberPolling trigger. Fires when a new active subscriber is added to the specified list.
Action
Add campaignCreate a draft campaign.
Action
Add or update subscriberAdds a subscriber to the specified list if the email is not found, otherwise updates the existing subscriber.
Action
Create listCreates a new subscriber list for the specified client.
Action
Delete listDelete a list.
Action
Delete subscriberDelete a subscriber from a list.
Action
Get listGet details of a list.
Action
Get subscriberRetrieves a subscriber's details (including custom fields and state) by email from the specified list.
Action
List campaignsList sent campaigns for a client.
Action
List draft campaignsLists a client's draft (unsent) campaigns.
Action
List listsList all subscriber lists for a client.
Action
List segmentsList segments for a list.
Action
List subscribersList active subscribers of a list (paginated).
Action
UnsubscribeRemoves a subscriber from the specified list.
Action
Update listUpdate list settings.
Action
Update subscriber multi-select fieldUpdates a subscriber's multi-select custom field. Existing selected values can be retained or replaced.
Action
Ban UserBan a user, preventing them from signing in.
Action
Create InvitationInvite a new user to the Clerk instance by email; they receive a sign-up link.
Action
Create UserCreates a new user in Clerk.
Action
Delete UserDeletes a user from Clerk.
Action
Unban UserRemove a ban on a user, restoring their ability to sign in.
Action
Update UserUpdates an existing user in Clerk.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Campaign Monitor
Campaign Monitor to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Campaign Monitor to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Campaign Monitor to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Campaign Monitor to Google SheetsGoogle Sheets
Campaign Monitor to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Campaign Monitor to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Clerk
Kit to ClerkKit is an email marketing platform for professional bloggers.
HubSpot to ClerkHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ClerkSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ClerkSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ClerkGoogle Sheets
Gmail to ClerkGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Campaign Monitor and Clerk, answered
What can start an automation from Campaign Monitor?
Any of Campaign Monitor's 3 triggers in the catalog, including New client, New list and New subscriber. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Clerk when something happens in Campaign Monitor?
Any of Clerk's 6 actions, including Create Invitation, Create User, Update User and Ban User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Clerk to Campaign Monitor?
Clerk has no triggers in the catalog today, so automations start in Campaign Monitor. If you need the other direction, ask: your agent reads Clerk's API documentation and adds it.
Do I have to build a connector for Campaign Monitor or Clerk?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.