Summary

UKG Ready employees can be transferred into iPaaS.com through a scheduled polling event or on demand from the Manual Sync page. Each transfer creates or updates an iPaaS.com Employee record and brings the employee's primary address across with it. UKG Ready is the source of truth for employee data; the transfer is one-way.

ID Format

Manual Sync ID Format

Enter the employee's numeric identifier from UKG Ready on its own, with no prefix, suffix, or separator.

Example: 12345

A value that is not a whole number is rejected and the transfer does not run.

External ID Format

After a successful transfer, iPaaS.com saves the UKG Ready employee identifier as the external ID on a dedicated external-ID record, separate from the Employee record's own fields. That record is what routes later transfers of the same employee to the existing iPaaS.com Employee rather than creating a second one.

For some record types iPaaS.com can fall back to matching on a primary-identifier field when no external-ID record exists yet. The iPaaS.com Employee record has no such field — it holds only the name, email address, and photo link — so the external-ID record is the only link between a UKG Ready employee and their iPaaS.com Employee record. If that link is removed, a later transfer of the same employee has nothing to match on and creates a duplicate.

Each transferred address also carries its own external-ID link, so repeat transfers update the existing address rather than adding another one.

Deleted Record Support

Outbound delete is not supported. Removing an employee in UKG Ready does not remove or deactivate the corresponding iPaaS.com Employee record, and delete mappings are not included in the default templates. Employees that leave the organisation remain in iPaaS.com until they are removed there directly.

Mapping Collection Status

Status: Enabled. Neither collection carries a mapping filter, so every employee submitted is processed.

Trigger Events: the employee/poll event starts a scheduled run; each employee the poll finds is raised as employee/created or employee/updated for processing. All three are enabled by subscribers or their MiSP in the subscription configuration's Inbound Data Flows section. Manual Sync is available at any time regardless of whether these events are enabled.

Duplicate or Conflicting Mappings

No other mapping collection in this integration writes to the iPaaS.com Employee or Employee Address record, so there is no risk of two collections competing for the same fields.

Every field iPaaS.com exposes on both records is mapped, apart from the link from an address to its parent employee, which iPaaS.com maintains itself. Each transfer refreshes all of them from UKG Ready. Subscribers or their MiSP who edit those fields directly in iPaaS.com should expect the next transfer of that employee to replace their edits.

Supported Child Collections

Parent Collection: Add/Update UKG Ready Employee TO iPaaS.com

Add/Update UKG Ready Employee Address TO iPaaS.com: transfers the employee's primary address as part of the same transfer. The address is linked to its employee through its own external-ID record.

System Caveats

UKG Ready Caveats

UKG Ready allows employees with no primary email address: the field is not mandatory in UKG Ready, so employee records without one are normal. iPaaS.com does require it, so those employees cannot transfer. See Additional Notes below, and the UKG Ready Integration Known Limitations article, for how to handle them.
Service account permissions: the API credentials configured on the subscription must retain the Web Services permission that grants access to employee data, or transfers fail with an authentication error rather than returning partial data.
Changed-employee reporting reaches back 30 days: UKG Ready only reports employees changed within the last 30 days. See Known Limitations in the companion article for what this means for polling frequency.
Separate mailing address is not transferred: UKG Ready can hold a separate mailing address alongside an employee's primary address. This release transfers the primary address only.
Employee profile and rate table data are not transferred: pay rates, rate tables, and profile detail are not brought into iPaaS.com.

iPaaS.com Caveats

Transfers are one-way: changes made to an iPaaS.com Employee record are not sent back to UKG Ready, and this integration does not create or update employees in UKG Ready.
Employees must exist in iPaaS.com before their timesheets can be sent to UKG Ready: the outbound timesheet collection only processes timesheets whose employee has already been transferred and linked. Transfer employees first.

Setup Requirements

UKG Ready Configuration

