Contents
Summary
ID Format
Deleted Record Support
Mapping Collection Status
Duplicate or Conflicting Mappings
Supported Child Collections
System Caveats
Setup Requirements
Integration Flow
Mappings
Error Handling
Testing & Validation
Out of Scope
Summary
Clover customer records can be created and updated from iPaaS.com customer records through Manual Sync or through automatic outbound transfers. This flow maps the customer's name, email, and business name to Clover, and carries the customer's address details through a child collection, so the Clover customer list stays aligned with the customers managed in iPaaS.com.
ID Format
Manual Sync ID Format
To sync one customer on demand, enter the iPaaS.com customer identifier as the record key, exactly as it appears in iPaaS.com. For example, a customer with iPaaS.com identifier 10001 is entered as 10001.
The child address collection does not take its own Manual Sync key. The address is matched to its customer through the parent customer transfer, so there is no separate identifier to enter for the address.
External ID Format
The integration uses a dedicated external-identifier record to match an iPaaS.com customer to its Clover counterpart. After the first transfer, that saved identifier links the two records, so the same iPaaS.com customer resolves to the same Clover customer on repeat transfers rather than creating a duplicate.
Deleted Record Support
At the time this documentation was written, this outbound flow transfers customer creates and updates only. Delete mappings are not included in the default templates for the customer or the address collection, so removing a customer in iPaaS.com does not remove the corresponding customer from Clover through this flow. To remove a customer from Clover, delete it directly in Clover.
Mapping Collection Status
Status: Enabled.
Trigger Events: Manual Sync at any time, and automatic outbound transfers when a customer is added or changed in iPaaS.com and the outbound customer triggers are enabled in Outbound Data Flows.
Both the parent customer collection and the child address collection are active and have no mapping filter, so every customer dispatched to this flow is processed.
Duplicate or Conflicting Mappings
This flow creates and updates Clover customers from iPaaS.com in a single Add/Update operation, so a separate add-only and update-only pair is not needed for this direction. To avoid records overwriting one another, no other active mapping collection should write the same Clover customer, or the same Clover customer address, from the same iPaaS.com source.
Collision Handling
The Clover integration does not offer collision handling. When the same record could be updated from more than one side, the integration does not run a field-level merge or conflict-resolution step. Because mapped fields follow the iPaaS.com source on every transfer, decide which system is the system of record for a customer and drive changes from that side. See the Clover Integration Known Limitations article for the full behavior.
Unmapped-field overwrite risk
Because this is an Add/Update flow, the mapped fields are written to Clover on every transfer, so a value edited directly in Clover on a mapped field is replaced by the iPaaS.com value on the next transfer. Fields that are not mapped are left as they are on the Clover record — the integration omits empty values from the write rather than sending them as blanks. If a mapped field must keep its Clover value and never be overwritten, set that field's mapping to use the DestinationValue function (for example DestinationValue.CustomerNumber), which reads the existing Clover value back into the write.
Supported Child Collections
Parent Collection: Add/Update Clover Customer FROM iPaaS.com — creates or updates the Clover customer record and its name, email, and business name.
Child Collection: Add/Update Clover Customer Address FROM iPaaS.com — writes the customer's address details (street, city, region, postal code, country, and phone number) to the Clover customer alongside the customer record. It runs only as part of the parent customer transfer.
System Caveats
Clover Caveats
When Clover reports that too many requests have been made in a short period, the integration automatically pauses and retries the affected calls; no subscriber action is required.
Clover validates email format, so an email that iPaaS.com holds in an invalid form can be rejected by Clover.
Business name supplied on a transfer overwrites the business name on the Clover customer.
Clover may reject or ignore address values that do not match its expected formats. Keep region and postal values in forms Clover accepts, and validate in a staging environment where unsure.
Clover does not publish a strict single required field for a customer record or a customer address. First Name, Last Name, and Business Name on the customer, and the mapped address fields, are treated as Recommended for a usable Clover record. Subscribers should validate this behavior in a staging environment before relying on it in production.
iPaaS.com Caveats
The integration dispatches this flow when the outbound customer triggers are enabled or when a Manual Sync is run. The iPaaS.com customer must have the fields the mappings read for those values to reach Clover.
This flow always supplies an email value, using the default guest value
guest@customerdomain.comwhen the iPaaS.com email is empty, so a customer is never sent to Clover without an email. Because that default is a single shared value, several customers without an email can arrive in Clover with the same address. Provide a real, unique email on each customer where possible. Placeholder value — replace during implementation:customerdomain.comis an example domain — replace it in the EmailAddress mapping with a domain your organization controls so the fallback emails are recognizable and under your own domain.Errors are reported in the Dashboard under Integration Monitoring and the Error Logs.
Setup Requirements
iPaaS.com Configuration
The Clover integration must be installed and authorized for the subscription before this flow can be used.
For automatic transfers, enable the outbound customer triggers in Outbound Data Flows so that a customer added or changed in iPaaS.com is dispatched to Clover.
Manual Sync can be used at any time once the integration is authorized.
Clover Configuration
The Clover connection must be authorized through Clover's OAuth flow so the integration holds a valid access token for the merchant. See the Clover Connections and Settings article for the authorization walkthrough.
Integration Flow
iPaaS.com identifies the customer to transfer, either from an enabled outbound trigger or from a Manual Sync entered with the iPaaS.com customer identifier.
The mapped customer fields are assembled — first name, last name, email (with the guest-email default applied when the source email is empty), and business name.
The mapped address fields are assembled from the child address collection — street lines, city, region, postal code, country (with the United States default applied when the source country is empty), and phone number.
Clover creates the customer if no matching record exists, or updates the existing customer when the saved external identifier links to one. The address is written to that same Clover customer as part of the transfer.
The saved external identifier links the iPaaS.com customer to its Clover customer so subsequent transfers resolve to the same record.
No upstream iPaaS.com record must be transferred first — the customer is the top-level record in this flow, and its address travels with it rather than as a separate subscriber-initiated step.
Mappings
Add/Update Clover Customer FROM iPaaS.com
iPaaS.com data type: Customer.
This parent collection maps the iPaaS.com customer's name, email, and business name to the Clover customer, creating the customer if it does not yet exist or updating it if it does.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Clover) | Description |
Field | FirstName | FirstName | Recommended. Writes the iPaaS.com customer's first name to Clover; Clover does not publish it as a strict requirement. If the source first name is empty, an empty value is sent. Validate in a staging environment before relying on it in production. |
Field | LastName | LastName | Recommended. Writes the iPaaS.com customer's last name to Clover; Clover does not publish it as a strict requirement. If the source last name is empty, an empty value is sent. Validate in a staging environment before relying on it in production. |
Dynamic Formula |
| EmailAddress | Recommended. Sets the Clover customer's email from the iPaaS.com email; when the source email is empty, the default |
Field | Company | BusinessName | Optional. Writes the iPaaS.com Company value to the Clover Business Name, supplied only when the customer has a company value. When a value is sent, it overwrites the business name on the Clover customer. If the source company is empty, an empty value is sent on this Add/Update flow. |
Add/Update Clover Customer Address FROM iPaaS.com
iPaaS.com data type: Customer Address.
This child collection writes the iPaaS.com customer's address details to the Clover customer as part of the parent customer transfer. It does not run on its own.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Clover) | Description |
Field | Address1 | Address1 | Recommended. Writes the first address line to Clover; not published by Clover as a strict requirement. An empty source value sends an empty value. Validate address behavior in staging before relying on it in production. |
Field | Address2 | Address2 | Recommended. Writes the second address line to Clover; not required. An empty source value sends an empty value on this Add/Update flow. |
Field | Address3 | Address3 | Recommended. Writes the third address line to Clover; not required. An empty source value sends an empty value on this Add/Update flow. |
Field | City | City | Recommended. Writes the city to Clover; not required. An empty source value sends an empty value on this Add/Update flow. |
Field | Region | State | Recommended. Maps the iPaaS.com Region value to the Clover State field; not required. Clover may accept only recognized state or region values, so keep the source in a form Clover accepts and validate in staging where unsure. An empty source value sends an empty value. |
Field | PostalCode | Zip | Recommended. Maps the iPaaS.com Postal Code value to the Clover Zip field; not required. An empty source value sends an empty value on this Add/Update flow. |
Dynamic Formula |
| Country | Recommended. Sets the Clover country from the iPaaS.com country, returning the resolved country code when a value is present and defaulting to the United States code |
Field | PhoneNumber | PhoneNumber | Recommended. Writes the phone number to Clover; not required. An empty source value sends an empty value on this Add/Update flow. |
Error Handling
This flow surfaces the connection, authorization, and general Clover API errors cataloged in the Clover Error Messages article rather than a set of customer-specific messages. All errors appear in the Dashboard under Integration Monitoring and then Error Logs. The messages most relevant to the customer flow are:
"Clover API Quota Exception. Too May Request. Available in :[seconds]" — Clover returned an HTTP 429 rate-limit response. This is usually transient; the integration waits and retries when the reported reset window is short. Re-run the affected transfer after the reported wait period, and stagger manual syncs rather than running them all at once. If quota errors recur under normal operation, contact iPaaS.com Support.
"[Clover error message] [Clover error details]" — Clover rejected an API call and the integration surfaces Clover's own message text. For a customer transfer this most often reflects a value Clover would not accept, such as an email that fails Clover's format validation. Review the mapped values for the affected customer, correct the source data or mapping, and re-run. For an authorization failure, re-authorize the Clover connection so a fresh access token is stored.
For the full catalog, including the connection and OAuth authorization errors, see the Clover Error Messages article.
Testing & Validation
Test Scenarios
New customer transfer — Create a new customer in iPaaS.com with a first name, last name, email, and address, then Manual Sync it using the iPaaS.com customer identifier (for example
10001) and confirm the customer and its address are created in Clover.Customer update — Change the email, name, or company on an existing customer in iPaaS.com, re-transfer, and confirm the update appears on the same Clover customer rather than a duplicate.
Address sync — Change an address field on an existing customer in iPaaS.com, re-transfer through the parent customer, and confirm the address change reflects on the Clover customer.
Guest-email default — Transfer a customer with no email in iPaaS.com and confirm Clover receives the default
guest@customerdomain.com. Repeat with a second email-less customer to observe how Clover consolidates the shared default.Country default — Transfer a customer whose address has no country and confirm Clover records the United States code; transfer a non-US customer with a populated country and confirm the correct code is sent.
ID format — Manual Sync using the documented iPaaS.com customer identifier format and confirm the transfer succeeds and links to the correct Clover customer.
Validation Checklist
First name, last name, email, and business name write to the correct Clover customer fields.
The email default is applied only when the source email is empty; a populated source email passes through unchanged.
Address lines, city, region (Clover State), postal code (Clover Zip), country, and phone write to the correct Clover address fields.
The country default resolves to the United States code only when the source country is empty.
Repeat transfers of the same customer resolve to the same Clover record rather than creating duplicates.
Errors, if any, appear in the Dashboard under Integration Monitoring and Error Logs.
Out of Scope
This flow does not transfer orders, products, or inventory to Clover.
Address handling is limited to the fields carried by the child address collection.
The flow does not manage Clover-side customer categories or relationships.
Deletions are not propagated to Clover through this flow; delete mappings are not included in the default templates.
Fields not listed in the mappings are not sent to Clover.
For the field-level detail behind each collection and the integration-wide constraints, see the Clover mapping collection descriptions and the Clover Integration Known Limitations article.