Skip to content
Human resources ⇄ CRM

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

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

Keep the people who own accounts in Salesforce in step with the workforce records in Namely, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Salesforce runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Namely. Namely is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.

Stacksync syncs Accounts, Contacts, Leads, Opportunities in Salesforce with Groups, Teams, Reports, Profile Fields in Namely field by field, in real time, and in both directions. You decide which system owns which fields, so Namely stays authoritative on roles and org structure while Salesforce keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
  • 02 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • 03 Feed Namely Reports as JSON into a database on a schedule for roster, turnover, and diversity dashboards without manual CSV exports.
  • 04 Provision or deprovision accounts in an IdP or directory when a Profile's user_status or start_date changes, and write the resulting user ID and email back onto the Profile.

Common sync patterns

Ownership and territory follow the org chart

When a person changes team, manager, or region in Namely, their accounts and territory assignments in Salesforce update to match, so pipeline stays with the right owner.

Deactivate access when someone leaves

When Namely marks a worker as departed, the matching user in Salesforce is flagged or deactivated, so former employees do not keep CRM access after their last day.

One directory of people

A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.

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

Namely objects Salesforce objects How this pairing syncs
Teams Teams and team categories a Profile belongs to; read and written for org-chart and provisioning workflows. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Teams is specific to Namely and Campaigns to Salesforce — each maps to any object or custom field on the other side.
Reports Saved Namely reports returned as JSON snapshots that update instantly; read-only feeds for headcount and roster analytics. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Reports is specific to Namely and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Profile Fields Metadata describing standard and company-defined custom field sections; read to discover schema and generate mappings. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Profile Fields is specific to Namely and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
Events Home-feed items such as announcements, birthdays, anniversaries, and new arrivals; typically read-only into comms tools. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Events is specific to Namely and Custom Objects to Salesforce — each maps to any object or custom field on the other side.
Profiles The core employee record (personal, job, contact, and compensation fields); synced two-way via GET/POST/PUT with updated_at driving incremental polling. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Profiles is specific to Namely and Accounts to Salesforce — each maps to any object or custom field on the other side.
Job Titles Job title definitions; read and written so titles stay aligned with an HRIS, directory, or reporting dimension. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Job Titles is specific to Namely and Contacts to Salesforce — each maps to any object or custom field on the other side.

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

Namely Salesforce Interval-based propagation

DetectionStacksync polls Namely for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks.

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

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

Rate-limit considerations

  • Namely: Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Namely ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Namely and Salesforce connectors work

Namely

Integration surface
REST API (JSON over HTTPS)
Authentication
OAuth 2.0 authorization-code grant, or a personal access token sent as a Bearer token; all calls run over HTTPS against https://{subdomain}.namely.com/api/v1
Change detection
No webhooks; integrations poll GET endpoints and compare the updated_at / created_at timestamps on Profiles and related objects to detect changes
Capabilities
read · write
Rate limits
Namely's public docs do not publish a fixed request quota; the REST API returns standard HTTP status codes, so integrations should throttle and back off on 429/5xx responses.

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

    Choose tables

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

Namely 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 434 integrations available for Namely and Salesforce.

Popular · 5 of 434
All Namely 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