Real-time
Two-way sync
Changes in Freshsales or Greenhouse instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Freshsales to Greenhouse integration — real-time, two-way sync
Keep Freshsales and Greenhouse 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 Freshsales and Greenhouse
Keep the people who own accounts in Freshsales 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.
Freshsales 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 Products, Contacts, Accounts, Deals in Freshsales with Jobs, Offers, Scorecards, Scheduled Interviews 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 Freshsales keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Sync sales activities and appointments into analytics tools for rep productivity reporting.
- 02 Two-way sync of contacts and accounts between Freshsales and a Postgres database so product and data teams query CRM data with SQL.
- 03 Write enriched or sourced Candidates from external tools into Greenhouse and keep contact fields refreshed as data changes.
- 04 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.
Common sync patterns
New team members provisioned when they are hired
When Greenhouse records a new hire, a matching user or owner is created in Freshsales, 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 Freshsales update to match, so pipeline stays with the right owner.
Deactivate access when someone leaves
When Greenhouse marks a worker as departed, the matching user in Freshsales is flagged or deactivated, so former employees do not keep CRM access after their last day.
What you can sync between Freshsales and Greenhouse
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.
| Freshsales objects | Greenhouse objects | How this pairing syncs | |
|---|---|---|---|
| Appointments Scheduled meetings readable for activity analytics. | Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. | Appointments is specific to Freshsales and Users to Greenhouse — each maps to any object or custom field on the other side. | |
| Notes Free-text records attached to contacts, accounts, and deals. | Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. | Notes is specific to Freshsales and Departments and Offices to Greenhouse — each maps to any object or custom field on the other side. | |
| Sales activities Configurable activity types logged against records, useful for engagement scoring. | Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. | Sales activities is specific to Freshsales and Candidates to Greenhouse — each maps to any object or custom field on the other side. | |
| Products Catalog items attached to deals for line-level revenue data. | Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. | Products is specific to Freshsales and Applications to Greenhouse — each maps to any object or custom field on the other side. | |
| Contacts Person records carrying lifecycle stages; the main entity for two-way CRM syncs. | Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. | Contacts is specific to Freshsales and Jobs to Greenhouse — each maps to any object or custom field on the other side. | |
| Accounts Company records kept aligned with billing, ERP, and warehouse tables. | Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. | Accounts is specific to Freshsales and Offers to Greenhouse — each maps to any object or custom field on the other side. |
How changes propagate between Freshsales and Greenhouse
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.
Freshsales Greenhouse Sub-second propagation
DetectionFreshsales notifies Stacksync of record changes through webhook events. Polling with updated-at filters through views.
DeliveryEach detected change is written to Greenhouse through its API, with automatic retries and rate-limit backoff.
Greenhouse Freshsales 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 Freshsales through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Freshsales: Subject to per-account API rate limits that vary by Freshworks plan.
- 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.
What ships with Freshsales ⇄ Greenhouse
Connect Freshsales and Greenhouse for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Freshsales–Greenhouse connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Freshsales or Greenhouse 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 Freshsales or Greenhouse record.
Observability
Monitoring
Track your Freshsales ⇄ Greenhouse sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Freshsales and Greenhouse.
How the Freshsales and Greenhouse connectors work
Freshsales
- Integration surface
- REST API
- Authentication
- API key sent as a Token authorization header
- Change detection
- Polling with updated-at filters through views; outbound webhooks can be configured via workflow automations
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that vary by Freshworks plan
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.
How it works
How to connect Freshsales to Greenhouse — 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.
- 01
Connect your apps
Authenticate Freshsales and Greenhouse with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Freshsales
connected
Greenhouse
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Freshsales and Greenhouse 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.
objects · Freshsales ⇄ GreenhouseCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Freshsales GreenhouseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Freshsales and Greenhouse integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Freshsales and Greenhouse: authenticate both systems, choose the objects to sync (such as Freshsales's Appointments and Notes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Freshsales and Greenhouse: New team members provisioned when they are hired; Ownership and territory follow the org chart; Deactivate access when someone leaves. When Greenhouse records a new hire, a matching user or owner is created in Freshsales, so a new rep can start working accounts without waiting on a manual setup ticket.
-
Freshsales: REST API. Authentication: API key sent as a Token authorization header. Greenhouse: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Freshsales: Current Freshsales versions use lifecycle stages on contacts instead of a separate lead object, so lead routing maps to a stage field. Greenhouse: Change feeds rely on signed webhooks or updated_after / last_activity_after polling; there is no log-based change data capture. Stacksync's field mapping accounts for these differences between Freshsales and Greenhouse without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Freshsales and Greenhouse records are not retained after a sync operation.
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 522 integrations available for Freshsales and Greenhouse.
Popular · 8 of 522
-
Freshsales ⇄ Success Factors -
Freshsales ⇄ Hibob -
Freshsales ⇄ Ceridian Dayforce -
Freshsales ⇄ D2l Brightspace -
Greenhouse ⇄ Attio -
Greenhouse ⇄ Pipedrive -
Greenhouse ⇄ Zoho CRM -
Greenhouse ⇄ Shopify
No integrations match .
