Skip to content
Human resources ⇄ Business productivity

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

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

Keep the people, teams, and status that Microsoft Teams and Hibob 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. Hibob 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 Online Meetings, Tabs & Installed Apps, Teams, Channels in Microsoft Teams with Documents, Named lists, People (Employees), Employment in Hibob bi-directionally and in real time. A person added, moved, or offboarded in Hibob 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 Hibob 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 team membership from HR or identity systems so channels match the org chart.
  • 02 Route support case updates from the CRM into a triage channel for faster response.
  • 03 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.
  • 04 Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.

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 Hibob 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 Hibob, the queues, ownership, or approvals in Microsoft Teams update to match, so work reaches whoever holds the role now.

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

Hibob objects Microsoft Teams objects How this pairing syncs
Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Chats & Chat Messages 1:1 and group chat content read under protected-API access for compliance use. Employment is specific to Hibob and Chats & Chat Messages to Microsoft Teams — each maps to any object or custom field on the other side.
Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. Team Members & Users Membership synced with identity, HR, or CRM ownership data. Work is specific to Hibob and Team Members & Users to Microsoft Teams — each maps to any object or custom field on the other side.
Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. Online Meetings Meeting records synced with scheduling and CRM activity timelines. Salaries is specific to Hibob and Online Meetings to Microsoft Teams — each maps to any object or custom field on the other side.
Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Tabs & Installed Apps App configuration read to audit or provision team workspaces. Time off is specific to Hibob and Tabs & Installed Apps to Microsoft Teams — each maps to any object or custom field on the other side.
Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Teams Team containers provisioned or read to mirror org and project structure. Lifecycle is specific to Hibob and Teams to Microsoft Teams — each maps to any object or custom field on the other side.
Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Channels Channel targets used for routing synced notifications and updates. Documents is specific to Hibob and Channels to Microsoft Teams — each maps to any object or custom field on the other side.

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

Hibob Microsoft Teams Sub-second propagation

DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.

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

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

Rate-limit considerations

  • Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
What ships with Hibob ⇄ Microsoft Teams

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Hibob and Microsoft Teams connectors work

Hibob

Integration surface
REST API (the Bob API)
Authentication
Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
Change detection
Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
Hibob 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 Hibob 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 Hibob 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
    Hibob connected
    Microsoft Teams connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Hibob 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 Hibob and Microsoft Teams.

Popular · 8 of 445
All Hibob 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