99minds from iPaaS.com Customer Mapping Documentation
99minds customers can be created and updated from iPaaS.com customer data through Manual Sync or an outbound transfer. On creation the integration creates a new 99minds customer from the mapped name, email, and contact identifier, provisions a 99minds loyalty card for that customer at a starting balance of 0, and links the new 99minds customer to the iPaaS.com record. On update it locates the already-linked 99minds customer and keeps its name, email, and contact identifier in sync with iPaaS.com. Whether a transfer creates or updates the 99minds customer is determined by whether the iPaaS.com record is already linked by an external id, not by which outbound scope fired.
ID Format
Manual Sync ID Format
On the iPaaS.com Manual Sync page, enter the iPaaS.com Customer Id — for example, 158056.
External ID Format
After a successful transfer, the 99minds Customer ID is saved as the external-id link on the iPaaS.com customer. Subsequent transfers use this link to target the same 99minds customer rather than creating a duplicate.
Deleted Record Support
Outbound delete is not supported. The Customer Delete operation is not implemented, delete mappings are not included in the default template, and removing a customer in iPaaS.com does not delete the customer in 99minds; deletions do not propagate.
Mapping Collection Status
Status: Enabled.
Trigger Events: Outbound transfers fire from the iPaaS.com Outbound Data Flows the subscriber subscribes to — customer/created, customer/updated, customer/deleted. Manual Sync is available at any time. Whether a transfer creates a new 99minds customer or updates an existing one is determined by whether the iPaaS.com record is already linked by an external id, not by which scope fired.
Duplicate or Conflicting Mappings
Several mapping collections operate on the same 99minds Customer:
Add 99minds Customer FROM iPaaS.com — creates the 99minds customer from an iPaaS.com customer.
Update 99minds Customer FROM iPaaS.com — updates an existing 99minds customer from iPaaS.com.
Add 99minds Customer TO iPaaS.com — creates the iPaaS.com customer from a 99minds customer.
Update 99minds Customer TO iPaaS.com — updates the iPaaS.com customer's 99minds loyalty data.
Review each collection's filters and Add/Update settings before enabling, and decide which system is the source of truth for customer data so the same record is not written from both directions in a conflicting way.
Collision Handling
Collision handling is not used for Customer. Add and Update routing is determined by whether the iPaaS.com record is already linked to a 99minds customer by an external id.
Supported Child Collections
None — these are standalone collections with no dependent child collections.
System Caveats
99minds Caveats
Email is mandatory to create a customer in 99minds. A customer with a matching email resolves to the existing 99minds record rather than creating a duplicate.
The Phone field stores whatever value is mapped to it; in these collections that is the iPaaS.com Customer Number, so the stored value reflects that identifier rather than a dialable phone number.
On update, the customer must already exist in 99minds — the Update collection updates rather than creates. The integration locates the existing 99minds customer by the identifier linked when the customer was first synced.
Loyalty card balance is not changed by these collections. Loyalty point balances are managed by the Loyalty Card Transaction collections.
iPaaS.com Caveats
Email Address and Customer Number are required on every iPaaS.com customer, and Email Address must be unique. Records that do not meet these conditions cannot exist in iPaaS.com and will not transfer.
Integration-Specific Caveats
On creation, a 99minds loyalty card is provisioned for the new customer at a fixed starting balance of 0; the balance is adjusted later through the Loyalty Card Transaction collections, not by these collections.
The 99minds Phone field carries the iPaaS.com Customer Number as a round-trip identifier so the same value exists on both systems. If a real phone number is required in 99minds, remap this field to an actual phone source.
Setup Requirements
iPaaS.com Configuration
Subscribe to the Customer outbound triggers under Outbound Data Flows: customer/created, customer/updated, customer/deleted. No automatic transfers occur until those outbound subscriptions are enabled.
99minds Configuration
No 99minds-side configuration is required for these collections beyond authentication. The 99minds customer is created or located directly by the integration.
Authentication & Security
Authentication uses the 99minds API key configured on the subscription — see the 99minds Installation Instructions.
Integration Flow
Resolve whether the iPaaS.com customer is already linked to a 99minds customer by an external id.
On a new customer (Add), create the customer in 99minds from the mapped name, email, and contact identifier, provision a 99minds loyalty card at a starting balance of 0, and save the returned 99minds Customer ID as the external-id link.
On an existing customer (Update), locate the linked 99minds customer by its saved identifier and update its name, email, and contact identifier from iPaaS.com.
A duplicate email resolves to the existing 99minds customer rather than creating a new one.
Mappings
Add 99minds Customer FROM iPaaS.com
No mapping filter is applied to this collection. All records routed to it are processed.
Description: Creates a customer in 99minds from an iPaaS.com customer record, provisions a 99minds loyalty card at a starting balance of 0, and links the new 99minds Customer ID back to the iPaaS.com customer.
Mapping Type | Source Field (iPaaS.com) | Destination Field (99minds) | Description |
Field | EmailAddress | The customer's email address is sent to 99minds. This is a required field — 99minds cannot create a customer without an email, and iPaaS.com already requires Email Address on every customer, so a value is always available. If a 99minds customer with the same email already exists, 99minds links to that existing customer instead of creating a duplicate. | |
Dynamic Formula | (see formula below) | Name | Builds the 99minds customer's full name from the iPaaS.com First Name and Last Name. This is a recommended field — it sets the customer's display name in 99minds. If both source names are empty, the 99minds name is left blank. |
Field | CustomerNumber | Phone | Carries the iPaaS.com Customer Number into the 99minds Phone field so the same identifier exists on both systems for matching. Important: the value stored here is the Customer Number, which may not be a dialable phone number. If a real phone number is required in 99minds, remap this field to an actual phone source. |
Static | "0" | Amount | Sets the new 99minds customer's initial loyalty card balance to 0 at creation. Loyalty point balances are adjusted later through the Loyalty Card Transaction collections, not by this collection. Leave this at 0 unless an initial balance is intended at customer creation. |
Name formula:
FirstName + " " + LastName
Update 99minds Customer FROM iPaaS.com
No mapping filter is applied to this collection. All records routed to it are processed.
Description: Updates an existing 99minds customer from an iPaaS.com customer record, keeping the 99minds customer's name, email, and contact identifier in sync. This collection updates only — it does not create a new customer; the existing 99minds customer is located by the identifier linked when the customer was first synced.
Mapping Type | Source Field (iPaaS.com) | Destination Field (99minds) | Description |
Field | EmailAddress | Updates the 99minds customer's email from iPaaS.com. This is a required field for the 99minds customer. This collection updates an existing 99minds customer (located by the identifier linked when the customer was first synced); it does not create new customers. | |
Dynamic Formula | (see formula below) | Name | Updates the 99minds customer's full name from the iPaaS.com First Name and Last Name. Recommended so the 99minds display name stays in sync with iPaaS.com. |
Field | CustomerNumber | Phone | Keeps the iPaaS.com Customer Number stored in the 99minds Phone field — the same identifier round-trip used by the Add collection. The value is the Customer Number and may not be a dialable phone number; remap to an actual phone source if a real phone number is required in 99minds. Loyalty balance is not changed by this collection. |
Name formula:
FirstName + " " + LastName
Error Handling
Customer cannot be created without an email — 99minds requires an email to create a customer. Because iPaaS.com requires Email Address on every customer, a value is always available; if a transfer fails for a missing email, confirm the source record has a valid Email Address.
Customer not found on update — the Update collection updates an existing 99minds customer located by its linked identifier. If the linked 99minds customer no longer resolves, confirm the customer still exists in 99minds and was synced (linked) by the Add collection first.
Testing & Validation
Test Scenarios
Create a new customer — transfer an iPaaS.com customer that is not yet linked; confirm a new 99minds customer is created with the mapped email, name, and phone (Customer Number), a loyalty card is provisioned at balance 0, and the 99minds Customer ID is saved as the external-id link.
Duplicate email — transfer a customer whose email already exists in 99minds; confirm the transfer resolves to the existing 99minds customer rather than creating a duplicate.
Update an existing customer — change the name, email, or Customer Number on a linked iPaaS.com customer and re-transfer; confirm the linked 99minds customer is updated in place.
Name composition — confirm the 99minds Name is composed as First Name followed by Last Name, and that an empty first and last name leaves the 99minds name blank.
Phone round-trip — confirm the iPaaS.com Customer Number is stored in the 99minds Phone field.
Manual Sync — enter an iPaaS.com Customer Id on the Manual Sync page and confirm the customer is created or updated as expected.
Validation Checklist
New customers are created in 99minds with the correct email, name, and phone (Customer Number).
A 99minds loyalty card is provisioned at balance 0 on creation.
The external-id link (99minds Customer ID) is saved and reused on subsequent updates.
Updates target the existing linked 99minds customer rather than creating a duplicate.
Duplicate emails resolve to the existing 99minds customer.
Additional Notes
Email is required on both systems and is the primary key for resolving a 99minds customer; a matching email resolves to the existing 99minds customer rather than creating a duplicate.
The 99minds Phone field carries the iPaaS.com Customer Number as a round-trip identifier, not a dialable phone number; remap it to an actual phone source if a true phone number is required in 99minds.
Loyalty card balance is managed by the Loyalty Card Transaction collections; these collections do not change the balance after the initial 0 set at creation.
Related Documents
Setup & Reference
Mapping Documentation