Skip to content
Database ⇄ Human resources

Azure SQL Database to Smartrecruiters integration — real-time, two-way sync

Keep Azure SQL Database 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 Azure SQL Database and Smartrecruiters

Put your workforce data where your apps can reach it: Azure SQL Database and Smartrecruiters share the same people, positions, and org structure in real time.

Smartrecruiters is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Azure SQL Database is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Candidates, Applications, Jobs, Job Postings in Smartrecruiters need to exist as queryable Change tracking / CDC tables, Tables, Views, Schemas in Azure SQL Database before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Change tracking / CDC tables, Tables, Views, Schemas in Azure SQL Database with Candidates, Applications, Jobs, Job Postings in Smartrecruiters field by field, in real time. You decide which system owns which fields — Smartrecruiters typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Consolidate data from several line-of-business apps into one Azure SQL database as an integration hub.
  • 02 Feed an Azure SQL operational database with orders and inventory from an ERP in near real time.
  • 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

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in Azure SQL Database, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in Azure SQL Database write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Smartrecruiters land as queryable Change tracking / CDC tables, Tables, Views, Schemas in Azure SQL Database, so internal apps and dashboards read live data instead of a periodic export.

What you can sync between Azure SQL Database 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.

Azure SQL Database objects Smartrecruiters objects How this pairing syncs
Schemas Namespaces that organize tables and control which objects a sync user can reach. 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). Schemas is specific to Azure SQL Database and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.
Rows and columns Standard relational records with typed columns; primary keys anchor upserts. Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Rows and columns is specific to Azure SQL Database and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Stored procedures Existing business logic that some teams invoke on write instead of direct table inserts. 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). Stored procedures is specific to Azure SQL Database and Offers to Smartrecruiters — each maps to any object or custom field on the other side.
Change tracking / CDC tables System-maintained change records used to drive incremental sync. Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Change tracking / CDC tables is specific to Azure SQL Database and Users to Smartrecruiters — each maps to any object or custom field on the other side.
Tables The primary sync target; rows map one-to-one to records in the paired system. Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Tables is specific to Azure SQL Database and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.
Views Read-only projections used when the sync should expose a curated shape rather than raw tables. 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. Views is specific to Azure SQL Database and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.

How changes propagate between Azure SQL Database 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.

Azure SQL Database Smartrecruiters Sub-second propagation

DetectionChanges in Azure SQL Database are captured at the source via change data capture — no polling loop against its API. Change data capture or change tracking, both supported on Azure SQL Database.

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

Smartrecruiters Azure SQL Database 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 applied to Azure SQL Database as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • 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 Azure SQL Database ⇄ Smartrecruiters

Connect Azure SQL Database and Smartrecruiters for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure SQL Database and Smartrecruiters.

How the Azure SQL Database and Smartrecruiters connectors work

Azure SQL Database

Integration surface
SQL wire protocol (TDS), the same protocol as SQL Server; T-SQL over standard drivers
Authentication
SQL authentication (database credentials) or Microsoft Entra ID authentication
Change detection
Change data capture or change tracking, both supported on Azure SQL Database; polling as a fallback
Capabilities
read · write · CDC

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 Azure SQL Database 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 Azure SQL Database 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
    Azure SQL Database connected
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure SQL Database 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 · Azure SQL Database ⇄ 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
    Azure SQL Database Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure SQL Database 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 443 integrations available for Azure SQL Database and Smartrecruiters.

Popular · 8 of 443
All Azure SQL Database 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