Skip to content
Human resources ⇄ Accounting and finance

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

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

Keep the employee, department, and cost records that Workday and Smartrecruiters share consistent in real time, so the finance system and the people system stop drifting apart.

Workday runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Smartrecruiters runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Time Off and Absence, Payroll Results, Suppliers, Customers and Invoices in Workday with Interviews, Offers, Users, Approvals in Smartrecruiters bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

Common use cases

  • 01 Push completed payroll results into a finance system or data warehouse each pay cycle.
  • 02 Import journal entries from external billing or expense systems into Workday Financials.
  • 03 Push hired Applications and their Offers into an HRIS such as Workday or SAP SuccessFactors to trigger onboarding and headcount records.
  • 04 Stream Jobs and Job Postings into a reporting database for requisition, funnel, and time-to-fill dashboards.

Common sync patterns

Department and cost-center alignment

The org structure maintained in Smartrecruiters keeps the departments or cost centers in Workday current, so spend and headcount roll up the same way.

Status changes propagate

A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.

People-driven costs land in finance

Compensation, reimbursements, or other costs tied to a person on the Smartrecruiters side flow into Workday for posting, so the books reflect what people actually cost without manual re-entry.

What you can sync between Smartrecruiters and Workday

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.

Smartrecruiters objects Workday objects How this pairing syncs
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. Workers The central HCM record covering employment, job, and personal data; the anchor of most syncs. Applications is specific to Smartrecruiters and Workers to Workday — each maps to any object or custom field on the other side.
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. Organizations Supervisory and company hierarchies read to drive routing and reporting in other systems. Jobs is specific to Smartrecruiters and Organizations to Workday — each maps to any object or custom field on the other side.
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). Positions Job seats synced with recruiting and planning tools. Job Postings is specific to Smartrecruiters and Positions to Workday — each maps to any object or custom field on the other side.
Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Compensation Pay components read into payroll, planning, and equity systems under strict access control. Interviews is specific to Smartrecruiters and Compensation to Workday — each maps to any object or custom field on the other side.
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). Time Off and Absence Balances and requests synced with scheduling and workforce tools. Offers is specific to Smartrecruiters and Time Off and Absence to Workday — each maps to any object or custom field on the other side.
Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Payroll Results Completed pay data exported to finance and benefits systems. Users is specific to Smartrecruiters and Payroll Results to Workday — each maps to any object or custom field on the other side.

How changes propagate between Smartrecruiters and Workday

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.

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

Workday Smartrecruiters Interval-based propagation

DetectionStacksync polls Workday for changes on an incremental schedule, reading only records changed since the previous pass. Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment.

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

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 Smartrecruiters ⇄ Workday

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Smartrecruiters and Workday connectors work

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

Workday

Integration surface
SOAP Workday Web Services (WWS), a REST API, and Reports-as-a-Service (RaaS) endpoints for custom reports
Authentication
OAuth 2.0 for the REST API; integration system users with WS-Security or certificate-based auth for SOAP
Change detection
Polling, including transaction-log criteria on SOAP operations to fetch objects changed since a given moment; no general webhook surface
Capabilities
read · write
How it works

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

    Choose tables

    Pick the Smartrecruiters and Workday 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 · Smartrecruiters ⇄ Workday
    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
    Smartrecruiters Workday
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Smartrecruiters and Workday 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.

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 495 integrations available for Smartrecruiters and Workday.

Popular · 8 of 495
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.