Skip to content
Business productivity ⇄ Human resources

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

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

Keep the people, teams, and status that Agiloft 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 Agiloft 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 Custom tables, Contracts, Companies, People in Agiloft 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 Agiloft within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Agiloft 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 Write contract or company records into Agiloft when a deal closes in the CRM to kick off downstream legal and procurement workflows.
  • 02 Two-way sync Contracts between Agiloft and an ERP or warehouse so value, renewal dates, and status stay current without manual re-keying.
  • 03 Write enriched or sourced Candidates from external sourcing tools into SmartRecruiters and keep contact fields refreshed as data changes.
  • 04 Stream Jobs and Job Postings into a reporting database for requisition, funnel, and time-to-fill dashboards.

Common sync patterns

Onboarding: access ready on day one

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

Offboarding: no standing access after a departure

When someone is marked as leaving in Smartrecruiters, the matching account in Agiloft is deactivated or flagged, so departures do not leave open access behind.

One employee directory

A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.

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

Agiloft objects Smartrecruiters objects How this pairing syncs
Approvals Per-record approval instances generated from Approval Templates and Workflows; read to report approval status and cycle time, or written to trigger and record decisions. Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Tasks Assigned action items with owners, due dates, and states tied to contracts or projects; synced two-way to surface Agiloft work inside a PM or operations system. 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 Agiloft and Jobs to Smartrecruiters — each maps to any object or custom field on the other side.
Clause Library Reusable, approved contract clauses with metadata and categories; read to feed clause content into other systems or reporting, or maintained from an external source of truth. 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). Clause Library is specific to Agiloft and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.
Custom tables Agiloft is a no-code platform, so any customer-built table (NDAs, SOWs, vendor risk, renewals) exposes the same REST and SOAP CRUD and syncs like the standard CLM tables. Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Custom tables is specific to Agiloft and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Contracts The core table holding contract records with value, key dates, status, type, and linked parties; created and updated two-way so contract data moves between Agiloft and a database, ERP, or CRM. 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). Contracts is specific to Agiloft and Offers to Smartrecruiters — each maps to any object or custom field on the other side.
Companies Records for every organization - counterparties, vendors, customers - linked to contracts and people; read and written to keep account master data aligned with a CRM or ERP. Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Companies is specific to Agiloft and Users to Smartrecruiters — each maps to any object or custom field on the other side.

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

Agiloft Smartrecruiters Sub-second propagation

DetectionAgiloft notifies Stacksync of record changes through webhook events. Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL.

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

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

Rate-limit considerations

  • Agiloft: Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.
  • 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 Agiloft ⇄ Smartrecruiters

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Agiloft and Smartrecruiters connectors work

Agiloft

Integration surface
REST API (/ewws/rest/{kb}) and SOAP/EWS v2 web services (EWWSv2Service WSDL), plus a native Webhooks subscription API
Authentication
OAuth 2.0 via OAuth2 Client Setup - Authorization Code with PKCE for user-delegated apps and Client Credentials for machine-to-machine; also JWT tokens or Basic Auth with a session token from POST /ewws/rest/{kb}/login
Change detection
Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL; otherwise poll each table by its Date Updated / modified-time fields. Agiloft has no database change-data-capture log.
Capabilities
read · write · webhooks
Rate limits
Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.

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

    Choose tables

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

Agiloft 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 407 integrations available for Agiloft and Smartrecruiters.

Popular · 8 of 407
All Agiloft 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