A service account with Web Services permissions must exist in UKG Ready, and its API User, API Password, API Key, and Company ID must be entered on the iPaaS.com subscription. The full walkthrough is in the UKG Ready Installation Instructions article — this document does not repeat it.

iPaaS.com Configuration

Enable employee/poll, employee/created, and employee/updated under Inbound Data Flows in the subscription configuration, and set the schedule the poll should run on. No employees transfer automatically until those events are enabled.

Integration Flow

A scheduled polling run starts, or a subscriber enters an employee identifier on the Manual Sync page.
On the first polling run the integration retrieves the complete employee list from UKG Ready. On every run after that it asks UKG Ready only for employees changed since the previous successful run, and records the run date so the next run knows where to resume.
Each employee identified is raised for processing individually.
The integration retrieves that employee's full record from UKG Ready in a single request. The employee's primary address is part of that record, so no separate address lookup is needed.
The employee mappings are applied and iPaaS.com creates or updates the Employee record, matched by the external-ID link where one already exists.
The employee's primary address is dispatched to the child collection, where the address mappings are applied and the iPaaS.com Employee Address record is created or updated.
iPaaS.com records the external-ID links for the employee and the address, so subsequent transfers update these records rather than duplicating them.

Mappings

Add/Update UKG Ready Employee TO iPaaS.com

iPaaS.com data type: Employee

Description: Creates or updates the iPaaS.com Employee record from the UKG Ready employee.

Mapping Type	Source Field (UKG Ready)	Destination Field (iPaaS.com)	Description
Field	PrimaryEmail	EmailAddress	Required by iPaaS.com, not by UKG Ready. iPaaS.com rejects an Employee record whose email address is empty; UKG Ready allows the field to be blank. An employee without one cannot transfer — see Additional Notes for the two ways to handle that.
Field	FirstName	FirstName	Required unless LastName is supplied — iPaaS.com requires at least one of the two. The default mappings supply both.
Field	LastName	LastName	Required unless FirstName is supplied — iPaaS.com requires at least one of the two. The default mappings supply both.
Field	PhotoHREF	PictureLink	Optional. A link to the employee's photo rather than the image itself. Employees without a photo transfer successfully with the field empty. Whether the link resolves outside UKG Ready depends on the subscriber's UKG Ready configuration.

Add/Update UKG Ready Employee Address TO iPaaS.com (Child)

iPaaS.com data type: Employee Address

Description: Creates or updates the iPaaS.com Employee Address record from the employee's primary address in UKG Ready. This collection runs only as part of a transfer of its parent; it has no independent trigger or Manual Sync entry point.

Mapping Type	Source Field (UKG Ready)	Destination Field (iPaaS.com)	Description
Dynamic Formula	`Id`	Name	Recommended. Labels the address, using the address identifier to choose between two fixed labels. In this release only the primary address is transferred, so every address arrives labelled Address; the formula's second label, MailingAddress, is not produced by the shipped configuration. Always produces a value, so the field is never sent empty. The full formula follows the table.
Field	City	City	Recommended. The city portion of the address. Arrives empty when UKG Ready holds no value, rather than blocking the transfer.
Field	State	Region	Recommended. UKG Ready calls this field State; iPaaS.com calls it Region. Transferred exactly as supplied — the integration does not convert between state names and abbreviations.
Field	Country	Country	Recommended. Transferred exactly as supplied — the integration does not convert between country names and country codes.
Field	Zip	PostalCode	Recommended. UKG Ready calls this field Zip; iPaaS.com calls it PostalCode.
Field	AddressLine1	Address1	Optional. The first line of the street address. An address that uses only some of the three lines transfers without error.
Field	AddressLine2	Address2	Optional. Commonly empty; an empty value does not prevent the address from transferring.
Field	AddressLine3	Address3	Optional. Commonly empty; an empty value does not prevent the address from transferring.
Field	Number	PhoneNumber	Optional. The phone number recorded against the address. Transferred exactly as supplied, including any formatting characters.

