Real-time
Two-way sync
Changes in Smartrecruiters or Twilio instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Business productivity
Smartrecruiters to Twilio integration — real-time, two-way sync
Keep Smartrecruiters and Twilio 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 Twilio
Keep the people, teams, and status that Twilio 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 Twilio 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 Messaging Services, Calls, Incoming Phone Numbers, Outgoing Caller IDs in Twilio with Approvals, Candidates, Applications, Jobs in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters creates or updates the matching user in Twilio within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Twilio 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 Trigger outbound messages by writing rows to a synced database table instead of calling the Twilio API directly from application code.
- 02 Sync delivery and error statuses back into the system that initiated the send, so failed messages surface where the campaign lives.
- 03 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update hiring status, tags, and custom fields in SQL while recruiters keep working in SmartRecruiters.
- 04 Write enriched or sourced Candidates from external sourcing tools into SmartRecruiters and keep contact fields refreshed as data changes.
Common sync patterns
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.
Org and team structure kept current
Department, team, and reporting-line changes from Smartrecruiters keep the groups, queues, or projects in Twilio assigned to the right people.
Where Twilio routes or assigns work by person: assignments follow the org
When someone changes teams or managers in Smartrecruiters, the queues, ownership, or approvals in Twilio update to match, so work reaches whoever holds the role now.
What you can sync between Smartrecruiters and Twilio
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 | Twilio 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. | Roles Synced with incremental and full sync per the Stacksync docs. | Applications is specific to Smartrecruiters and Roles to Twilio — 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. | Addresses Synced with incremental and full sync per the Stacksync docs. | Jobs is specific to Smartrecruiters and Addresses to Twilio — 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). | Flows Synced with incremental and full sync per the Stacksync docs. | Job Postings is specific to Smartrecruiters and Flows to Twilio — 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. | Usage Records Aggregated usage and spend data synced into finance systems for cost tracking. | Interviews is specific to Smartrecruiters and Usage Records to Twilio — 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). | Messages SMS, MMS, and WhatsApp messages with delivery status; synced to log outreach in CRMs and databases. | Offers is specific to Smartrecruiters and Messages to Twilio — 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. | Messaging Services Synced with incremental and full sync per the Stacksync docs. | Users is specific to Smartrecruiters and Messaging Services to Twilio — each maps to any object or custom field on the other side. |
How changes propagate between Smartrecruiters and Twilio
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 Twilio 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 Twilio through its API, with automatic retries and rate-limit backoff.
Twilio Smartrecruiters Sub-second propagation
DetectionTwilio notifies Stacksync of record changes through webhook events. Status callback webhooks per message and call, plus polling of resource lists for backfill.
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 ⇄ Twilio
Connect Smartrecruiters and Twilio for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Smartrecruiters–Twilio connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Smartrecruiters or Twilio 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 Twilio record.
Observability
Monitoring
Track your Smartrecruiters ⇄ Twilio 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 Twilio.
How the Smartrecruiters and Twilio 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.
Twilio
- Integration surface
- REST API (per-product APIs for Messaging, Voice, Conversations, Verify)
- Authentication
- Account SID + Auth Token (copied from Twilio Console Account Info and entered into the Stacksync Twilio connector)
- Change detection
- Status callback webhooks per message and call, plus polling of resource lists for backfill
- Capabilities
- read · write · webhooks
How it works
How to connect Smartrecruiters to Twilio — 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 Smartrecruiters and Twilio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Smartrecruiters
connected
Twilio
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Smartrecruiters and Twilio 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 · Smartrecruiters ⇄ TwilioCustomers 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.
Smartrecruiters TwilioCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Smartrecruiters and Twilio integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Smartrecruiters and Twilio: authenticate both systems, choose the objects to sync (such as Smartrecruiters's Applications and Jobs), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Smartrecruiters and Twilio connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Smartrecruiters–Twilio integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Smartrecruiters and Twilio. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection 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. On Twilio: Status callback webhooks per message and call, plus polling of resource lists for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Twilio side: Messaging Services, Calls, Incoming Phone Numbers, Outgoing Caller IDs, plus custom fields where Twilio exposes them. On the Smartrecruiters side: Approvals, Candidates, Applications, Jobs. 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.
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 453 integrations available for Smartrecruiters and Twilio.
Popular · 8 of 453
-
Smartrecruiters ⇄ Campfire -
Smartrecruiters ⇄ Front -
Smartrecruiters ⇄ Amazon Seller Central -
Smartrecruiters ⇄ SendGrid -
Twilio ⇄ Greenhouse -
Twilio ⇄ Jobvite -
Twilio ⇄ Lever -
Twilio ⇄ Namely
No integrations match .
