Skip to content
Human resources ⇄ CRM

Jobvite to Twenty CRM integration — real-time, two-way sync

Keep Jobvite 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 Jobvite and Twenty CRM

Keep the people who own accounts in Twenty CRM 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.

Twenty CRM 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 Workspace Members, People, Companies, Opportunities in Twenty CRM with Offer, Candidate, Requisition (Job), Application 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 Twenty CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Run a continuous sync from a legacy CRM into Twenty during a migration so both systems stay usable through cutover.
  • 02 Two-way sync of People and Companies between Twenty and a production Postgres database so engineers can query CRM data with SQL.
  • 03 Sync Employee roster data into Jobvite with POST /employee to power employee-referral matching and internal-mobility postings.
  • 04 Two-way sync Candidate records and their Workflow Status between Jobvite and a Postgres database so recruiting-ops teams query and update pipeline data in SQL.

Common sync patterns

Deactivate access when someone leaves

When Jobvite marks a worker as departed, the matching user in Twenty CRM 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.

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 Twenty CRM, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

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

Jobvite objects Twenty CRM objects How this pairing syncs
Attachment Resumes, cover letters, and files attached to a candidate; synced out to object storage or a document management system. Attachments Files linked to records. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Application Links a candidate to one requisition with its workflow state; read for pipeline reporting and status written back through the candidate update call. Notes Free-form notes attached to records, useful for mirroring activity from other tools. Application is specific to Jobvite and Notes to Twenty CRM — 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. Custom Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. Workflow Status is specific to Jobvite and Custom Objects to Twenty CRM — 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. Workspace Members User accounts used for record ownership and assignment mapping. New Hire is specific to Jobvite and Workspace Members to Twenty CRM — 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. People Individual contact records with emails, phones, and company links; a core target for contact syncs. Employee is specific to Jobvite and People to Twenty CRM — each maps to any object or custom field on the other side.
Offer Offer state tied to an application (extended, accepted, declined); read out for offer-acceptance reporting and written to downstream comp or HR systems. Companies Account-level records that group people and opportunities. Offer is specific to Jobvite and Companies to Twenty CRM — each maps to any object or custom field on the other side.

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

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

Twenty CRM Jobvite 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 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.
  • Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Jobvite ⇄ Twenty CRM

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Jobvite ⇄ 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 Jobvite and Twenty CRM.

How the Jobvite and Twenty CRM 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

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

    Choose tables

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

Jobvite 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 435 integrations available for Jobvite and Twenty CRM.

Popular · 7 of 435
Coworkers laughing in front of a laptop in a casual office setting

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