Available Connectors
Okta HRIS Integration
Okta connector for Kombo’s HRIS API
The Okta HRIS integration allows you to sync HRIS data between Okta and your application through Kombo’s unified API. The tool slug for this connector is okta
.
Guides and Resources
Supported Features & Coverage
Legal Entities
Legal Entities
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
address | |
remote_data |
Employees
Employees
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
employee_number | |
first_name | |
last_name | |
display_full_name | |
job_title | |
work_email | |
personal_email | |
mobile_phone_number | |
employment_status | |
avatar | |
legal_entity_id | |
manager_id | |
home_address | |
start_date | |
termination_date | |
remote_created_at | |
custom_fields | |
integration_fields | |
remote_data |
Groups
Groups
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
remote_data |
Employee <> Group
Employee <> Group
Field | Notes |
---|---|
employee_id | |
team_id | |
id | |
changed_at | |
remote_deleted_at |
Legal Entities
Legal Entities
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
address | |
remote_data |
Employees
Employees
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
employee_number | |
first_name | |
last_name | |
display_full_name | |
job_title | |
work_email | |
personal_email | |
mobile_phone_number | |
employment_status | |
avatar | |
legal_entity_id | |
manager_id | |
home_address | |
start_date | |
termination_date | |
remote_created_at | |
custom_fields | |
integration_fields | |
remote_data |
Groups
Groups
Field | Notes |
---|---|
id | |
remote_id | |
changed_at | |
remote_deleted_at | |
name | |
remote_data |
Employee <> Group
Employee <> Group
Field | Notes |
---|---|
employee_id | |
team_id | |
id | |
changed_at | |
remote_deleted_at |
Create employee
Create employee
When an employee is created, an email is sent to the user with an activation token that the user can use to complete the activation process
Input Field | Notes |
---|---|
first_name | |
last_name | |
work_email | |
job_title | |
home_address.street_1 | |
home_address.city | |
home_address.zip_code | |
home_address.country | |
mobile_phone_number |
Feature | Notes |
---|---|
Connection Guide | |
Prerequisites | |
Create credentials | |
API Passthrough | |
Additional Scopes | |
Delta Syncs |