Summary
Revel employees can be transferred into iPaaS.com through the Add/Update Revel Employee TO iPaaS.com mapping collection. The integration retrieves each employee from Revel on a polling schedule, or on demand through Manual Sync, and creates or updates the matching iPaaS.com Employee record. Only the employee's identity fields are transferred.
ID Format
Manual Sync ID Format
Enter the Revel Employee ID — the system record identifier Revel assigns to the employee. For example: 79.
External ID Format
After a successful transfer, iPaaS.com saves the Revel Employee ID as the external ID on a dedicated external-ID record. That record is the primary match for every subsequent transfer of the same employee, routing it to an update of the existing iPaaS.com Employee rather than creating a duplicate.
Deleted Record Support
Outbound delete is not part of this collection. It adds and updates records only. Delete mappings are not included in the default templates, and removing an employee in Revel does not remove the matching iPaaS.com Employee record.
Custom Field Support
Revel custom fields are not supported by this integration; only the standard employee fields listed below are transferred.
Mapping Collection Status
Status: Enabled. This collection has no mapping filter, so every employee returned by a poll or entered on the Manual Sync page is processed.
Trigger Events: Create, Update — detected on the integration's polling schedule.
Duplicate or Conflicting Mappings
The Add/Update Revel Employee FROM iPaaS.com collection writes iPaaS.com employees back into Revel. Before enabling both directions at once, review the mapping filters on each so a change written by one direction does not immediately flow back through the other, and decide which system is the source of truth for employee data.
System Caveats
Revel Caveats
Employee records are read, not modified. This collection only retrieves data from Revel. Nothing on the Revel employee record is changed by a transfer in this direction.
Email address is not required in Revel. Revel does not require an email address on its own employee records, but iPaaS.com does (see below). Confirm every employee expected to sync has one populated in Revel.
iPaaS.com Caveats
Email address is required. iPaaS.com rejects an Employee record whose email address is missing or empty. An employee without an email address in Revel fails to transfer, and the failure appears in Dashboard / Integration Monitoring / Error Logs.
Employees must transfer before their timesheets. The Timesheet collection can only attach a timesheet to an employee already present and linked in iPaaS.com, so run this collection first.
Integration Flow
The employee is retrieved from Revel, either by a scheduled poll or by a Manual Sync using the Revel Employee ID.
The integration matches the employee to an existing iPaaS.com Employee by its saved external ID. If none exists, a new Employee record is created; otherwise the existing record is updated.
The mapped identity fields are written to the iPaaS.com Employee record.
Mappings
Add/Update Revel Employee TO iPaaS.com
iPaaS.com data type: Employee
This collection transfers an employee's identity fields from Revel to iPaaS.com.
Mapping Type | Source Field (Revel) | Destination Field (iPaaS.com) | Description |
Field |
| EmailAddress | Required. The employee's email address. iPaaS.com rejects the record if this is empty. |
Field |
| FirstName | Required. The employee's given name. iPaaS.com requires a given name or a family name; both are mapped here. |
Field |
| LastName | Required. The employee's family name. iPaaS.com requires a given name or a family name; both are mapped here. |
Error Handling
Errors are cataloged in the Revel Error Messages reference. The most common error on this flow is an employee that reaches iPaaS.com without an email address, which iPaaS.com rejects.
Testing & Validation
Test Scenarios
Create a new employee in Revel with a name and email address, then confirm it appears as an iPaaS.com Employee record with the expected values.
Update an existing Revel employee's name, then confirm the change propagates to iPaaS.com on the next transfer.
Attempt a transfer for a Revel employee with no email address and confirm the record is rejected with an error in the error log.
Manually sync a specific employee by entering its Revel Employee ID and confirm the transfer succeeds.
Validation Checklist
The employee's first name, last name, and email address appear correctly in iPaaS.com.
A second transfer of the same employee updates the existing record rather than creating a duplicate.
Employees are synchronized before any timesheets that reference them.