Skip to content
Human resources ⇄ ERP

Greenhouse to Dynamics 365 Business Central integration — real-time, two-way sync

Keep Greenhouse and Dynamics 365 Business Central 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 Dynamics 365 Business Central

Sync the workers, org structure, and cost centers that Dynamics 365 Business Central and Greenhouse share in real time, so the people Greenhouse manages stay current in the system that runs finance and operations.

Greenhouse is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Dynamics 365 Business Central runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Sales Invoices, Purchase Orders, General Ledger Entries, Journals in Dynamics 365 Business Central with Offers, Scorecards, Scheduled Interviews, Users in Greenhouse field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Dynamics 365 Business Central keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.
  • 02 Sync vendor and purchase order data with procurement or AP automation tools.
  • 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

One org structure

Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Dynamics 365 Business Central roll up to the same structure Greenhouse maintains.

Reporting lines drive approvals

Manager and reporting-hierarchy changes in Greenhouse keep expense and purchase approval chains in Dynamics 365 Business Central pointed at the right people.

Where Greenhouse runs payroll: labor cost in the books

Pay and compensation data from Greenhouse posts into Dynamics 365 Business Central as labor cost, so finance sees workforce spend without re-entering it by hand.

What you can sync between Greenhouse and Dynamics 365 Business Central

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 Dynamics 365 Business Central objects How this pairing syncs
Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Sales Invoices Billing documents synced to CRMs and payment platforms. Scorecards is specific to Greenhouse and Sales Invoices to Dynamics 365 Business Central — 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. Purchase Orders Procurement documents exchanged with supplier-facing systems. Scheduled Interviews is specific to Greenhouse and Purchase Orders to Dynamics 365 Business Central — 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. General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. Users is specific to Greenhouse and General Ledger Entries to Dynamics 365 Business Central — 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. Journals Staging records for financial postings created by integrations before posting. Departments and Offices is specific to Greenhouse and Journals to Dynamics 365 Business Central — 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. Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. Candidates is specific to Greenhouse and Dimensions to Dynamics 365 Business Central — 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. Payments Customer and vendor payment records reconciled against invoices. Applications is specific to Greenhouse and Payments to Dynamics 365 Business Central — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse and Dynamics 365 Business Central

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

Dynamics 365 Business Central Greenhouse Sub-second propagation

DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.

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 ⇄ Dynamics 365 Business Central

Connect Greenhouse and Dynamics 365 Business Central for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Greenhouse–Dynamics 365 Business Central connection.

Real-time

Two-way sync

Changes in Greenhouse or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Greenhouse or Dynamics 365 Business Central 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 Dynamics 365 Business Central record.

Observability

Monitoring

Track your Greenhouse ⇄ Dynamics 365 Business Central 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 Dynamics 365 Business Central.

How the Greenhouse and Dynamics 365 Business Central 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

Dynamics 365 Business Central

Integration surface
REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks
How it works

How to connect Greenhouse to Dynamics 365 Business Central — 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 Dynamics 365 Business Central 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
    Dynamics 365 Business Central connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Greenhouse and Dynamics 365 Business Central 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 ⇄ Dynamics 365 Business Central
    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 Dynamics 365 Business Central
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Greenhouse and Dynamics 365 Business Central 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 509 integrations available for Greenhouse and Dynamics 365 Business Central.

Popular · 7 of 509
All Greenhouse integrations All Dynamics 365 Business Central 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