Skip to content
Human resources ⇄ Business productivity

Greenhouse to Microsoft Teams integration — real-time, two-way sync

Keep Greenhouse and Microsoft Teams 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 Teams

Keep the people, teams, and status that Microsoft Teams 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 Teams 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 Channel Messages, Chats & Chat Messages, Team Members & Users, Online Meetings in Microsoft Teams with Candidates, Applications, Jobs, Offers in Greenhouse bi-directionally and in real time. A person added, moved, or offboarded in Greenhouse creates or updates the matching user in Microsoft Teams within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Microsoft Teams 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 Route support case updates from the CRM into a triage channel for faster response.
  • 02 Archive channel messages into a warehouse for compliance and communication analytics.
  • 03 Write enriched or sourced Candidates from external tools into Greenhouse and keep contact fields refreshed as data changes.
  • 04 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.

Common sync patterns

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 Greenhouse keep the groups, queues, or projects in Microsoft Teams assigned to the right people.

Where Microsoft Teams 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 Teams update to match, so work reaches whoever holds the role now.

What you can sync between Greenhouse and Microsoft Teams

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 Teams objects How this pairing syncs
Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Online Meetings Meeting records synced with scheduling and CRM activity timelines. Jobs is specific to Greenhouse and Online Meetings to Microsoft Teams — each maps to any object or custom field on the other side.
Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Tabs & Installed Apps App configuration read to audit or provision team workspaces. Offers is specific to Greenhouse and Tabs & Installed Apps to Microsoft Teams — each maps to any object or custom field on the other side.
Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Teams Team containers provisioned or read to mirror org and project structure. Scorecards is specific to Greenhouse and Teams to Microsoft Teams — 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. Channels Channel targets used for routing synced notifications and updates. Scheduled Interviews is specific to Greenhouse and Channels to Microsoft Teams — 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. Channel Messages Posted messages read for archiving or written to broadcast record changes. Users is specific to Greenhouse and Channel Messages to Microsoft Teams — 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. Chats & Chat Messages 1:1 and group chat content read under protected-API access for compliance use. Departments and Offices is specific to Greenhouse and Chats & Chat Messages to Microsoft Teams — each maps to any object or custom field on the other side.

How changes propagate between Greenhouse and Microsoft Teams

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

Microsoft Teams Greenhouse Sub-second propagation

DetectionMicrosoft Teams notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) for messages and membership.

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 Teams

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Greenhouse ⇄ Microsoft Teams 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 Teams.

How the Greenhouse and Microsoft Teams 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

Microsoft Teams

Integration surface
REST API (Microsoft Graph)
Authentication
OAuth 2.0 via Microsoft Entra ID; reading message content at scale requires Microsoft-approved protected-API access
Change detection
Graph change notifications (webhooks) for messages and membership; delta queries on some resources
Capabilities
read · write · webhooks
How it works

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

    Choose tables

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

Greenhouse and Microsoft Teams 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 445 integrations available for Greenhouse and Microsoft Teams.

Popular · 8 of 445
All Greenhouse integrations All Microsoft Teams 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