Skip to content
Human resources ⇄ CRM

Greenhouse to Veeva CRM integration — real-time, two-way sync

Keep Greenhouse and Veeva 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 Greenhouse and Veeva CRM

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

Veeva 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 Greenhouse. Greenhouse 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 Events, Approved Email Activity, Accounts (HCPs and HCOs), Calls in Veeva CRM with Applications, Jobs, Offers, Scorecards in Greenhouse field by field, in real time, and in both directions. You decide which system owns which fields, so Greenhouse stays authoritative on roles and org structure while Veeva CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Mirror medical inquiries into a medical information system for fulfillment and audit.
  • 02 Sync HCP and HCO accounts between Veeva CRM and a customer master or MDM system to keep the customer master aligned.
  • 03 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.
  • 04 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update stage, status, and custom fields in SQL while recruiters stay in Greenhouse.

Common sync patterns

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

A person recorded in Greenhouse, such as a candidate or applicant, can create or update the matching contact in Veeva CRM, 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 Greenhouse records a new hire, a matching user or owner is created in Veeva CRM, so a new rep can start working accounts without waiting on a manual setup ticket.

Ownership and territory follow the org chart

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

What you can sync between Greenhouse and Veeva 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.

Greenhouse objects Veeva CRM objects How this pairing syncs
Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Sample Transactions Sample disbursement records tracked for regulatory compliance. Users is specific to Greenhouse and Sample Transactions to Veeva CRM — each maps to any object or custom field on the other side.
Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. Consent Records Channel-level communication consent for HCPs, synced to enforce opt-outs across systems. Departments and Offices is specific to Greenhouse and Consent Records to Veeva CRM — each maps to any object or custom field on the other side.
Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Key Messages and CLM Content Approved content presented during calls, referenced in activity data. Candidates is specific to Greenhouse and Key Messages and CLM Content to Veeva CRM — each maps to any object or custom field on the other side.
Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Territories and Alignments Rep-to-account assignments, often fed from a roster or alignment system. Applications is specific to Greenhouse and Territories and Alignments to Veeva CRM — each maps to any object or custom field on the other side.
Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Events Medical events and speaker programs managed through Veeva's events capabilities. Jobs is specific to Greenhouse and Events to Veeva CRM — each maps to any object or custom field on the other side.
Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Approved Email Activity Sent-email records from Veeva Approved Email, used in engagement reporting. Offers is specific to Greenhouse and Approved Email Activity to Veeva CRM — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse and Veeva 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.

Greenhouse Veeva CRM Sub-second propagation

DetectionGreenhouse notifies Stacksync of record changes through webhook events. HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after /.

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

Veeva CRM Greenhouse Interval-based propagation

DetectionStacksync polls Veeva CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record modification timestamps.

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

Rate-limit considerations

  • Greenhouse: Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
  • Veeva CRM: Subject to the underlying platform's API request allocations, which are contract-dependent.
What ships with Greenhouse ⇄ Veeva CRM

Connect Greenhouse and Veeva CRM for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Greenhouse ⇄ Veeva CRM sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Greenhouse and Veeva CRM.

How the Greenhouse and Veeva CRM connectors work

Greenhouse

Integration surface
Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import)
Authentication
HTTP Basic Auth with a Harvest API key (key as username, blank password, colon appended then Base64-encoded); write calls require an On-Behalf-Of header naming the Greenhouse user
Change detection
HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters
Capabilities
read · write · webhooks
Rate limits
Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
Greenhouse setup guide

Veeva CRM

Integration surface
Salesforce-platform APIs (REST, SOAP, Bulk) for classic Veeva CRM; Vault REST API for Vault CRM
Authentication
OAuth 2.0
Change detection
Polling on record modification timestamps; platform event streams where the underlying org enables them
Capabilities
read · write
Rate limits
Subject to the underlying platform's API request allocations, which are contract-dependent.
How it works

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

    Choose tables

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

Greenhouse and Veeva 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.

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 505 integrations available for Greenhouse and Veeva CRM.

Popular · 7 of 505
All Greenhouse integrations All Veeva CRM 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