Skip to content
CRM ⇄ Human resources

Nimble to Smartrecruiters integration — real-time, two-way sync

Keep Nimble 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 Nimble and Smartrecruiters

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

Nimble 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 Contacts, Companies, Deals, Tasks in Nimble with Approvals, Candidates, Applications, Jobs 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 Nimble keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Push product usage or billing flags from internal databases into Nimble custom fields so reps have context before outreach.
  • 02 Keep deals aligned between Nimble and an accounting system so invoicing starts when a deal closes.
  • 03 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.
  • 04 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.

Common sync patterns

Deactivate access when someone leaves

When Smartrecruiters marks a worker as departed, the matching user in Nimble 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 Smartrecruiters tracks people the business also engages: contacts stay in sync

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

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

Nimble objects Smartrecruiters objects How this pairing syncs
Companies Stored as contact records with a company record type, so they sync through the same contacts resource Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. Companies is specific to Nimble and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.
Deals Pipeline records linked to contacts, synced to keep revenue systems aligned with sales activity Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. Deals is specific to Nimble and Applications to Smartrecruiters — each maps to any object or custom field on the other side.
Tasks To-do items tied to contacts, mirrored into work-management tools or reporting tables 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. Tasks is specific to Nimble and Jobs to Smartrecruiters — each maps to any object or custom field on the other side.
Activities Calls, events, and interaction history used for engagement reporting outside Nimble 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). Activities is specific to Nimble and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.
Notes Free-text records attached to contacts, replicated for a complete account timeline Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Notes is specific to Nimble and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Tags Segmentation labels that map to list membership or filters in downstream systems 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). Tags is specific to Nimble and Offers to Smartrecruiters — each maps to any object or custom field on the other side.

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

Nimble Smartrecruiters Interval-based propagation

DetectionStacksync polls Nimble 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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • Nimble: Subject to per-account API request quotas.
  • 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 Nimble ⇄ Smartrecruiters

Connect Nimble and Smartrecruiters for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Nimble or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Nimble 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 Nimble or Smartrecruiters record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Nimble and Smartrecruiters.

How the Nimble and Smartrecruiters connectors work

Nimble

Integration surface
REST API (JSON)
Authentication
API key; OAuth 2.0 available for registered applications
Change detection
polling on record modification timestamps
Capabilities
read · write
Rate limits
subject to per-account API request quotas

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.
Smartrecruiters setup guide
How it works

How to connect Nimble 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.

  1. 01

    Connect your apps

    Authenticate Nimble 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Nimble connected
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Nimble 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Nimble ⇄ Smartrecruiters
    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
    Nimble Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Nimble and Smartrecruiters 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 419 integrations available for Nimble and Smartrecruiters.

Popular · 7 of 419
All Nimble integrations All Smartrecruiters 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