Two-way sync
Changes in Slack or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Slack 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.
Each tool in Slack 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 Users, User groups, Files, Reactions in Slack with Offers, Users, Approvals, Candidates in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters creates or updates the matching user in Slack within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Slack 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.
A new hire recorded in Smartrecruiters creates the matching user in Slack with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
When someone is marked as leaving in Smartrecruiters, the matching account in Slack is deactivated or flagged, so departures do not leave open access behind.
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.
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.
| Slack objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Users Workspace members with profile fields, synced against HR systems and identity providers. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| User groups Handles like @support that map to teams in external systems. | 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). | User groups is specific to Slack and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Files Uploads attached to messages, retrievable for archiving. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Files is specific to Slack and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Reactions Emoji responses that can drive workflows, such as approving a synced record. | 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. | Reactions is specific to Slack and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Channels Conversations (public, private, DMs) that messages are read from and posted to. | 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. | Channels is specific to Slack and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Messages Keyed by channel and timestamp; posted via chat.postMessage and read via history methods. | 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. | Messages is specific to Slack and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. |
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.
DetectionSlack notifies Stacksync of record changes through webhook events. Events API webhooks, delivered over HTTP callbacks or Socket Mode.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
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 Slack through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Slack–Smartrecruiters connection.
Changes in Slack or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Slack or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Slack or Smartrecruiters record.
Track your Slack ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Slack and Smartrecruiters.
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.
Authenticate Slack 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.
Pick the Slack 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Slack and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Slack's Users and User groups), 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 Slack and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Slack–Smartrecruiters integration in-house.
Yes — Stacksync ships production-grade connectors for both Slack and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Slack: Events API webhooks, delivered over HTTP callbacks or Socket Mode. 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 Slack side: Users, User groups, Files, Reactions, plus custom fields where Slack exposes them. On the Smartrecruiters side: Offers, Users, Approvals, Candidates. 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.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 453 integrations available for Slack and Smartrecruiters.