Connect your HR workspace with the systems your organization uses. Enterprise integrations are scoped around supported data, provider compatibility and the workflow you need to complete.
API access and webhooks are part of Enterprise scoped configuration. Custom connections, provider setup and implementation services are confirmed in your quotation. Compare plan inclusions.
Organization-scoped API credentials support approved data access. The API includes employee directory fields, organization structure, published schedules and leave data, subject to the credential’s permissions.
Confirm the fields, read or write operation, permissions and expected request volume your connection needs.
Webhook subscriptions deliver supported events to a configured endpoint. The integration workspace includes signed delivery, retry handling and delivery status so authorized administrators can investigate failures.
Confirm the event, destination, signature verification and how your receiving system handles repeated or failed delivery.
Enterprise identity requirements are scoped with your organization. Provider configuration and sign-in testing are required; recording provider details alone does not establish a working SSO connection.
Name your identity provider and confirm sign-in, employee access, administrator recovery and employee departure scenarios.
ERP, accounting, payroll-provider and other system connections are evaluated individually. Define the data direction and responsibility for each system before agreeing implementation and support.
Confirm connector availability, data mapping, vendor requirements, implementation fees and ongoing ownership in your proposal.
API access and webhooks are part of Enterprise scoped configuration. Confirm the required data, permissions, event types and implementation responsibilities in your proposal. They are not included in Starter, Growth or Business as standard plan features.
Bring the system name, version and required data flow to the evaluation. A connection may require custom work or a provider-supported interface. Confirm compatibility, supported operations, cost and acceptance tests before treating it as available.
No. SSO requires provider-specific configuration and verification. Confirm your provider and required login policies, then test sign-in and access with the implementation team. A listed identity feature is not proof that a particular provider is already connected.
No. API credentials are organization-bound and scoped. Available endpoints and approved data fields determine what the credential can access. Review the required fields during integration planning rather than assuming full database access.
Use a controlled test with sample records. Verify the expected data, access boundaries, error and retry handling, and the result in the receiving system. Agree who signs off the connection and who handles support after launch.
