Best practice for syncing employee OOO (vacation/sick) status from Personio / Outlook / Teams to Hub

Hi everyone,

I’m looking for best practices to keep HubSpot aware of employee availability — for example, when a HubSpot user is on vacation or sick, new inbound leads should automatically route to another owner.

We use Personio as our HR system (with Outlook and Teams also in use), so ideally Personio would serve as the main source of truth for absence data.

Has anyone set up a similar workflow to handle this kind of automatic routing in HubSpot?

Thanks,
Conor

I’ve seen a few setups like this, and the cleanest approach is to let your HR system (Personio in your case) be the source of truth and push that data into HubSpot automatically. HubSpot doesn’t have native awareness of OOO statuses, so you’ll need an integration layer to update user availability or reassign leads dynamically.

Personio can trigger webhooks or API calls when an absence is logged. You can use that to flag the user as unavailable in HubSpot (for example, update a custom Is available property on the user object) and route new leads to a fallback owner via workflow logic.

Hi @COHagan8

This comes up more often now that routing rules in HubSpot are getting smarter. HubSpot doesn’t natively sync “OOO” or leave data from HR tools, but you can make it work cleanly by linking Personio’s absence status to HubSpot via workflow triggers.

The simplest pattern is: Personio > webhook (or Outlook calendar event) > update a custom user property in HubSpot, e.g. “Is on leave.” Then, in your lead assignment workflow, add an if/then branch to skip any owners where that property = true (Create workflows )

If you’re routing through a shared inbox or round-robin, you can also leverage the Rotate owner action with filters so HubSpot reassigns automatically whenever that flag is set. Documentation on owner-based routing here (Assign ownership of records )

If your HR system, Outlook, and Teams all hold parts of that absence data, consistency becomes the hard part Stacksync can unify those systems so HubSpot always reflects the current status in real time without you having to rebuild every webhook chain.