What the integration does
The innDex integration keeps the company's worker ID aligned with the worker's ID in innDex. Attendance continues to be exported from innDex to Excel and imported through the existing Requidex timesheet import process.
Configure the company connection
A company administrator or an MSP administrator with access to the company opens Company > Integrations > innDex and selects Configure.
Enter the innDex company ID. Agree the incoming event format and authentication with innDex before enabling live delivery.
Save the innDex company ID to enable incoming events and company worker ID sync. Copy the generated webhook credential when it is shown; it is displayed once. There is no separate enable checkbox.
Select Instructions on the innDex connection card to open the developer documentation in a new tab at Integrations > innDex. The page separates Requidex configuration, outgoing assignment events, the proposed incoming event contract, and worker ID linking for timesheet imports. Agree the incoming format with innDex before live delivery. The current receiver supports induction submitted, approved, change requested and rejected events for existing workers and requires their Requidex worker ID. All four event types use the same payload fields, including the innDex induction ID.
The credential lets Requidex verify incoming induction events from innDex. Use the copy icon in the Incoming webhook URL field and provide that URL and credential securely to whoever configures innDex webhook delivery. The credential is used as the bearer token for those deliveries.
Use the existing Webhooks tab to configure the agreed assignment events that innDex listens to for invitations and onboarding.
How workers are linked
innDex retains the full Requidex worker ID and returns it with the innDex worker ID in each supported induction event. The worker must already belong to the company. National Insurance numbers are not used as a fallback for matching. Events with an omitted, null or blank Requidex worker ID are acknowledged as ignored without changing data or appearing in Incoming events. Handling workers originating in innDex, including possible worker or assignment creation, has not yet been decided.
A successful event populates the company worker ID and updates the worker ID copied onto that company's assignments and timesheets. Other companies' worker IDs are preserved.
A newer event can update an ID previously linked by this integration. An older event cannot replace a newer successfully linked ID. Repeated deliveries of the same event do not apply the update again.
Receiving an induction submitted, approved, change requested or rejected event with a Requidex worker ID records the event type and syncs the company worker ID. It does not create workers or assignments, change assignment status, or approve or revoke compliance, site access or timesheets in Requidex. innDex handles invitations and onboarding. Each distinct lifecycle event needs its own event ID; reuse an ID only to retry the same event. Events for the same induction include the same innDex induction ID. Requidex records that reference but does not currently retrieve induction details.
Review sync results
The connection card shows the integration status, innDex company ID and whether a webhook credential is configured. Select Incoming events to open the event log dialog, then use Refresh to reload the event history.
The incoming events dialog shows the latest 100 recorded events, including the event type, Requidex worker ID, innDex worker ID, induction ID, sync result and any conflict. An induction rejected event can have a successful sync result: the result describes worker ID sync, not induction approval. Rejected requests with invalid credentials or payloads are not included. New Webhook and Export logs are available on the Webhooks tab.
Conflicts include a worker outside the company, an existing company worker ID that differs, a company worker ID already used by another worker, or ambiguous company ID entries. Check the worker profile and correct the underlying issue before using Retry sync from the event's actions menu. Retry sync does not force an overwrite.
To disable the integration, clear the innDex company ID in Configure and save. This stops incoming sync and retries and invalidates the webhook credential. Saving a company ID again enables the integration and generates a new credential. Generating a replacement credential or changing the innDex company ID also immediately invalidates the previous credential, so update the sending configuration in innDex.
Import timesheets
Export attendance from innDex to Excel and use the existing timesheet import process. The worker ID in the import must match the company's worker ID in Requidex. Resolve missing or conflicting worker IDs before importing.
For agencies
This connection is configured by the hiring company or its authorised MSP administrator. Agencies continue to supply workers and use their existing assignment and timesheet workflows. If a company worker ID is missing or incorrect for an innDex timesheet import, contact the hiring company to review its innDex sync results. Agency Integrations remains the place to manage the agency's own outgoing webhooks.