Summary
iPaaS.com Timesheet records can be written into Revel through the Add/Update Revel Timesheet FROM iPaaS.com mapping collection. The integration creates a Revel timesheet entry the first time a record is transferred and updates it on every transfer afterward. Three of the values Revel requires — the establishment, hourly wage, and processing stage — ship as fixed defaults that must be reviewed before go-live.
ID Format
Manual Sync ID Format
Enter the iPaaS.com Timesheet ID — the record identifier iPaaS.com assigns to the timesheet, not the Revel one.
External ID Format
After a successful transfer, iPaaS.com saves the Revel Timesheet Entry ID as the external ID on a dedicated external-ID record. That record is the primary match for every subsequent transfer of the same timesheet, routing it to an update of the existing Revel entry 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 a Timesheet record in iPaaS.com does not remove the matching Revel timesheet entry.
Custom Field Support
Revel custom fields are not supported by this integration; only the standard timesheet fields listed below are transferred.
Mapping Collection Status
Status: Enabled. This collection has no mapping filter, so every iPaaS.com Timesheet dispatched to it is processed.
Trigger Events: Create, Update — dispatched by the iPaaS.com Timesheet outbound triggers the subscriber enables under Outbound Data Flows.
Duplicate or Conflicting Mappings
The Add/Update Revel Timesheet TO iPaaS.com collection transfers Revel timesheet entries into iPaaS.com. Before enabling both directions at once, review the mapping filters on each so a shift written by one direction does not immediately flow back through the other, and decide which system is the source of truth for labour data.
Supported Child Collections
None. A timesheet is written to Revel as a single entry. The worked-time and break child collections belong to Add/Update Revel Timesheet TO iPaaS.com and apply to the inbound direction only.
System Caveats
Revel Caveats
Required fields. Revel requires a clock-in time, an employee, an establishment, and an hourly wage on every timesheet entry it creates.
The employee must exist in Revel first. A timesheet can only be attached to an employee already written to Revel and linked by Add/Update Revel Employee FROM iPaaS.com. When no linked Revel employee exists, the transfer fails and the failure appears in Dashboard / Integration Monitoring / Error Logs.
The establishment must exist in Revel. The establishment supplied on the entry must be a real establishment in the subscriber's Revel account — see the placeholder note in the Mappings section.
Records are attributed to the configured agent. Revel requires every entry to name the user that created and last updated it; the integration supplies the AgentId subscription setting, which must be a valid Revel user.
Updates are partial. Only the mapped fields are written; values already on the Revel entry that this collection does not map are left untouched.
iPaaS.com Caveats
The employee must be written to Revel first. This collection does not create the employee as part of the timesheet transfer.
Break detail is not carried outbound. A shift written to Revel carries its start and end times but not a separate break record.
Setup Requirements
iPaaS.com configuration. Replace the shipped establishment and wage placeholder values (see the Mappings section) with values valid for your Revel account. Enable the Timesheet outbound triggers under Outbound Data Flows for automatic transfers. See the Revel Installation Instructions for connection and credential setup, including the AgentId value that records are attributed to.
Integration Flow
The iPaaS.com Timesheet is dispatched to Revel, either by an enabled outbound trigger or by a Manual Sync using the iPaaS.com Timesheet ID.
The integration resolves the timesheet's employee to the linked Revel employee. If no linked Revel employee exists, the transfer fails.
The integration matches the timesheet to an existing Revel entry by its saved external ID, creating a new entry or updating the existing one, changing only the mapped fields.
Mappings
Add/Update Revel Timesheet FROM iPaaS.com
iPaaS.com data type: Timesheet
This collection writes a timesheet from iPaaS.com into a Revel timesheet entry.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Revel) | Description |
Dynamic Formula |
| ClockIn | Required. The shift start time, reformatted into the layout Revel accepts. Revel rejects the entry without a clock-in. |
Dynamic Formula |
| ClockOut | Optional. The shift end time. Absent while a shift is still open, allowing an open shift to be written and closed later. |
Dynamic Formula |
| EmployeeId | Required. Resolves the iPaaS.com employee to the linked Revel employee. Revel rejects the entry without an employee. |
Static |
| EstablishmentId | Required. The Revel establishment the entry is recorded against. Placeholder — replace before go-live (see note below). |
Static |
| RoleWage | Required. The hourly wage recorded against the entry. Placeholder — replace before go-live (see note below). |
Field |
| Remarks | Optional. Free-text notes carried onto the Revel entry. |
Static |
| Stage | Optional. The processing stage the entry is created in. Revel treats this as a numeric code but does not publish its meaning; validate in a staging environment if you rely on it. |
Placeholder value — replace during implementation: the EstablishmentId default 1 and the RoleWage default 16.5 are example values that are not meaningful for any particular subscriber. Revel requires both, so leaving them in place produces timesheets that are recorded against the wrong establishment and carry the wrong pay data. Replace each with a value valid for your Revel account before enabling the collection. Where more than one establishment or pay rate is in use, change the mapping from a fixed value to a formula or field mapping that selects the correct value per record.
Error Handling
Errors are cataloged in the Revel Error Messages reference. Common errors on this flow are a missing required field, an establishment that does not exist in Revel, and an employee that has not yet been written to Revel, each of which Revel rejects.
Testing & Validation
Test Scenarios
Replace the establishment and wage placeholders with valid values, transfer an iPaaS.com Timesheet whose employee already exists in Revel, and confirm a Revel timesheet entry is created with the expected times.
Update the timesheet in iPaaS.com and confirm the change propagates to the existing Revel entry without creating a duplicate.
Transfer a timesheet for an employee not yet written to Revel and confirm the transfer fails with an error in the error log.
Transfer a timesheet with the shipped establishment placeholder left in place and confirm Revel rejects it because the establishment does not exist.
Validation Checklist
The EstablishmentId and RoleWage placeholder values have been replaced with values valid for the Revel account.
The employee has been written to Revel before the timesheet is transferred.
The AgentId subscription setting is a valid Revel user.