Summary

99minds VIP Tiers are represented in iPaaS.com as Customer Categories. Two related flows make up this area, both inbound (99minds → iPaaS.com): the VIP tier definition is synced into iPaaS.com as a Customer Category, and when a customer's tier changes in 99minds the customer's Customer Category assignment in iPaaS.com is updated to their current tier. The tier-assignment flow runs as part of the existing Customer integration on update only — it never creates a new customer.

ID Format

Manual Sync ID Format

On the iPaaS.com Manual Sync page, enter the 99minds Tier ID — for example, tier_01901310df875def01.

External ID Format

After a successful transfer, the 99minds Tier ID is saved as the external-id link. Subsequent events update the same iPaaS.com Customer Category rather than creating a duplicate. Whether an incoming tier is created or updated in iPaaS.com is determined by whether it is already linked by an external id, not by which event fired.

Deleted Record Support

Inbound delete is not supported. This integration creates and updates Customer Categories only; removing a tier in 99minds does not delete the linked Customer Category in iPaaS.com.

Tier removal is also not supported by the source system: once a VIP tier is assigned to a customer in 99minds, there is no way to remove or un-assign it through the 99minds interface or API. As a result, a "no tier" state cannot be propagated to iPaaS.com. See 99minds Integration Known Limitations.

Mapping Collection Status

Status: Enabled.
Trigger Events: Automatic transfers run when 99minds sends a tier-changed webhook to iPaaS.com. This webhook must be configured manually in 99minds (Settings → Webhooks → Manage → New Webhook) using your iPaaS.com subscription Webhook API Key — see the 99minds Installation Instructions. No automatic transfers occur until the webhook is configured. Manual Sync is available at any time. Whether an incoming tier is created or updated is determined by whether it is already linked by an external id, not by which event fired.

Duplicate or Conflicting Mappings

This is an inbound-only area (99minds → iPaaS.com). There is no opposing iPaaS.com → 99minds Customer Category collection, so there is no two-direction overwrite concern for tiers.

99minds is the source of truth for the VIP-tier Customer Category only. When a customer's tier changes, the customer's VIP-tier Customer Category is updated to their current tier — only one VIP tier is assigned at a time, so a new tier replaces the previous tier's Customer Category (the latest tier wins) rather than leaving both assigned. Any other Customer Categories the subscriber assigned in iPaaS.com (for example, categories assigned by an ERP or another system) are preserved and are not removed by a tier change.

Collision Handling

This integration does not use iPaaS.com collision handling — it is not supported for this direction. Whether an incoming tier is created or updated is determined by whether it is already linked by an external id; there is no collision recovery step.

Supported Child Collections

None — this is a standalone collection with no dependent child collections. The tier-assignment step runs as part of the existing Customer update flow, which has its own documentation.

System Caveats

99minds Caveats

A customer's current tier is read from the customer's tier history in 99minds. The most recent tier change determines the current tier.
Renaming a tier in 99minds creates a new Customer Category in iPaaS.com rather than renaming the existing one, because matching is by external id.
Once a tier is assigned to a customer in 99minds, it cannot be removed (through the 99minds interface or API), so a customer cannot be returned to a "no tier" state.

iPaaS.com Caveats

The Customer Category Name is required and must be unique in iPaaS.com. If a category with the same name already exists, the existing record is updated rather than duplicated.
A tier assignment is applied only to a customer that is already linked between iPaaS.com and 99minds. If the customer cannot be matched, the assignment is not applied and no customer is created — the event is surfaced for follow-up rather than silently dropped.
A tier change updates only the customer's VIP-tier Customer Category; other Customer Categories on the customer are preserved.

Setup Requirements

iPaaS.com Configuration

No custom fields are required for the Customer Category. The customer-to-99minds linkage used by the tier-assignment flow must already be established by the existing Customer integration.

99minds Configuration

Configure the tier-changed webhook in 99minds (Settings → Webhooks → Manage → New Webhook) using your iPaaS.com subscription Webhook API Key. See the 99minds Installation Instructions.

Authentication & Security

Authentication uses the 99minds API key / Webhook API Key configured on the subscription — see the 99minds Installation Instructions.

Integration Flow

Tier definition into a Customer Category:

A tier is synced into iPaaS.com (as part of a tier-assignment transfer, or by Manual Sync of a Tier ID).
The integration retrieves the tier from 99minds and matches an existing iPaaS.com Customer Category by name; if found it links the 99minds Tier ID as the external id, otherwise it creates the Customer Category. The Tier ID is the durable match key thereafter.