The Name formula in full:

if(Id.EndsWith("MailingAddress"))
    return "MailingAddress";
return "Address";

The employee an address belongs to is required by iPaaS.com but is not mapped — it is supplied automatically by the parent transfer.

Error Handling

"Invalid data passed to the employee record: [value]": the identifier entered on the Manual Sync page is not a whole number. Re-enter the employee's numeric identifier from UKG Ready with no prefix, suffix, or separator, then run the sync again.
Employee rejected for a missing email address: iPaaS.com requires an email address on every Employee record and UKG Ready does not, so this is expected for any employee whose primary email is blank. Either populate the primary email address in UKG Ready and transfer again, or change the EmailAddress mapping to supply a fallback value when the source is empty. See Additional Notes for the trade-off between the two.
Authentication failures during a poll or sync: the API credentials on the subscription are wrong, expired, or have lost the Web Services permission that grants access to employee data. Confirm the service account is still active in UKG Ready and that its API User, API Password, API Key, and Company ID on the subscription still match, then run the transfer again.
"More than one employee matches the requested external ID prefix": a lookup by partial external identifier matched several UKG Ready employees. Confirm that external identifiers are unique in UKG Ready for the employees in scope, and contact iPaaS.com Support at support@ipaas.com if the duplication is not visible from the UKG Ready side.

For the full catalogue of errors this integration can raise, see the UKG Ready Error Messages article.

Testing & Validation

Test Scenarios

Create a new employee in UKG Ready with a primary email address and a complete primary address, then transfer them from the Manual Sync page and confirm the iPaaS.com Employee and Employee Address records are created with all mapped fields populated.
Change the employee's last name and address in UKG Ready, transfer again, and confirm both records are updated in place rather than duplicated.
Attempt to transfer an employee with no primary email address in UKG Ready and confirm the transfer fails rather than creating a partial record.
Enter a non-numeric value on the Manual Sync page and confirm the transfer is rejected with an error rather than running.
Enable the polling events, let a scheduled run complete, and confirm the first run brings across the full employee list.
Change an employee in UKG Ready after that first run, wait for the next scheduled run, and confirm only the changed employee is processed.
Confirm an employee whose UKG Ready record holds a separate mailing address arrives in iPaaS.com with only the primary address, as designed.

Validation Checklist

Every employee in scope has a primary email address in UKG Ready.
The service account's Web Services permissions are in place and its credentials are entered on the subscription.
employee/poll, employee/created, and employee/updated are enabled under Inbound Data Flows.
The polling schedule runs well inside 30 days, so no changed-employee reporting is missed.
Employees have been transferred before any outbound timesheet events are enabled.

Additional Notes

Employees Without a Primary Email Address

iPaaS.com requires an email address on every Employee record and rejects one that is empty. UKG Ready does not impose the same requirement, so an employee can exist there with the field blank — and that employee will not reach iPaaS.com.

The attempt is not silent. It appears in Dashboard / Integration Monitoring / Error Logs, so affected employees can be identified rather than quietly going missing, and this applies equally to scheduled polling and to Manual Sync.

There are two ways to handle it:

Populate the primary email address in UKG Ready. Preferred, because the value stored in iPaaS.com is then a real, usable contact address.
Change the EmailAddress mapping to supply a fallback value when the source is empty. This lets the record transfer, but the address stored in iPaaS.com is not a working contact address and should not be used for correspondence. Subscribers or their MiSP choosing this route should agree a convention that makes such records easy to identify later.

Out of Scope

Creating, updating, or deleting employees in UKG Ready.
Deleting or deactivating employees in iPaaS.com when they are removed in UKG Ready.
Employee custom field values.
Employee profiles, pay rates, and rate tables.
Separate mailing addresses.

UKG Ready to iPaaS.com Employee Mapping Documentation