HR integrations

Connect HRlume to the identity, communication and calendar tools your team already uses.

Keep employee workflows in HRlume while notifications, meetings and approved data access reach the systems around it.

Available connections

Practical integrations for everyday people operations.

Each integration solves a specific workflow instead of asking for broad access to unrelated data.

Identity access

Enterprise SSO & identity

Google, Microsoft and LDAP / Active Directory — verified employees sign in with the identity provider your organisation already runs, without auto-creating new accounts.

Google
Microsoft
LDAP / AD
Scheduling

Calendar sync

Push meetings to the organiser's own calendar and invite the other participant through a separate, employee-authorised grant.

Google
Outlook

Slack & Telegram notifications

Deliver selected employee notifications through Slack (matched by email) or a linked personal Telegram chat.

Calendar feeds & custom domain

Subscribe to HRlume calendar feeds from any compatible app, and connect your own careers hostname with guided DNS setup.

Scoped REST API

Read workforce data and safely create or update selected assets, recruiting, document, survey, goal and knowledge records — every key has its own purpose, lifetime and read/write scopes.

View API documentation
Controlled access

Integrations should not become master keys.

HRlume separates employee sessions, OAuth grants and API keys. Every API key has an editable purpose, lifetime, IP allowlist and independent read/write scopes. Sensitive write access is highlighted and never inherited by legacy keys.

Single sign-on does not create new employee records automatically: an administrator still controls who has an account and therefore who consumes a licensed seat.

API key administration

Make every integration identifiable, limited and revocable.

Create personal or service keys, choose a fixed expiry or unlimited lifetime, and combine resource-specific read and write scopes. Administrators can edit access without exposing the raw token again.

  • One-time secret display and secure token hashing
  • Named purposes in Ukrainian and English
  • Optional IP allowlists and expiration dates
  • Warnings for sensitive write permissions
Open the API reference →
HRlume API key settings with scoped read and write access