Overview
What Gets Indexed
How It Works
- You provide your Darwinbox base URL, tenant credentials, and dataset key
- The connector syncs enabled modules and stores a checkpoint for resumable syncs
- Synced employee and org data becomes searchable in Omni
- Optional action modules expose self-service, manager, HR operations, ATS, and report actions to agents
Darwinbox tenant capabilities and API availability vary by deployment. Enable only the sync and action modules your tenant supports.
Prerequisites
Before setting up the Darwinbox connector, ensure you have:- Darwinbox API access for your tenant
- Base URL for your Darwinbox instance, such as
https://acme.darwinbox.in - Dataset key for the APIs Omni should call
- One supported credential set:
- Basic auth username, password, and API key
- OAuth2 client credentials
- Legacy dynamic-token credentials with an authorization code or refresh token
- Omni deployment with the Darwinbox connector service running (profile:
darwinbox)
Setup
Step 1: Connect in Omni
- Navigate to Settings → Integrations
- Find Darwinbox and click Connect
- Enter your Darwinbox base URL
- Choose an authentication mode:
- Basic auth + API key: API username, password, API key, and dataset key
- OAuth2 client credentials: Client ID, client secret, optional API key, and dataset key
- Legacy dynamic token: Client ID, client secret, grant type, authorization code or refresh token, optional API key, and dataset key
- Set the Default timezone if needed
- Choose optional modules:
- Sync position master
- Enable ATS jobs/actions
- Enable HR lifecycle actions
- Enable report actions
- Click Connect
- Click Sync to start the initial sync
Your Darwinbox connector is now configured. Initial indexing time depends on the number of employees and enabled modules.
Managing the Integration
Viewing Sync Status
Navigate to Settings → Integrations to view sync status, indexed counts, and errors. Click Settings on the source for sync history and source configuration.Sync Modes
Search Operators
The connector registers source-specific operators that work in Search and Chat once the source is running:AI Assistant Actions
Darwinbox actions are grouped by module:
Write-capable actions are only registered when the corresponding action module is enabled and are subject to the same agent/chat approval and action-allowlist controls as other connector actions.
Removing the Integration
- Navigate to Settings → Integrations
- Click Settings against the Darwinbox source
- Click Delete Permanently
- Revoke or rotate the Darwinbox API credentials if needed
Troubleshooting
Connection failed
Connection failed
Verify the base URL, authentication mode, credentials, API key, and dataset key. Remove any trailing slash from the base URL.
Some modules fail during sync
Some modules fail during sync
Confirm your Darwinbox tenant has the relevant API enabled. Disable optional modules such as positions or ATS if your tenant does not expose those endpoints.
Employee permissions look wrong
Employee permissions look wrong
The connector can use Darwinbox permission data and optional admin/recruiter email lists in source configuration. Review the source settings and verify the synced employee directory contains the expected email addresses.
Security Considerations
- Credential storage: Darwinbox credentials are encrypted at rest in Omni
- Module scoping: Keep optional HR, ATS, and report actions disabled unless your team needs them
- Write actions: HR lifecycle, leave approval, ATS, and document-upload actions can change data in Darwinbox; expose them only to trusted agents or users
- Token rotation: Rotate API keys, passwords, client secrets, and refresh tokens according to your Darwinbox security policy
What’s Next
Search Your Data
Learn how to search HR and organization data
Background Agents
Use approved HR workflow actions in agents
Connector Management
Monitor syncs and manage the source