Skip to content
Marketing ⇄ CRM

Salesforce Marketing Cloud to Twenty CRM integration — real-time, two-way sync

Keep Salesforce Marketing Cloud and Twenty CRM in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Salesforce Marketing Cloud and Twenty CRM

Keep the people you sell to and the people you market to in one shared view: Twenty CRM and Salesforce Marketing Cloud sync contacts, accounts, and engagement in real time, in both directions.

Twenty CRM owns the customer relationship and the pipeline; Salesforce Marketing Cloud runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.

Stacksync syncs Attachments, Workspace Members, People, Companies in Twenty CRM with Contacts / Subscribers, Journeys (Journey Builder), Content Assets (Content Builder), Automations (Automation Studio) in Salesforce Marketing Cloud field by field, in real time, and in both directions. You decide which system owns which fields — Twenty CRM can own account and opportunity status while Salesforce Marketing Cloud owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Push product usage or billing data from a warehouse into Twenty custom fields to give reps account context.
  • 02 Sync Opportunities into a finance system to keep revenue forecasts current.
  • 03 Land tracking events - Sent, Open, Click, Bounce, Unsubscribe - from the SOAP tracking objects or Automation Studio Data Views into a warehouse table for per-send deliverability reporting.
  • 04 Sync Contacts and Subscriber Key subscription status between Marketing Cloud and a CRM so suppression and opt-in state stay current before the next send.

Common sync patterns

Where Salesforce Marketing Cloud captures engagement: activity lands on the record

Opens, clicks, form fills, event attendance, or ad responses recorded in Salesforce Marketing Cloud post back to the contact or account in Twenty CRM, so reps see interest before they reach out.

Lead and lifecycle status agree

Status, stage, or score set in one system updates the matching record in the other, so a lead marketing is still nurturing is not worked as sales-ready, and a closed account stops receiving prospecting.

Segments and audiences follow the CRM

Where Salesforce Marketing Cloud builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Twenty CRM, so who receives a campaign reflects current pipeline reality instead of a stale export.

What you can sync between Salesforce Marketing Cloud and Twenty CRM

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Salesforce Marketing Cloud objects Twenty CRM objects How this pairing syncs
Journeys (Journey Builder) Multi-step automated flows read and managed via /interaction/v1/interactions; contacts are injected by firing an entry event to /interaction/v1/events with an EventDefinitionKey and contact data. Companies Account-level records that group people and opportunities. Journeys (Journey Builder) is specific to Salesforce Marketing Cloud and Companies to Twenty CRM — each maps to any object or custom field on the other side.
Content Assets (Content Builder) Emails, templates, images, and reusable content blocks stored in Content Builder and read or written via /asset/v1/content/assets, used to compose the messages a journey or send delivers. Opportunities Deal records tracked through pipeline stages, synced for forecasting. Content Assets (Content Builder) is specific to Salesforce Marketing Cloud and Opportunities to Twenty CRM — each maps to any object or custom field on the other side.
Automations (Automation Studio) Scheduled or triggered workflows of import, query, extract, and send activities managed via /automation/v1/automations; SQL Query Activities read Data Views and write results into Data Extensions. Tasks To-dos linked to people, companies, or deals. Automations (Automation Studio) is specific to Salesforce Marketing Cloud and Tasks to Twenty CRM — each maps to any object or custom field on the other side.
Tracking Events Sent, Open, Click, Bounce, Unsubscribe, and NotSent events retrieved through the SOAP tracking objects (SentEvent, OpenEvent, ClickEvent, BounceEvent) or the Automation Studio Data Views (_Sent, _Open, _Click, _Bounce) - the queryable record of engagement per send. Notes Free-form notes attached to records, useful for mirroring activity from other tools. Tracking Events is specific to Salesforce Marketing Cloud and Notes to Twenty CRM — each maps to any object or custom field on the other side.
Transactional Sends Triggered and transactional Email/SMS delivered through the Messaging API (/messaging/v1/email/messages/{key}); the Event Notification Service reports each message's disposition (delivered, bounced, opened, clicked). Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. Transactional Sends is specific to Salesforce Marketing Cloud and Custom Objects to Twenty CRM — each maps to any object or custom field on the other side.
Data Extensions Custom relational tables that store subscriber, audience, and arbitrary business data; rows are read via GET /data/v1/customobjectdata or SOAP Retrieve and upserted via the synchronous rowset PUT or the async /data/v1/async/dataextensions rows endpoint. This is the primary two-way surface. Attachments Files linked to records. Data Extensions is specific to Salesforce Marketing Cloud and Attachments to Twenty CRM — each maps to any object or custom field on the other side.

How changes propagate between Salesforce Marketing Cloud and Twenty CRM

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Salesforce Marketing Cloud Twenty CRM Sub-second propagation

DetectionSalesforce Marketing Cloud notifies Stacksync of record changes through webhook events. The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback.

DeliveryEach detected change is written to Twenty CRM through its API, with automatic retries and rate-limit backoff.

Twenty CRM Salesforce Marketing Cloud Sub-second propagation

DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.

DeliveryEach detected change is written to Salesforce Marketing Cloud through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Salesforce Marketing Cloud: Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
  • Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Salesforce Marketing Cloud ⇄ Twenty CRM

Connect Salesforce Marketing Cloud and Twenty CRM for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce Marketing Cloud–Twenty CRM connection.

Real-time

Two-way sync

Changes in Salesforce Marketing Cloud or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Salesforce Marketing Cloud or Twenty CRM data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Salesforce Marketing Cloud or Twenty CRM record.

Observability

Monitoring

Track your Salesforce Marketing Cloud ⇄ Twenty CRM sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Salesforce Marketing Cloud and Twenty CRM.

How the Salesforce Marketing Cloud and Twenty CRM connectors work

Salesforce Marketing Cloud

Integration surface
Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
Authentication
OAuth 2.0 via an Installed Package (Client ID + Client Secret). Server-to-server uses the client_credentials grant and web apps use authorization_code, both against {subdomain}.auth.marketingcloudapis.com/v2/token. The 20-minute access token response also returns the account's rest_instance_url and soap_instance_url.
Change detection
The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback URL and subscription are registered and verified. There is no general data-change feed, so Data Extension and Data View syncs poll by date fields.
Capabilities
read · write · webhooks
Rate limits
Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.

Twenty CRM

Integration surface
GraphQL and REST APIs
Authentication
API key
Change detection
Webhooks on record create, update, and delete events, or polling on record update timestamps
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works

How to connect Salesforce Marketing Cloud to Twenty CRM — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Salesforce Marketing Cloud and Twenty CRM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Salesforce Marketing Cloud connected
    Twenty CRM connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Salesforce Marketing Cloud and Twenty CRM objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Salesforce Marketing Cloud ⇄ Twenty CRM
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Salesforce Marketing Cloud Twenty CRM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Salesforce Marketing Cloud and Twenty CRM integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 395 integrations available for Salesforce Marketing Cloud and Twenty CRM.

Popular · 8 of 395
All Salesforce Marketing Cloud integrations All Twenty CRM integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own