Customer tier assignment:

99minds sends a tier-changed webhook for a customer.
The integration resolves the iPaaS.com customer through the existing customer linkage and reads the customer's current tier from 99minds.
It ensures the matching Customer Category exists, then updates the customer's VIP-tier Customer Category assignment to the current tier. The previous VIP-tier category is replaced (the latest tier wins); other (non-VIP) categories are preserved. No duplicate category is appended, and no customer is created when the customer cannot be matched.

Mappings

Add/Update 99minds Tier TO iPaaS.com

Mapping Filter

This mapping collection does not have a mapping filter applied. All records routed to it are processed.

Description: Creates or updates the iPaaS.com Customer Category from the 99minds tier, matched durably by the 99minds Tier ID. The Tier ID is saved as the Customer Category's external id and is the durable match key (it is not a configurable mapping row).

Mapping Type	Source Field (99minds)	Destination Field (iPaaS.com)	Description
Field	Tier name	Customer Category Name	Required. The Name must be mapped — it is required and unique in iPaaS.com. If a category with the same name already exists, the existing record is updated rather than duplicated.
Field	Tier description	Customer Category Description	Optional. The human-readable tier description, copied from the 99minds tier when present.

Update 99minds Customer TO iPaaS.com — VIP tier assignment

The tier-to-category assignment is part of the Update 99minds Customer TO iPaaS.com collection. It is intentionally not part of the Add collection, because a tier change must never create a new customer — it only updates an existing, matched customer's category. The rest of that collection's mappings are covered in the 99minds to iPaaS.com Customer Mapping Documentation; only the tier-assignment mapping is shown here.

Description: Updates a matched iPaaS.com customer's VIP-tier Customer Category assignment to their current 99minds tier. The previous VIP-tier category is replaced (latest tier wins) and the customer's other (non-VIP) categories are preserved.

Mapping Type	Source Field (99minds)	Destination Field (iPaaS.com)	Description
Dynamic Formula	Customer's current tier	Categories	Maps the customer's current 99minds VIP tier (for example, "Gold" or "Silver") to the matching iPaaS.com Customer Category, so that whenever the customer's tier changes in 99minds their iPaaS.com category is updated to match. Replaces the previous VIP-tier category and preserves the customer's other categories.

Customer Category assignment formula:

return await Convert99MindsTierToiPaaSCategories(CustomerId, Tier_CurrentTierId);

Error Handling

Customer not matched — a tier assignment is applied only to a customer already linked between iPaaS.com and 99minds. When the customer cannot be matched, the assignment is not applied and no customer is created; the event is surfaced as an error for follow-up rather than silently dropped.
Customer Category Name required / not unique — the Name is required and unique in iPaaS.com. A tier whose name collides with an existing category updates that existing category rather than creating a duplicate.
Tier removal not available — because 99minds provides no way to remove a tier from a customer, a "no tier" state cannot be sent to iPaaS.com; plan tier management accordingly.

Testing & Validation

Test Scenarios

Tier definition created — sync a 99minds tier and confirm an iPaaS.com Customer Category is created with the matching name and linked by the Tier ID.
Tier definition updated — change a tier's description in 99minds and confirm the same Customer Category is updated, with no duplicate created.
No duplicate — sync the same tier again and confirm no duplicate Customer Category is created.
Customer tier assignment — change a linked customer's tier in 99minds and confirm the customer's VIP-tier Customer Category reflects the new tier.
Unmatched customer — change the tier for a customer that is not linked in iPaaS.com and confirm no customer is created and no assignment is applied (the event is surfaced for follow-up).
Latest tier wins — change a linked customer's tier twice and confirm only the latest VIP-tier Customer Category remains assigned.
Other categories preserved — assign a non-VIP Customer Category in iPaaS.com, then change the customer's tier, and confirm the non-VIP category survives.

Validation Checklist

Tier definitions create or update the matching iPaaS.com Customer Category with no duplicates.
A linked customer's VIP-tier Customer Category updates on a tier change; unmatched customers are neither created nor assigned.
Only the latest VIP tier remains assigned; other categories are preserved.
The Customer Category exists before a customer is assigned to it.

Additional Notes

The tier-assignment mapping is part of the Update Customer collection only; a tier change updates an existing customer and never creates one.
99minds is the source of truth for the VIP-tier category only; categories assigned in iPaaS.com from other systems are preserved across tier changes.
A tier cannot be removed from a customer in 99minds, so iPaaS.com cannot reflect a return to "no tier."

99minds to iPaaS.com Customer Category (VIP Tier) Mapping Documentation