Skip to content
Human resources ⇄ Business productivity

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

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

Keep the people, teams, and status that Wrike and Greenhouse 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. Greenhouse 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 Folders & Projects, Custom Fields, Comments, Timelogs in Wrike with Applications, Jobs, Offers, Scorecards in Greenhouse bi-directionally and in real time. A person added, moved, or offboarded in Greenhouse 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 Greenhouse 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 Push support tickets or intake requests from an operational database into Wrike Tasks, then read completion and status Custom Fields back when work finishes.
  • 02 Sync Comments and status changes from Wrike into a database so downstream dashboards and tools react to project progress in near real time.
  • 03 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.
  • 04 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.

Common sync patterns

Org and team structure kept current

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

Where Wrike routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Greenhouse, the queues, ownership, or approvals in Wrike update to match, so work reaches whoever holds the role now.

Onboarding: access ready on day one

A new hire recorded in Greenhouse creates the matching user in Wrike with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

What you can sync between Greenhouse 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.

Greenhouse objects Wrike objects How this pairing syncs
Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. 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. Scorecards is specific to Greenhouse and Custom Fields to Wrike — each maps to any object or custom field on the other side.
Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Comments Discussion and activity entries attached to Tasks and Folders; read out for history and reporting or written back as comments. Scheduled Interviews is specific to Greenhouse and Comments to Wrike — each maps to any object or custom field on the other side.
Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Timelogs Time-tracking entries logged against Tasks; read for billing and utilization reporting or written back when hours are recorded elsewhere. Users is specific to Greenhouse and Timelogs to Wrike — each maps to any object or custom field on the other side.
Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. Contacts Account members and user groups referenced by task responsibles and authors; read to resolve IDs to names and email addresses. Departments and Offices is specific to Greenhouse and Contacts to Wrike — each maps to any object or custom field on the other side.
Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Workflows Sets of custom statuses grouped into stages (Active, Completed, Cancelled, Deferred); read to map task status transitions to database values. Candidates is specific to Greenhouse and Workflows to Wrike — each maps to any object or custom field on the other side.
Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Spaces Top-level containers that hold Folders, Projects, and their members; used to scope which Folders a given sync covers. Applications is specific to Greenhouse and Spaces to Wrike — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse 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.

Greenhouse Wrike Sub-second propagation

DetectionGreenhouse notifies Stacksync of record changes through webhook events. HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after /.

DeliveryEach detected change is written to Wrike through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • Greenhouse: Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
  • 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 Greenhouse ⇄ Wrike

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Greenhouse ⇄ Wrike sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Greenhouse and Wrike.

How the Greenhouse and Wrike connectors work

Greenhouse

Integration surface
Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import)
Authentication
HTTP Basic Auth with a Harvest API key (key as username, blank password, colon appended then Base64-encoded); write calls require an On-Behalf-Of header naming the Greenhouse user
Change detection
HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters
Capabilities
read · write · webhooks
Rate limits
Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
Greenhouse 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 Greenhouse 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 Greenhouse 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
    Greenhouse connected
    Wrike connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Greenhouse 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 Greenhouse and Wrike.

Popular · 8 of 511
All Greenhouse 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