Real-time
Two-way sync
Changes in Freshsales or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Freshsales to Smartrecruiters integration — real-time, two-way sync
Keep Freshsales and Smartrecruiters 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 Smartrecruiters
Keep the people who own accounts in Freshsales in step with the workforce records in Smartrecruiters, 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 Smartrecruiters. Smartrecruiters 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, Deals, Tasks, Appointments in Freshsales with Users, Approvals, Candidates, Applications in Smartrecruiters field by field, in real time, and in both directions. You decide which system owns which fields, so Smartrecruiters 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 Stream Jobs and Job Postings into a reporting database for requisition, funnel, and time-to-fill dashboards.
- 04 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.
Common sync patterns
Ownership and territory follow the org chart
When a person changes team, manager, or region in Smartrecruiters, their accounts and territory assignments in Freshsales update to match, so pipeline stays with the right owner.
Deactivate access when someone leaves
When Smartrecruiters 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.
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 Freshsales and Smartrecruiters
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 | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Notes Free-text records attached to contacts, accounts, and deals. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Notes is specific to Freshsales and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Sales activities Configurable activity types logged against records, useful for engagement scoring. | Job Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). | Sales activities is specific to Freshsales and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Products Catalog items attached to deals for line-level revenue data. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Products is specific to Freshsales and Interviews to Smartrecruiters — 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. | Offers Offer records tied to an Application with status, custom offer fields, and offer documents; readable and writable, commonly synced to an HRIS on hire (documents endpoint limited to 2 requests/sec). | Contacts is specific to Freshsales and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Accounts Company records kept aligned with billing, ERP, and warehouse tables. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Accounts is specific to Freshsales and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Deals Pipeline records synced to a warehouse for revenue reporting. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Deals is specific to Freshsales and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Freshsales and Smartrecruiters
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 Smartrecruiters 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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Freshsales Sub-second propagation
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
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.
- Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with Freshsales ⇄ Smartrecruiters
Connect Freshsales and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Freshsales–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Freshsales or Smartrecruiters 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 Smartrecruiters record.
Observability
Monitoring
Track your Freshsales ⇄ Smartrecruiters 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 Smartrecruiters.
How the Freshsales and Smartrecruiters 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
Smartrecruiters
- Integration surface
- SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions
- Authentication
- X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions
- Change detection
- Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture.
- Capabilities
- read · write · webhooks
- Rate limits
- Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
How it works
How to connect Freshsales to Smartrecruiters — 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 Smartrecruiters 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
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Freshsales and Smartrecruiters 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 ⇄ SmartrecruitersCustomers 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 SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Freshsales and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Freshsales and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Freshsales's Notes and Sales activities), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Freshsales side: Accounts, Deals, Tasks, Appointments, plus custom fields where Freshsales exposes them. On the Smartrecruiters side: Users, Approvals, Candidates, Applications. Stacksync auto-detects both schemas and converts types between the two systems.
-
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 Smartrecruiters: Ownership and territory follow the org chart; Deactivate access when someone leaves; One directory of people. When a person changes team, manager, or region in Smartrecruiters, their accounts and territory assignments in Freshsales update to match, so pipeline stays with the right owner.
-
Freshsales: REST API. Authentication: API key sent as a Token authorization header. Smartrecruiters: SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions. Authentication: X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions. 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. Smartrecruiters: Authentication is either an X-SmartToken API key (full company access, no scopes or expiry) or an OAuth 2.0 authorization-code flow that scopes access to the authorizing user's permissions. Stacksync's field mapping accounts for these differences between Freshsales and Smartrecruiters without custom code.
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 Smartrecruiters.
Popular · 7 of 522
-
Freshsales ⇄ Paylocity -
Freshsales ⇄ Ukg Ready -
Freshsales ⇄ Success Factors -
Smartrecruiters ⇄ Vitally -
Smartrecruiters ⇄ DealCloud -
Smartrecruiters ⇄ Chorusai -
Smartrecruiters ⇄ Clari
No integrations match .
