- Content lifecycle: create content, clone it, publish and unpublish in one call each
- Variants: update or delete a content variant by id; items search across the CMS
- Content spaces and folders: list, create and update spaces, read a space or folder by id
- 13 routes (5 read-only) under /services/data/vXX.X/connect/cms on your org's My Domain instance URL
- Same Connected App credential as the other Salesforce core connectors; nothing stored in Apivom Atlas
Salesforce Marketing Cloud Next API Connector
Salesforce Marketing Cloud Next — the edition built on the Salesforce core platform — and its Connect CMS content API: create, clone, publish and unpublish content, manage variants, search items and organise content spaces and folders, registered in Apivom Atlas as 13 routes on your My Domain org.
What you can do
Use cases
- Publish approved content from one place — Create the content record, clone it per market and publish it when the CRM approval step completes, instead of repeating the steps in the Marketing Cloud Next UI.
- Keep variants aligned with product data — Update a content variant when the catalogue price or product name changes in the CRM, and unpublish items whose product has been retired.
- Content inventory next to the campaign — Search CMS items and list the spaces and folders a campaign uses, so the campaign record shows which assets are live and where they live.
Marketing Cloud Next is Salesforce's newer marketing edition, built directly on the core platform rather than on the separate Engagement stack, so its content lives in the org's CMS and is reached through the Connect REST API like any other Salesforce resource. The slice Apivom Atlas catalogues is that CMS content surface — 13 routes, 5 of them read-only: create a content record, clone it, publish and unpublish, update or delete a variant, search items, and list, create or update the content spaces and folders that hold them. The API base path is part of the route so the org's API version is chosen per call, and the My Domain instance URL is applied per request, which makes the connector usable against any org. The credential is a Connected App, identical to the Salesforce Platform connector. No Apivom product workflow uses Marketing Cloud Next today — Apivom's own marketing automation runs on Apivom's platform — so the connector is available to tenants on this edition who want CRM-driven content published or kept in step from an Apivom workflow, scoped per customer.
A Connected App on your Salesforce org (consumer key + secret) and your My Domain instance URL. The caller runs the OAuth 2.0 flow and sends the access token as Bearer; the instance URL becomes the per-request base URL. Apivom Atlas forwards, logs and stores nothing.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
Is this the same as Marketing Cloud Engagement?
No. Engagement is the subdomain-based platform at marketingcloudapis.com with its own REST/SOAP APIs and installed packages; it has a separate connector here with 116 routes. Marketing Cloud Next runs on the Salesforce core platform and is addressed through your org's My Domain with a Connected App.
Why only the CMS content routes?
They are the Marketing Cloud Next-specific surface Salesforce documents under the Connect REST API. Campaigns, flows, data model objects and other core-platform resources of the same org are covered by the Salesforce Platform connector in this catalogue.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.