Ship customer-facing integrations faster
Build once and publish to many customers.
Salesforce Marketing Cloud Connector
Build in-app integrations that upsert Data Extension rows, trigger transactional sends and subscribe to delivery events so customers can run email, contact and journey workflows without leaving your product.
Governed, reusable orchestration
Centralize logic and enforce MCP controls.
Reduce engineering work
Re-use connector methods across products and tenants.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
What teams can integrate or automate
Teams can read and write Contacts and Data Extension records, trigger transactional emails and use Automations and Journeys via the Marketing Cloud REST and SOAP APIs. Use Cyclr to embed those capabilities so customers upsert Data Extension rows, fire API-triggered sends and receive delivery webhooks natively in your app.
PRODUCT USE CASES
Top Use Cases for Salesforce Marketing Cloud Integrations
Quickly create integrations between your SaaS application and Salesforce Marketing Cloud using Cyclr’s low-code builder. Publish integrations into your product through Cyclr’s embedded marketplace and let customers upsert Data Extension rows, send transactional messages and subscribe to ENS delivery events.
Sync leads and profiles into Data Extensions
Upsert user or lead records into Data Extensions (POST/PUT data/v1/async or sync endpoints) to power targeted campaigns.
Send transactional emails from your app
Trigger API‑driven transactional sends using Messaging endpoints (POST /messaging/v1/messageDefinitionSends/{key}/send) for receipts, passwords and alerts.
Subscribe to delivery and engagement events
Register Event Notification Service callbacks to receive send, bounce, open and click events for real‑time orchestration.
ORCHESTRATION
How Salesforce Marketing Cloud works with Cyclr
Cyclr sits between your SaaS product and Salesforce Marketing Cloud to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Salesforce Marketing Cloud
Salesforce Marketing Cloud processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Salesforce Marketing Cloud methods you can orchestrate through Cyclr.
Data Events3
Upsert Custom Data Extension Rows
ActionCreates or updates a batch of data extension rows. Custom fields must be provided for both the request and response objects.
Upsert Data Extension Rows By Key
ActionCreates or updates a batch of data extensions rows by key.
Insert Data Extension Rows By ID
ActionCreates or updates a batch of data extensions rows by ID. We have provided some optional sample keys and values, you can add your own to the request in the format [].keys.mykey and [].values.myvalue. You can also map the key in the response [].keys.mykey.
Interaction1
Fire The Event
ActionFires the entry event that initiates the journey. Properties of the event can be added as custom request fields e.g. "Data.accountNumber".
Subscriber Lists3
Retrieve Lists
ActionRetrieves all lists.
Check Subscription
ActionChecks if a contact exists by data extension external key.
Add Subscribers To List
ActionAdds subscribers to the specified list.
Contacts3
Search Contacts
ActionFinds specified contacts based on provided attributes.
Update Contact
ActionUpdates a contact with the specified information in the specified attribute groups.
Create Contact
ActionCreates a new contact with the specified information in the specified attribute groups.
Transactional Email1
Send Transactional Email
ActionSends transactional email using Marketing Cloud's triggered send functionality. In order to use this service, configure a triggered send definition in Email Studio.
SMS1
Queue MO Message
ActionQueues an MO message for sending.
TECHNICAL DETAILS
Salesforce Marketing Cloud integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Salesforce Marketing Cloud integrations in Cyclr.
API and authentication
- API host
https://YOUR_SUBDOMAIN.auth.marketingcloudapis.com- Authentication
- OAuth 2.0 (Client credentials); OAuth 2.0 (Authorization code)
- Credentials
Client ID; Client Secret; tenant subdomain (auth host); optional Account ID or Is Sandbox flag
- Method categories
Data Extensions; Contacts; Messaging (triggered sends); Event Notification Service; Automations; Content Builder
Pagination and rate limits
Pagination
Data Extension and async-results endpoints use $page and $pageSize (default 50). Sendable Data Extensions can return up to 2,500 rows per page; non‑sendable endpoints are more limited.
Rate limits
No fixed public numeric limits. Marketing Cloud throttles per account and may return HTTP 429 with Retry-After; implement backoff and token reuse.
IMPLEMENTATION
Authentication at a glance
Marketing Cloud requires an Installed Package API integration and issues OAuth 2.0 tokens (POST /v2/token). Cyclr stores client_id/client_secret and uses returned REST/SOAP instance URLs; confirm the Cyclr Console OAuth flow option.
- Authentication method
- OAuth 2.0 (Client credentials); OAuth 2.0 (Authorization code)
- Credential required
Client ID; Client Secret; tenant subdomain (auth host); optional Account ID or Is Sandbox flag
Before you begin:
View setup guideRequires an Installed Package (API Integration) and tenant subdomain configuration in Cyclr.
COMMON QUESTIONS
Frequently asked questions
It automates Data Extension upserts, contact CRUD, API‑triggered sends and event subscriptions. Teams can push or pull Data Extension rows, fire transactional sends and subscribe to delivery events via ENS.
OAuth 2.0 is required. Create an Installed Package (API Integration) to get client_id and client_secret, request tokens at POST /v2/token and store returned rest_instance_url/soap_instance_url for API calls.
Yes. Use a central Installed Package or per‑customer credentials; Cyclr lets you store partner Client ID/Secret centrally or request credentials during installation to support multi‑tenant deployments.
Yes. Connector methods like Data Extension upserts and triggered sends can be published as reusable, governed MCP tools and embedded integration actions in Cyclr.
KEEP EXPLORING
Related resources and connectors
Documentation
Email Marketing Integrations to make your daily tasks easier
Read more →ProductCRM Integrations you should be using
Read more →ProductMCP PaaS
Read more →Related connectorAct!
Related Crms connector for customer-facing integration workflows.
Related connectorActiveCampaign
Related Crms connector for customer-facing integration workflows.
Related connectorGist
Related Crms connector for customer-facing integration workflows.