Skip to content
Human resources ⇄ Business productivity

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

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

Keep the people, teams, and status that Wrike 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 Wrike 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 Comments, Timelogs, Contacts, Workflows in Wrike 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 Wrike within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Wrike 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 Sync Comments and status changes from Wrike into a database so downstream dashboards and tools react to project progress in near real time.
  • 02 Two-way sync of Tasks and their Custom Fields between a Wrike project and Postgres so ops teams work in SQL while project owners stay in Wrike.
  • 03 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.
  • 04 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.

Common sync patterns

Offboarding: no standing access after a departure

When someone is marked as leaving in Smartrecruiters, the matching account in Wrike 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.

Org and team structure kept current

Department, team, and reporting-line changes from Smartrecruiters keep the groups, queues, or projects in Wrike assigned to the right people.

What you can sync between Smartrecruiters and Wrike

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 Wrike objects How this pairing syncs
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. Tasks The primary unit of work and main record; created, updated, completed, and deleted via the REST v4 API and synced two-way. Subtasks are Tasks linked by superTask/subTask references. Candidates is specific to Smartrecruiters and Tasks to Wrike — each maps to any object or custom field on the other side.
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. Folders & Projects The container hierarchy: Folders group Tasks, and Projects add dates, an owner, and a status. Each maps to a synced table scope, and its structure defines what a sync covers. Applications is specific to Smartrecruiters and Folders & Projects to Wrike — 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. Custom Fields Typed fields (Text, Numeric, Date, DropDown, Contacts, Checkbox) defined at account or space level; mapped to database columns, with values written by field ID. Jobs is specific to Smartrecruiters and Custom Fields to Wrike — 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). Comments Discussion and activity entries attached to Tasks and Folders; read out for history and reporting or written back as comments. Job Postings is specific to Smartrecruiters and Comments to Wrike — 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. Timelogs Time-tracking entries logged against Tasks; read for billing and utilization reporting or written back when hours are recorded elsewhere. Interviews is specific to Smartrecruiters and Timelogs to Wrike — 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). Contacts Account members and user groups referenced by task responsibles and authors; read to resolve IDs to names and email addresses. Offers is specific to Smartrecruiters and Contacts to Wrike — each maps to any object or custom field on the other side.

How changes propagate between Smartrecruiters and Wrike

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

Wrike Smartrecruiters Sub-second propagation

DetectionWrike notifies Stacksync of record changes through webhook events. Webhooks scoped to a folder, a space, or the whole account fire on events like TaskCreated, TaskStatusChanged, and FolderCreated, with event.

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.
  • Wrike: Approximately 400 requests/minute per user (estimated on a per-second basis) with a higher per-IP ceiling; exceeding the limit or tripping Wrike's internal overload protection returns HTTP 429, handled with exponential backoff.
What ships with Smartrecruiters ⇄ Wrike

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Smartrecruiters ⇄ Wrike 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 Wrike.

How the Smartrecruiters and Wrike 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.
Smartrecruiters setup guide

Wrike

Integration surface
REST API v4 (JSON), single account endpoint such as www.wrike.com/api/v4; the data-center host (US or EU) comes from the OAuth token response, plus REST-managed Webhooks
Authentication
OAuth 2.0 for multi-user apps (Authorization header carrying access_token and requested scopes), and a legacy Permanent Access Token for single-account and testing use
Change detection
Webhooks scoped to a folder, a space, or the whole account fire on events like TaskCreated, TaskStatusChanged, and FolderCreated, with event filtering and custom payload fields; polling the task updatedDate is the fallback
Capabilities
read · write · webhooks
Rate limits
Approximately 400 requests/minute per user (estimated on a per-second basis) with a higher per-IP ceiling; exceeding the limit or tripping Wrike's internal overload protection returns HTTP 429, handled with exponential backoff
Wrike setup guide
How it works

How to connect Smartrecruiters to Wrike — 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 Smartrecruiters and Wrike 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
    Smartrecruiters connected
    Wrike connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Smartrecruiters and Wrike 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 511 integrations available for Smartrecruiters and Wrike.

Popular · 8 of 511
All Smartrecruiters integrations All Wrike 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