Summary
This article documents how the Zuper integration transfers employee records from iPaaS.com to Zuper. When an iPaaS.com employee is dispatched to Zuper, the integration creates or updates a Zuper user with the employee's name, email, employee code, role, a default weekly working-hours schedule, and an initial password. The result keeps your Zuper user list aligned with the employees maintained in iPaaS.com.
Data in this direction flows outbound from iPaaS.com to Zuper. A mapping filter is applied so that only employees that have an email address are sent, because Zuper uses the email address as each user's login identity.
ID Format
Manual Sync ID Format
Manual Sync ID: the iPaaS.com employee identifier. Enter this identifier on the iPaaS.com Manual Sync page to send a single employee to Zuper. Example: 512.
External ID Format
External ID: the Zuper user_uid. After a successful transfer, iPaaS.com records the Zuper user_uid as the external ID on a dedicated external-ID record, which routes later updates back to the same Zuper user. Example: 2a1c15a0-5ac9-4a0a-9ce1-a4412032736c.
Deleted Record Support
Deleted record support is not available for this entity. This collection creates and updates Zuper users only. Delete mappings are not included in the default templates, so removing an employee in iPaaS.com does not remove the corresponding user in Zuper. Deactivate or remove users directly in Zuper when needed.
Mapping Collection Status
Enabled. A mapping filter applies to this collection, so only employees that meet the filter condition are processed (see the Mapping Filter block under Mappings below).
Trigger Events: this collection is dispatched by iPaaS.com outbound Add and Update triggers, and it can be run on demand from the iPaaS.com Manual Sync page. There are no inbound Zuper webhook triggers in this direction.
Duplicate or Conflicting Mappings
This collection is the only one that operates on the Employee entity in the Zuper integration. There are no other collections writing to the same Zuper user records, so there are no conflicting mappings to reconcile.
Collision Handling
Collision handling is not used by this collection. Users are matched by the saved external ID; before an external-ID link exists, the record is matched by its identifier. No merge or conflict-resolution logic runs on the destination user.
Zuper Caveats
Email is the login identity: a Zuper user must have an email address, which serves as their login. This is why the collection filters on email presence and why the Email field is required.
Initial password equals the email address: new users are created with an initial password set to their email address. Because this is a predictable value, have users reset their password after their first sign-in, or remap the Password field to a value that meets your security policy.
Role must exist: the assigned role id must be a valid role in your Zuper account. The shipped role id is a placeholder (see the mappings table) and must be confirmed or replaced before go-live.
iPaaS.com Caveats
Employee record must exist first: the employee record must exist in iPaaS.com before it can be dispatched to Zuper.
Email is required to transfer: because of the mapping filter, an iPaaS.com employee without an email address is skipped and never reaches Zuper. Populate the employee's email address in iPaaS.com before expecting the record to sync.
Setup Requirements
Before employees flow to Zuper, complete the following:
Enable outbound triggers: in the subscription configuration's Outbound Data Flows section, subscribe the relevant employee Add and Update triggers so that employee changes in iPaaS.com dispatch to Zuper. No automatic transfers occur until those outbound subscriptions are enabled.
Authentication: the integration authenticates to Zuper with an API key. Configure a valid Zuper API key in the subscription connection settings.
Review placeholder values: replace the placeholder RoleId and Designation values (see the mappings table) with values valid for your Zuper account before enabling the collection.
For full connection and configuration steps, see the Zuper Installation Instructions article.
Integration Flow
An employee record is added or updated in iPaaS.com, or an operator enters an iPaaS.com employee identifier on the Manual Sync page.
The outbound trigger (or Manual Sync request) dispatches the employee to the Zuper integration.
The mapping filter is evaluated. If the employee has no email address, the record is skipped and no user is created in Zuper.
For an employee that passes the filter, the integration builds the Zuper user payload from the field, static, and dynamic-formula mappings.
On a new record, the integration creates the user in Zuper. On an update, the integration writes to the existing Zuper user identified by its saved external ID.
iPaaS.com records the Zuper user_uid as the external ID so later updates route to the same Zuper user.
Mappings
Add Zuper Employee FROM iPaaS.com
Mapping Filter
!IsEmpty(EmailAddress)
This filter passes only employees whose EmailAddress is not empty. Employees that have an email address are transferred to Zuper; employees without an email address are skipped and never reach Zuper. The filter exists because Zuper uses the email address as each user's login identity, so a user cannot be created without one.
Description: Creates or updates a Zuper user from an iPaaS.com employee record, mapping name, email, employee code, role, initial password, and a default weekly working-hours schedule.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Zuper) | Description |
Field | FirstName | FirstName | Required. Sets the user's first name in Zuper. Zuper rejects a new user without a first name. |
Field | LastName | LastName | Recommended. Sets the user's last name in Zuper for a complete user record. |
Field | EmailAddress | Required. Sets the user's email address, which Zuper uses as the login identity. The collection filter ensures only employees with an email reach this mapping. | |
Static | "Technician" | Designation | Optional. Sets the job title on the new user. Placeholder to replace: every user is given the designation Technician by default. Replace this static value, or map a source field, if users need different job titles. |
Field | EmailAddress | Password | Required. Sets the initial password on the new user. By default the password is set to the user's email address, which is predictable; have users reset it, or remap this field to meet your security policy. |
Field | EmailAddress | ConfirmPassword | Required. Confirms the initial password and must match the Password field. It is set to the email address so it matches the default password above. |
Dynamic Formula | Id | EmpCode | Recommended. Sets the employee code on the Zuper user to the iPaaS.com employee identifier so the Zuper record can be traced back to its source. Formula: |
Static | "3" | RoleId | Required. Assigns the Zuper role to the new user. Placeholder to replace: the role is set to a fixed id of 3, an example value. Role ids differ per Zuper account, so confirm the correct role id and replace this value before enabling the collection. |
Dynamic Formula | (default schedule) | WorkHours | Optional. Builds a default weekly working-hours schedule for the new user (each day 09:00 AM to 05:00 PM, 480 minutes). Subscribers who need specific hours can adjust the schedule in the iPaaS.com mapping editor. Formula: |
Error Handling
If a transfer fails, the error is surfaced in iPaaS.com with the message returned by Zuper. For the list of Zuper error messages, their causes, and how to resolve them, see the Zuper Error Messages article.
Testing & Validation
Test Scenarios
Transfer an employee that has an email address and confirm a matching user is created in Zuper with the correct first name, last name, email, and employee code.
Transfer an employee that has no email address and confirm the record is skipped by the filter and no user is created in Zuper.
Update an existing employee in iPaaS.com and confirm the change writes to the same Zuper user rather than creating a duplicate.
Confirm the new user's role in Zuper matches the RoleId value you configured, not the placeholder value 3, after replacing the placeholder.
Confirm the new user's designation reflects the value you configured if you replaced the Technician placeholder.
Sign in to Zuper as a newly created user with the initial password (the email address) and confirm the password can be reset.
Validation Checklist
Outbound employee Add and Update triggers are subscribed under Outbound Data Flows.
A valid Zuper API key is configured for the subscription.
The RoleId placeholder value has been confirmed or replaced with a role id valid in your Zuper account.
The Designation placeholder value has been reviewed and adjusted if different job titles are needed.
Employees expected to sync have an email address populated in iPaaS.com.
A transferred employee's Zuper user_uid is saved back to iPaaS.com as the external ID after the first successful sync.
Additional Notes
Out of scope for this collection:
Deletion: the collection creates and updates Zuper users; it does not delete or deactivate them.
Bulk initialization: this collection does not support initializing all employees in one operation. Records are transferred through outbound triggers or Manual Sync.
Zuper webhooks: transfers in this direction are driven by iPaaS.com outbound triggers and Manual Sync, not by Zuper webhook events, at the time this documentation was written.