Real-time
Two-way sync
Changes in Gladly or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Gladly to Smartrecruiters integration — real-time, two-way sync
Keep Gladly 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 Gladly and Smartrecruiters
Keep the people who own accounts in Gladly 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.
Gladly 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 Conversation items, Agents, Topics, Tasks in Gladly with Job Postings, Interviews, Offers, Users 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 Gladly keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Push conversation outcomes into a CRM so account teams see support context on their accounts.
- 02 Sync Gladly customer profiles with an order database so agents see purchase history and profile updates flow back.
- 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
New team members provisioned when they are hired
When Smartrecruiters records a new hire, a matching user or owner is created in Gladly, so a new rep can start working accounts without waiting on a manual setup ticket.
Ownership and territory follow the org chart
When a person changes team, manager, or region in Smartrecruiters, their accounts and territory assignments in Gladly update to match, so pipeline stays with the right owner.
Deactivate access when someone leaves
When Smartrecruiters marks a worker as departed, the matching user in Gladly is flagged or deactivated, so former employees do not keep CRM access after their last day.
What you can sync between Gladly 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.
| Gladly objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Topics Categorization applied to conversations; the key dimension for contact-driver reporting. | 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. | Topics is specific to Gladly and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tasks Follow-up work items created from external triggers or synced for workload reporting. | 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 Gladly and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Customer profiles The central entity; merges identifiers like email, phone, and order IDs, which syncs use for matching. | 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). | Customer profiles is specific to Gladly and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Conversations Each customer's continuous timeline; status and outcomes sync to CRMs and warehouses. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Conversations is specific to Gladly and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Conversation items Individual messages across voice, SMS, chat, and email attached to the conversation. | 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). | Conversation items is specific to Gladly and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Agents User records used to attribute work in CX analytics. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Agents is specific to Gladly and Users to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Gladly 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.
Gladly Smartrecruiters Sub-second propagation
DetectionGladly notifies Stacksync of record changes through webhook events. Webhook event subscriptions for conversation and customer events, supplemented by polling and report exports.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Gladly 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 Gladly through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Gladly: 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 Gladly ⇄ Smartrecruiters
Connect Gladly and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gladly–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Gladly 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 Gladly or Smartrecruiters record.
Observability
Monitoring
Track your Gladly ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Gladly and Smartrecruiters.
How the Gladly and Smartrecruiters connectors work
Gladly
- Integration surface
- REST API
- Authentication
- API tokens used with basic authentication tied to an agent email
- Change detection
- Webhook event subscriptions for conversation and customer events, supplemented by polling and report exports
- 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.
How it works
How to connect Gladly 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.
- 01
Connect your apps
Authenticate Gladly 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.
Gladly
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Gladly 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.
objects · Gladly ⇄ SmartrecruitersCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Gladly SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Gladly and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Gladly and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Gladly's Topics and Tasks), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Gladly: Webhook event subscriptions for conversation and customer events, supplemented by polling and report exports. On Smartrecruiters: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Gladly side: Conversation items, Agents, Topics, Tasks, plus custom fields where Gladly exposes them. On the Smartrecruiters side: Job Postings, Interviews, Offers, Users. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Gladly and Smartrecruiters: New team members provisioned when they are hired; Ownership and territory follow the org chart; Deactivate access when someone leaves. When Smartrecruiters records a new hire, a matching user or owner is created in Gladly, so a new rep can start working accounts without waiting on a manual setup ticket.
-
Gladly: REST API. Authentication: API tokens used with basic authentication tied to an agent email. Smartrecruiters: 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. Stacksync manages authentication, retries, and rate limits on both sides.
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 411 integrations available for Gladly and Smartrecruiters.
Popular · 7 of 411
-
Gladly ⇄ Success Factors -
Gladly ⇄ Hibob -
Gladly ⇄ Ceridian Dayforce -
Smartrecruiters ⇄ Infor CRM -
Smartrecruiters ⇄ Insightly -
Smartrecruiters ⇄ Intercom -
Smartrecruiters ⇄ Kommo
No integrations match .
