Two-way sync
Changes in Copper CRM or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Copper CRM 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.
Copper CRM 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 Leads, Opportunities, Activities, Tasks in Copper CRM with Approvals, Candidates, Applications, Jobs 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 Copper CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
When Smartrecruiters records a new hire, a matching user or owner is created in Copper CRM, so a new rep can start working accounts without waiting on a manual setup ticket.
When a person changes team, manager, or region in Smartrecruiters, their accounts and territory assignments in Copper CRM update to match, so pipeline stays with the right owner.
When Smartrecruiters marks a worker as departed, the matching user in Copper CRM is flagged or deactivated, so former employees do not keep CRM access after their last day.
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.
| Copper CRM objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Custom Field Definitions Org-defined fields whose definitions are fetched to build dynamic field mappings. | 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). | Custom Field Definitions is specific to Copper CRM and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| People Individual contact records, often created from Gmail interactions, and the main target of contact syncs. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | People is specific to Copper CRM and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Companies Organization records linked to people and opportunities. | 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). | Companies is specific to Copper CRM and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Leads Unqualified prospects kept separate from People until converted. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Leads is specific to Copper CRM and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Opportunities Deals tracked through pipelines and stages; synced for revenue reporting. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Opportunities is specific to Copper CRM and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Activities Logged emails, calls, meetings, and notes attached to records. | 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. | Activities is specific to Copper CRM and Candidates 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.
DetectionCopper CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record create/update/delete events.
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 Copper CRM through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Copper CRM–Smartrecruiters connection.
Changes in Copper CRM or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Copper CRM 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 Copper CRM or Smartrecruiters record.
Track your Copper CRM ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Copper CRM 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 Copper CRM 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 Copper CRM 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 Copper CRM and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Copper CRM's Custom Field Definitions and People), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Copper CRM 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 Copper CRM, so a new rep can start working accounts without waiting on a manual setup ticket.
Copper CRM: REST API. Authentication: API key paired with the requesting user's email address, sent as request headers. 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.
Copper CRM: API authentication uses an API key plus the user's email address in headers, so requests execute in the context of a specific Copper user. Smartrecruiters: Authentication is either an X-SmartToken API key (full company access, no scopes or expiry) or an OAuth 2.0 authorization-code flow that scopes access to the authorizing user's permissions. Stacksync's field mapping accounts for these differences between Copper CRM and Smartrecruiters without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Copper CRM and Smartrecruiters records are not retained after a sync operation.
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 526 integrations available for Copper CRM and Smartrecruiters.