Skip to content
Business productivity ⇄ Human resources

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

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

Keep the people, teams, and status that Orderful and Smartrecruiters share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Each tool in Orderful keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Smartrecruiters is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.

Stacksync syncs Relationships, Validation guidelines, Acknowledgments, Webhook events in Orderful with Candidates, Applications, Jobs, Job Postings in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters creates or updates the matching user in Orderful within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Orderful captures details of its own, such as a corrected contact or a login identity, those can flow back to Smartrecruiters in whichever direction you configure.

Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.

Common use cases

  • 01 Push invoices and advance ship notices from the ERP through Orderful to retail trading partners.
  • 02 Mirror transaction statuses and acknowledgments into a database for supply chain visibility dashboards.
  • 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 team structure kept current

Department, team, and reporting-line changes from Smartrecruiters keep the groups, queues, or projects in Orderful assigned to the right people.

Where Orderful routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Smartrecruiters, the queues, ownership, or approvals in Orderful update to match, so work reaches whoever holds the role now.

Onboarding: access ready on day one

A new hire recorded in Smartrecruiters creates the matching user in Orderful with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

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

Orderful objects Smartrecruiters objects How this pairing syncs
Relationships Active partner connections per transaction type that govern what can be sent and received 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). Relationships is specific to Orderful and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.
Validation guidelines Partner-specific rules transactions are checked against before delivery Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Validation guidelines is specific to Orderful and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Acknowledgments 997 functional acknowledgments confirming receipt of transmitted documents 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). Acknowledgments is specific to Orderful and Offers to Smartrecruiters — each maps to any object or custom field on the other side.
Webhook events Push notifications for inbound documents and transaction status changes Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Webhook events is specific to Orderful and Users to Smartrecruiters — each maps to any object or custom field on the other side.
Transactions EDI documents such as 850 purchase orders, 810 invoices, and 856 ship notices, represented as JSON Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Transactions is specific to Orderful and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.
Trading partners The retailers, carriers, and suppliers a company exchanges documents with 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. Trading partners is specific to Orderful and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.

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

Orderful Smartrecruiters Sub-second propagation

DetectionOrderful notifies Stacksync of record changes through webhook events. Webhooks push inbound transactions and status events.

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

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

Rate-limit considerations

  • Orderful: Subject to the platform's API rate limits.
  • 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 Orderful ⇄ Smartrecruiters

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Orderful and Smartrecruiters connectors work

Orderful

Integration surface
REST API (JSON)
Authentication
API key
Change detection
webhooks push inbound transactions and status events; polling available as fallback
Capabilities
read · write · webhooks
Rate limits
subject to the platform's API rate limits

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

    Choose tables

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

Orderful 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.

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 396 integrations available for Orderful and Smartrecruiters.

Popular · 7 of 396
Coworkers laughing in front of a laptop in a casual office setting

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