Summary
Stamped.io customers can be created and updated from iPaaS.com customer data. When a customer is transferred, the integration creates the customer in Stamped.io if it does not already exist, or updates the matching customer when it does, and reconciles the customer's survey and review-email subscription state when that field is mapped. Customer data flows in one direction, from iPaaS.com to Stamped.io.
ID Format
Manual Sync ID: to transfer a single customer from the iPaaS.com Manual Sync page, enter the iPaaS.com Customer ID (for example, 150713).
External ID Format
After a successful transfer, iPaaS.com records the Stamped.io customer id as the external ID that links the two records (an example Stamped.io id is 143491), which routes later updates to the same Stamped.io customer. Stamped.io itself matches and de-duplicates customers by their unique email address, so a transfer for an existing email updates that customer rather than creating a duplicate. The integration also writes the iPaaS.com customer number into the Stamped.io external-id reference field for traceability back to the iPaaS.com source.
Deleted Record Support
Outbound delete is not supported. Stamped.io does not provide a customer delete operation, so delete mappings are not included in the default template and deletions are not propagated to Stamped.io.
Custom Field Support
Custom field configuration is not part of this collection.
Mapping Collection Status
Status: Enabled. The collection has no mapping filter, so all customer records routed to it are processed.
Trigger Events: Create and Update. Whether a transfer results in a create or an update in Stamped.io depends on whether the customer is already linked by external ID.
Duplicate or Conflicting Mappings
This is the only collection that writes customers to Stamped.io, so there are no conflicting collections. Selectable collision-handling methods are not offered for this collection; matching relies on the external-ID link and the customer email.
Supported Child Collections
None. Customer is a standalone collection with no dependent child collections.
System Caveats
Stamped.io Caveats
Email is required and unique: a unique customer email must be present, because Stamped.io uses it to create and match the customer.
Updates send only mapped values: on update, the integration sends the fields populated by the mapping and omits unmapped fields rather than sending empty values. Whether Stamped.io preserves or clears an unsent field depends on Stamped.io's own update behavior; validate in staging.
No customer delete: Stamped.io exposes no customer delete operation.
iPaaS.com Caveats
Source customer must exist in iPaaS.com: the customer must be present in iPaaS.com to be transferred.
External ID link: after the first successful transfer, the Stamped.io customer id is stored as the external ID on the iPaaS.com side and is used to route subsequent updates.
Setup Requirements
Stamped.io: an active Stamped.io connection configured on the subscription (credentials and store identifier).
iPaaS.com: to transfer customers automatically, enable the relevant Customer outbound triggers (Customer created and Customer updated) in the subscription's Outbound Data Flows section. Manual Sync is available at any time regardless of the outbound triggers.
Integration Flow
A customer transfer is initiated, either automatically by an enabled outbound trigger or manually from the Manual Sync page using the iPaaS.com Customer ID.
The integration creates the customer in Stamped.io if no external-ID link exists, or updates the linked Stamped.io customer when one does.
On success, the Stamped.io customer id is recorded as the external ID linking the two records.
When the subscription field is mapped and the desired state differs from the customer's current state in Stamped.io, the integration makes a follow-up call to subscribe or unsubscribe the customer by email.
Mappings
Add / Update Stamped.io Customer FROM iPaaS.com
iPaaS.com data type: Customer
This mapping collection does not have a mapping filter applied; all records are processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Stamped.io) | Description |
Field | CustomerNumber | externalId | Optional. Writes the iPaaS.com customer number into the Stamped.io external-id reference field so the Stamped.io record can be traced back to its iPaaS.com source. |
Field | EmailAddress | CustomerEmail | Optional. This Stamped.io field is deprecated or merged with Email; map Email as the customer's primary email. |
Field | EmailAddress | Required. Sets the customer's email in Stamped.io and must be unique — Stamped.io matches and de-duplicates customers by email. | |
Field | FirstName | FirstName | Recommended. Sets the customer's first name in Stamped.io. |
Field | LastName | LastName | Recommended. Sets the customer's last name in Stamped.io. |
Field | Comment | Notes | Optional. Copies the iPaaS.com customer comment into the Stamped.io customer notes. |
Subscription Handling
To control whether a customer is subscribed to Stamped.io surveys and review-request emails, map the customer's subscription field (for example, as a Static value of true or false). When the mapped value differs from the customer's current state in Stamped.io, the integration makes a dedicated follow-up call to subscribe or unsubscribe the customer. This reconciliation runs on both create and update. When the field is not mapped, the existing subscription state in Stamped.io is left unchanged.
Error Handling
User-facing errors for this collection are cataloged in the Stamped.io Error Messages article, grouped under the Add/Update Stamped.io Customer FROM iPaaS.com flow. Errors appear in the iPaaS.com Dashboard under Integration Monitoring and in the Error Logs.
Testing & Validation
From the Manual Sync page, transfer a single customer by iPaaS.com Customer ID and confirm the customer appears in Stamped.io with the mapped fields populated.
Confirm the external-ID link is recorded by re-running the transfer and verifying the same Stamped.io customer is updated rather than duplicated.
Map the subscription field to a Static value and confirm the customer's subscription state in Stamped.io changes accordingly, then flip the value and confirm it reverses.
Additional Notes / Out of Scope
Inbound sync from Stamped.io: out of scope. This collection writes from iPaaS.com to Stamped.io only and does not poll or receive changes originating in Stamped.io.
Customer deletion: out of scope, as Stamped.io exposes no customer delete operation.
Custom fields: not configured for this collection.