Summary
iPaaS.com Customers can be transferred out to Podium as contacts. When a Customer is created or updated in iPaaS.com, the integration creates or updates the matching Podium contact, sending the name, email, phone number, and the Customer's first address. This keeps Podium contacts in step with iPaaS.com customer data.
ID Format
Manual Sync ID Format: on the iPaaS.com Manual Sync page, enter the iPaaS.com Customer identifier (for example, 288).
External ID Format: after a Customer is written to Podium, iPaaS.com saves an external ID on a dedicated external-ID record that links the iPaaS.com Customer to the Podium contact, so later transfers route to the existing contact rather than creating a duplicate. Podium identifies a contact by its email address or phone number, so those values are used to locate the contact when it already exists.
Deleted Record Support
Outbound deletion is not supported. The integration's Customer delete operation is not implemented, delete mappings are not included in the default templates, and deleting a Customer in iPaaS.com does not remove the corresponding contact in Podium at the time this documentation was written.
Custom Field Support
This integration does not expose a separate custom-field configuration step. The contact's phone number is read from an iPaaS.com Customer custom field named Phone Number and reformatted for Podium; no additional setup is required.
Mapping Collection Status
Enabled. This collection has no mapping filter, so every Customer it receives is processed.
Trigger Events: Create, Update (an iPaaS.com Customer created or updated).
Duplicate or Conflicting Mappings
The following collections also operate on the iPaaS.com Customer / Podium contact:
Add Podium Contact TO iPaaS.com brings contacts from Podium into iPaaS.com (the opposite direction).
Delete Podium Contact TO iPaaS.com removes the iPaaS.com Customer when the contact is deleted in Podium.
Before enabling these collections, review and customize your mapping collection filters and Add/Update settings to match your business rules, and define which system is the source of truth for customer data so a contact is not written in two directions in a way that conflicts.
Supported Child Collections
This collection has no child collections. The contact's address is written directly on the contact record from the Customer's first address.
System Caveats
Podium Caveats
Contact identified by email or phone: Podium matches an existing contact by its email address or phone number. A Customer without an email address or phone number may create a new contact rather than updating an existing one.
Location must exist: the location named in the Locations mapping must exist in Podium. Replace the shipped example location with a real Podium location name so contacts are associated correctly.
iPaaS.com Caveats
First address used: only the first address on the iPaaS.com Customer is written to the Podium contact.
Setup Requirements
Automatic transfers require the subscriber to subscribe to the iPaaS.com Customer created and updated triggers under the subscription configuration's Outbound Data Flows section. Until those triggers are enabled, no automatic transfers occur; Manual Sync is available regardless. Before enabling this collection, replace the example location in the Locations mapping with a Podium location name that exists in your Podium account.
Integration Flow
An iPaaS.com Customer created or updated event is received, or a Customer is synced manually by its identifier.
The integration builds the Podium contact from the Customer: the name from first and last name, the email address, the phone number (read from the Phone Number custom field and reformatted for Podium), and the first address.
The integration locates the contact in Podium by email address or phone number and updates it, or creates a new contact when none is found.
The contact is associated with the Podium location named in the Locations mapping.
Mappings
Add/Update Podium Contact FROM iPaaS.com
This collection has no mapping filter; all Customers are processed.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Podium) | Description |
Field |
| Identifies the contact in Podium; Podium locates or creates a contact by its email address (or phone number). | |
Dynamic Formula |
| Name | Recommended. The contact name, built from the Customer's first and last name joined by a space. |
Dynamic Formula |
| PhoneNumber | Optional. The first value of the Phone Number custom field, reformatted for Podium. |
Dynamic Formula | first address | AddressLine1 | Optional. First line of the Customer's first address. |
Dynamic Formula | first address | AddressLine2 | Optional. Second line of the address. |
Dynamic Formula | first address | City | Optional. City. |
Dynamic Formula | first address | State | Optional. State or province. |
Dynamic Formula | first address | Country | Optional. Country. |
Dynamic Formula | first address | PostalCode | Optional. Postal or ZIP code. |
Dynamic Formula | Podium location resolved by name | Locations | Associates the contact with a Podium location. Placeholder value — replace during implementation: the shipped mapping looks up a location named Test Location A, an example value that will not exist in a real Podium account; replace it with your actual Podium location name before enabling this collection. |
Error Handling
Errors appear in Dashboard / Integration Monitoring / Error Logs. If the contact cannot be created or updated in Podium, the transfer reports that the contact could not be created or updated. For the full catalog of messages a subscriber may see and how to resolve them, see the Podium Error Messages article.
Testing & Validation
Create a Customer in iPaaS.com with a name, email, phone number, and address, and verify a matching contact appears in Podium with the mapped values and the correct location.
Update the Customer's name in iPaaS.com and verify the same Podium contact is updated rather than a new one created.
Confirm the Locations mapping references a real Podium location before enabling; verify the contact is associated with that location.
Manually sync a Customer by its identifier from the Manual Sync page and confirm success.
Additional Notes
The Locations mapping ships with an example location (Test Location A) that must be replaced with a real Podium location name before go-live.
Only the first address on the Customer is written to Podium.