Enterprise Software
HRM Interop: Scheduling Provider Webhooks & GDPR Erase
How HRM syncs provider changes to scheduling and handles GDPR right-to-erasure — without shared people databases across suite products.
HRM Interop: Scheduling Provider Webhooks & GDPR Erase
HR updates a provider's role. The booking calendar still shows old availability. Compliance requests erasure. You hunt across HR, CRM, and scheduling.
HRM includes interop built for suite reality — webhooks and GDPR erase with audit — not another HR island.
Guide: HRM buyer's guide
Provider-changed webhook → scheduling
When HR updates an employee's provider status (role, active/inactive, bookable):
- HRM persists change in
hrm_*tables - Provider-changed webhook fires to linked scheduling product
- Scheduling updates availability and assignment rules
No shared DB. Scheduling validates webhook and updates its own schema.
GDPR erase workflow
- Compliance triggers GDPR erase in HRM (authorized role)
- HRM purges employee PII per policy
- Audit log records who triggered erase and when
- Sibling products may require coordinated erase — HRM is the HR system of record
Plan cross-product erasure in discovery; HRM does not silently delete CRM contacts without configured workflows.
Employee interop ports
HRM exposes interop port APIs for:
- Migration import from legacy HR stores
- Cross-product employee references (e.g. Projects resource allocation)
- Service link discovery via Suite Platform
Configuration checklist
- HRM SKU entitled on tenant
- Scheduling service link registered
- Provider-changed webhook URL and secret configured
- GDPR erase policy documented with legal
- Staging test: role change → availability update
Honest limits
- External payroll tax filing not in scope
- Recruitment/benefits depth on roadmap
- Coordinated erase across CRM requires explicit integration design