Skip to content
Communications ⇄ CRM

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

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

Keep Salesforce and RingCentral working from the same contacts, and log every call, message, and meeting back on the record, in real time and in both directions.

Salesforce holds the people the business talks to: the contacts, their phone numbers and email addresses, and which rep owns the relationship. RingCentral is where the talking happens, whether that is calls, texts, email, or meetings. The two depend on the same people, and when the contact list in one drifts from the other, outreach goes to stale numbers and the record of what was said never makes it back to the account.

Stacksync syncs Tasks and Events, Products and Price Books, Custom Objects, Accounts in Salesforce with Extensions (Users), Contacts (Address Book), RingOut (Click-to-call), Team Messaging (Chat) in RingCentral field by field, in real time, and in both directions. Current contact details flow out to RingCentral so it can reach the right person, and the calls, messages, and meetings RingCentral produces flow back onto the matching record in Salesforce. You decide which system owns which fields, and conflicts resolve by rules you set.

Common use cases

  • 01 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
  • 02 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
  • 03 Place RingOut click-to-dial calls from a CRM or internal app so reps dial contacts without leaving their workflow.
  • 04 Two-way sync personal Address Book contacts so a rep's RingCentral contacts match the CRM and new CRM contacts appear in RingCentral.

Common sync patterns

Calls, messages, and meetings on the record

Activity handled in RingCentral appears on the matching contact and account in Salesforce, so the next person sees the full history without leaving the CRM.

Where RingCentral sends at scale: delivery and reply status back on the contact

Sends, bounces, opens, and replies from RingCentral update fields on the contact in Salesforce, so lead status reflects what actually reached the person.

One contact list, opt-outs included

A number, address, or unsubscribe recorded in either system updates the other, so no one calls a disconnected line or messages someone who opted out.

What you can sync between RingCentral 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.

RingCentral objects Salesforce objects How this pairing syncs
Presence Real-time presence and detailed telephony state per extension, read via GET presence and subscribed to for live updates, used to reflect agent availability and call status across systems. Read-only. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Presence is specific to RingCentral and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Subscriptions (Webhooks / WebSocket) Event subscriptions created through the Subscription API with eventFilters (message-store, presence, telephony sessions, extension changes); full CRUD, and the mechanism for near-real-time change delivery over webhooks or WebSocket. Read and write. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Subscriptions (Webhooks / WebSocket) is specific to RingCentral and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
Message Store (SMS / MMS / Fax / Voicemail) Messages in an extension's mailbox - SMS, MMS, fax, voicemail, and pager - read via GET /account/~/extension/~/message-store filtered by dateFrom/dateTo and messageType; outbound SMS is sent via POST /sms, MMS and fax via POST /fax, and messages can be marked read or deleted. Read and write. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Message Store (SMS / MMS / Fax / Voicemail) is specific to RingCentral and Custom Objects to Salesforce — each maps to any object or custom field on the other side.
Call Log Call detail records with direction, result, duration, from/to numbers, and recording references, from the account-wide and per-extension call-log endpoints, filtered by dateFrom/dateTo. Read-only records. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Call Log is specific to RingCentral and Accounts to Salesforce — each maps to any object or custom field on the other side.
Extensions (Users) User extensions with profile, status, roles, and assigned phone numbers via the Configuration API; create, update, and disable extensions to provision or deprovision users and map them to CRM, HR, or directory identities. Read and write. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Extensions (Users) is specific to RingCentral and Contacts to Salesforce — each maps to any object or custom field on the other side.
Contacts (Address Book) Personal address-book contacts per extension with full CRUD via POST/PUT/DELETE /address-book/contact; the company directory has no create endpoint and is read-only, so only personal contacts are writable. Read and write. Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. Contacts (Address Book) is specific to RingCentral and Leads to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between RingCentral 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.

RingCentral Salesforce Sub-second propagation

DetectionRingCentral notifies Stacksync of record changes through webhook events. Subscription API webhooks (with a validation-token echo handshake) or WebSocket subscriptions on eventFilters such as message-store/instant,.

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

Salesforce RingCentral 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 RingCentral through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • RingCentral: Per-user (extension) throttling groups per 60 seconds - Heavy 10, Medium 40 (e.g. /sms), Light 50, Auth 5 - as customizable defaults; exceeding returns HTTP 429 with a Retry-After header and X-Rate-Limit-Group/Limit/Remaining/Window headers.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with RingCentral ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the RingCentral and Salesforce connectors work

RingCentral

Integration surface
REST API (RingEX Platform API) on platform.ringcentral.com, base path /restapi/v1.0, with resources under account/~/extension/~/ (message-store, call-log, sms, fax, ring-out, address-book, presence, subscription) plus the Configuration API for provisioning
Authentication
OAuth 2.0 - authorization code flow (with PKCE) for user-facing apps, and JWT bearer flow for server-to-server integrations; the legacy password (ROPC) grant was retired on March 31, 2024
Change detection
Subscription API webhooks (with a validation-token echo handshake) or WebSocket subscriptions on eventFilters such as message-store/instant, presence, and telephony/sessions; historical pulls poll message-store and call-log on dateFrom/dateTo
Capabilities
read · write · webhooks
Rate limits
Per-user (extension) throttling groups per 60 seconds - Heavy 10, Medium 40 (e.g. /sms), Light 50, Auth 5 - as customizable defaults; exceeding returns HTTP 429 with a Retry-After header and X-Rate-Limit-Group/Limit/Remaining/Window headers
RingCentral setup guide

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 RingCentral 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 RingCentral 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
    RingCentral connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

RingCentral 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 441 integrations available for RingCentral and Salesforce.

Popular · 7 of 441
All RingCentral 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