Real-time
Two-way sync
Changes in Greenhouse or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Business productivity
Greenhouse to Microsoft Dynamics 365 integration — real-time, two-way sync
Keep Greenhouse and Microsoft Dynamics 365 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 Microsoft Dynamics 365
Keep the people, teams, and status that Microsoft Dynamics 365 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 Microsoft Dynamics 365 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 Accounts, Contacts, Leads, Opportunities in Microsoft Dynamics 365 with Scheduled Interviews, Users, Departments and Offices, Candidates in Greenhouse bi-directionally and in real time. A person added, moved, or offboarded in Greenhouse creates or updates the matching user in Microsoft Dynamics 365 within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Microsoft Dynamics 365 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 Replicate standard and custom Dataverse tables into a warehouse for reporting.
- 02 Enrich leads from external data sources and write scores back onto Dynamics records.
- 03 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.
- 04 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update stage, status, and custom fields in SQL while recruiters stay in Greenhouse.
Common sync patterns
Where Microsoft Dynamics 365 routes or assigns work by person: assignments follow the org
When someone changes teams or managers in Greenhouse, the queues, ownership, or approvals in Microsoft Dynamics 365 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 Microsoft Dynamics 365 with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
Offboarding: no standing access after a departure
When someone is marked as leaving in Greenhouse, the matching account in Microsoft Dynamics 365 is deactivated or flagged, so departures do not leave open access behind.
What you can sync between Greenhouse and Microsoft Dynamics 365
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 | Microsoft Dynamics 365 objects | How this pairing syncs | |
|---|---|---|---|
| Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. | Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | Scheduled Interviews is specific to Greenhouse and Accounts to Microsoft Dynamics 365 — 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. | Contacts Person records kept consistent with marketing, support, and data-warehouse copies. | Users is specific to Greenhouse and Contacts to Microsoft Dynamics 365 — 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. | Leads Inbound records enriched and routed from external sources into sales queues. | Departments and Offices is specific to Greenhouse and Leads to Microsoft Dynamics 365 — 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. | Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Candidates is specific to Greenhouse and Opportunities to Microsoft Dynamics 365 — 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. | Cases (Incidents) Support records shared with ticketing tools and product databases. | Applications is specific to Greenhouse and Cases (Incidents) to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. | Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. | Jobs is specific to Greenhouse and Quotes, Orders & Invoices to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. |
How changes propagate between Greenhouse and Microsoft Dynamics 365
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 Microsoft Dynamics 365 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 Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Microsoft Dynamics 365 Greenhouse Sub-second propagation
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
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.
What ships with Greenhouse ⇄ Microsoft Dynamics 365
Connect Greenhouse and Microsoft Dynamics 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Greenhouse–Microsoft Dynamics 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Greenhouse or Microsoft Dynamics 365 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 Microsoft Dynamics 365 record.
Observability
Monitoring
Track your Greenhouse ⇄ Microsoft Dynamics 365 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 Microsoft Dynamics 365.
How the Greenhouse and Microsoft Dynamics 365 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.
Microsoft Dynamics 365
- Integration surface
- REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
- Authentication
- Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
- Change detection
- Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
- Capabilities
- read · write · CDC · webhooks
How it works
How to connect Greenhouse to Microsoft Dynamics 365 — 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 Greenhouse and Microsoft Dynamics 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Greenhouse
connected
Microsoft Dynamics 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Greenhouse and Microsoft Dynamics 365 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 · Greenhouse ⇄ Microsoft Dynamics 365Customers 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.
Greenhouse Microsoft Dynamics 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Greenhouse and Microsoft Dynamics 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Greenhouse and Microsoft Dynamics 365: authenticate both systems, choose the objects to sync (such as Greenhouse's Scheduled Interviews and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Greenhouse: 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. Microsoft Dynamics 365: REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface. Authentication: Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities). Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft Dynamics 365: Change tracking returns only rows changed since a delta token, giving integrations an incremental read path without full re-pulls. Greenhouse: Pagination is Link-header (RFC-5988) based with per_page between 1 and 500 (default 100). Stacksync's field mapping accounts for these differences between Greenhouse and Microsoft Dynamics 365 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 Greenhouse and Microsoft Dynamics 365 records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Greenhouse and Microsoft Dynamics 365 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Greenhouse–Microsoft Dynamics 365 integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Greenhouse and Microsoft Dynamics 365. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 513 integrations available for Greenhouse and Microsoft Dynamics 365.
Popular · 7 of 513
-
Greenhouse ⇄ Smartsheet -
Greenhouse ⇄ Sysaid -
Greenhouse ⇄ Wrike -
Greenhouse ⇄ Zendesk -
Microsoft Dynamics 365 ⇄ Ukg Ready -
Microsoft Dynamics 365 ⇄ Success Factors -
Microsoft Dynamics 365 ⇄ Hibob
No integrations match .
