Skip to content
Marketing ⇄ CRM

Rollworks to Salesforce integration — real-time, two-way sync

Keep Rollworks and Salesforce 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 Rollworks and Salesforce

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

Salesforce owns the customer relationship and the pipeline; Rollworks 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 Custom Objects, Accounts, Contacts, Leads in Salesforce with Campaigns, Ad Groups and Ads, Reporting and Attribution, Target Account Lists in Rollworks field by field, in real time, and in both directions. You decide which system owns which fields — Salesforce can own account and opportunity status while Rollworks owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • 02 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
  • 03 Read campaign delivery and attribution metrics from the GraphQL Reporting API into Postgres or a warehouse for pipeline and spend reporting.
  • 04 Activate high-intent accounts by writing them into a Target Account List tier when a product or intent signal fires in an operational database.

Common sync patterns

Where Rollworks generates leads: hand-off without re-keying

New leads or responders captured in Rollworks flow into Salesforce assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.

New and updated people stay in step

When a contact or lead is created or edited in either system, the matching record appears or updates in the other, so campaigns reach real people and reps see who is already being marketed to.

Where Rollworks captures engagement: activity lands on the record

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

What you can sync between Rollworks and Salesforce

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.

Rollworks objects Salesforce objects How this pairing syncs
Campaigns Prospecting v2 campaigns running on Web and LinkedIn with budget, KPI, and flight settings; created and edited via API and read back for status and pacing. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Target Account Lists Named lists of B2B accounts for ABM; managed through /audience/v1/target_accounts so a CRM or warehouse can push and reconcile the accounts RollWorks advertises against. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Target Account Lists is specific to Rollworks and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
Account Tiers Groups within a Target Account List; an account belongs to only one tier per list, so tier assignments are written from source-of-truth data to drive tiered targeting. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Account Tiers is specific to Rollworks and Custom Objects to Salesforce — each maps to any object or custom field on the other side.
Accounts (TAL Items) Individual accounts identified by domain; added or removed via the tier items endpoint (POST/DELETE) so an operational database can control which domains are targeted. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Accounts (TAL Items) is specific to Rollworks and Accounts to Salesforce — each maps to any object or custom field on the other side.
Audience Segments CRM (email), custom (cookie or ID), and lookalike segments created via /audience/v1/segments; membership is written from a warehouse with a duration of 1 to 540 days. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Audience Segments is specific to Rollworks and Contacts to Salesforce — each maps to any object or custom field on the other side.
Ad Groups and Ads Campaign subdivisions carrying attribute, contextual, geo, and device targeting plus creative; read and written to keep targeting aligned with an internal planning system. Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. Ad Groups and Ads is specific to Rollworks and Leads to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Rollworks and Salesforce

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.

Rollworks Salesforce Interval-based propagation

DetectionStacksync polls Rollworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule.

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

Salesforce Rollworks Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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

Rate-limit considerations

  • Rollworks: NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Rollworks ⇄ Salesforce

Connect Rollworks and Salesforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Rollworks–Salesforce connection.

Real-time

Two-way sync

Changes in Rollworks or Salesforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Rollworks or Salesforce 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 Rollworks or Salesforce record.

Observability

Monitoring

Track your Rollworks ⇄ Salesforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Rollworks and Salesforce.

How the Rollworks and Salesforce connectors work

Rollworks

Integration surface
REST APIs (Audience, Prospecting v2) plus a GraphQL Reporting API
Authentication
OAuth 2.0 via NextRoll (Authorization Code grant, Bearer tokens per RFC 6749/6750); Personal Access Tokens supported for server-side scripts
Change detection
Polling — reporting is pulled via GraphQL queries and account/audience membership is reconciled on a schedule; no change webhooks or CDC feed is published
Capabilities
read · write
Rate limits
NextRoll does not publish explicit rate limits; access tokens expire 24 hours after issue and refresh tokens rotate on use, so long-running syncs must keep refreshing credentials.

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Rollworks to Salesforce — 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 Rollworks and Salesforce 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
    Rollworks connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Rollworks and Salesforce 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 · Rollworks ⇄ Salesforce
    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
    Rollworks Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Rollworks and Salesforce 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 401 integrations available for Rollworks and Salesforce.

Popular · 7 of 401
All Rollworks integrations All Salesforce 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