Skip to content
Human resources ⇄ CRM

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

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

Keep the people who own accounts in Salesforce in step with the workforce records in Jobvite, 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 Jobvite. Jobvite 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 Products and Price Books, Custom Objects, Accounts, Contacts in Salesforce with Requisition (Job), Application, Workflow Status, New Hire in Jobvite field by field, in real time, and in both directions. You decide which system owns which fields, so Jobvite 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 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
  • 02 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
  • 03 Consolidate Applications, Offers, and Workflow Status into a warehouse for time-to-fill and funnel reporting across every requisition.
  • 04 Sync Employee roster data into Jobvite with POST /employee to power employee-referral matching and internal-mobility postings.

Common sync patterns

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.

Where Jobvite tracks people the business also engages: contacts stay in sync

A person recorded in Jobvite, such as a candidate or applicant, can create or update the matching contact in Salesforce, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

New team members provisioned when they are hired

When Jobvite records a new hire, a matching user or owner is created in Salesforce, so a new rep can start working accounts without waiting on a manual setup ticket.

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

Jobvite objects Salesforce objects How this pairing syncs
Candidate Read from the candidate feed (GET /candidate) and written back via POST /candidate/updateCandidates to change status, notes, and disposition on each record. Cases Support records; synced with help desk tools or internal databases for escalation workflows. Candidate is specific to Jobvite and Cases to Salesforce — each maps to any object or custom field on the other side.
Requisition (Job) Job openings created or updated through POST /job and read from GET /jobFeed; maps to opening tables in an ATS reporting warehouse. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Requisition (Job) is specific to Jobvite and Campaigns to Salesforce — each maps to any object or custom field on the other side.
Application Links a candidate to one requisition with its workflow state; read for pipeline reporting and status written back through the candidate update call. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Application is specific to Jobvite and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Workflow Status The pipeline stage per application (Screen, Interview, Offer, Hired); updated through POST /candidate/updateCandidates to advance records. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Workflow Status is specific to Jobvite and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
New Hire Hired-candidate records surfaced in the candidate feed and via the candidate hired webhook; commonly written into an HRIS or onboarding tool. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. New Hire is specific to Jobvite and Custom Objects to Salesforce — each maps to any object or custom field on the other side.
Employee Employee roster pushed through POST /employee (Onboard sync), used for referral matching and internal-mobility job postings. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Employee is specific to Jobvite and Accounts to Salesforce — each maps to any object or custom field on the other side.

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

Jobvite Salesforce Sub-second propagation

DetectionJobvite notifies Stacksync of record changes through webhook events. A candidate hired webhook, configured per customer by a Jobvite rep, POSTs to a custom URL on hire/offer-accepted events.

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

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

Rate-limit considerations

  • Jobvite: Roughly 15 requests per minute and 850 per hour, reset at midnight Pacific, with per-endpoint daily caps (e.g. 20,000/day candidate GET/PUT, 500/day employee sync); 429 on exceed.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Jobvite ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Jobvite and Salesforce connectors work

Jobvite

Integration surface
REST API (JSON) with candidate, requisition (job), and employee feed endpoints under https://api.jobvite.com/{version}
Authentication
API key (api) and secret (sc) plus company ID (companyId), sent in request headers since Jobvite's April 1, 2024 move from URL-query to header-based auth. Credentials are provisioned per customer by Jobvite Support.
Change detection
A candidate hired webhook, configured per customer by a Jobvite rep, POSTs to a custom URL on hire/offer-accepted events; otherwise Stacksync polls the candidate and job feeds on a schedule and diffs results, since records carry no per-item modified-date filter.
Capabilities
read · write · webhooks
Rate limits
Roughly 15 requests per minute and 850 per hour, reset at midnight Pacific, with per-endpoint daily caps (e.g. 20,000/day candidate GET/PUT, 500/day employee sync); 429 on exceed.
Jobvite 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 Jobvite 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 Jobvite 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
    Jobvite connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Jobvite 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 537 integrations available for Jobvite and Salesforce.

Popular · 8 of 537
All Jobvite 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