Summary
Podium contacts can be transferred into iPaaS.com as Customers. When a contact is created, updated, or deleted in Podium, the integration keeps the matching iPaaS.com Customer in step, including the contact's name, email, phone number, and address. This maintains accurate customer data in iPaaS.com and reliable synchronization between Podium and iPaaS.com.
ID Format
Manual Sync ID Format: on the iPaaS.com Manual Sync page, enter the Podium contact identifier (the contact Uid), for example 0a1b2c3d-4e5f-6789-abcd-ef0123456789.
External ID Format: after a contact is transferred, iPaaS.com saves an external ID on a dedicated external-ID record that links the Podium contact to the iPaaS.com Customer, keyed on the contact's phone number when present, otherwise the contact's email address. This external-ID record is the primary match that routes later updates for the same contact to the existing Customer. On a first sync, when no external-ID record exists yet, iPaaS.com also looks for an existing Customer whose email address matches and links to it rather than creating a duplicate.
Deleted Record Support
Deletions are supported inbound. When a contact is deleted in Podium, the Delete Podium Contact TO iPaaS.com collection removes the matching Customer in iPaaS.com, using the external-ID link recorded when the contact was first transferred. A contact that was never transferred has no link and no Customer to remove. Deletions are driven by the contact.deleted event, which the subscriber enables under Inbound Data Flows.
Custom Field Support
This integration does not expose a separate custom-field configuration step. Several Podium contact values are captured into iPaaS.com custom fields as ordinary mapping destinations — the contact's first phone number, its associated location identifiers, its conversation identifiers, and selected contact attributes such as a birthday. These are configured directly in the mapping and require no additional setup.
Mapping Collection Status
Enabled. The parent contact collection has no mapping filter, so every contact it receives is processed. The child address collection runs only when the contact has address details.
Trigger Events: Create, Update, Delete (a Podium contact created, updated, or deleted).
Duplicate or Conflicting Mappings
The following collections also operate on the Podium contact / iPaaS.com Customer:
Add/Update Podium Contact FROM iPaaS.com writes Customers from iPaaS.com out to Podium (the opposite direction).
Delete Podium Contact TO iPaaS.com removes the 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 Customer is not written in two directions in a way that conflicts.
Supported Child Collections
Parent Collection: Add Podium Contact TO iPaaS.com
Add Podium Contact Address TO iPaaS.com creates the Customer's address from the contact's address details. It is linked to the parent contact transfer and runs as part of it whenever the contact has an address.
System Caveats
Podium Caveats
Single name field: Podium stores one Name value per contact rather than separate first and last names. The integration uses the first word as the first name and the remainder as the last name.
First value used: a contact can have multiple emails and phone numbers in Podium; the integration uses the first email and the first phone number.
Attributes by label: contact attributes such as a birthday are read by matching the attribute label (case-insensitively). The attribute must exist on the contact with the expected label for a value to transfer.
iPaaS.com Caveats
Unique email: iPaaS.com requires each Customer email address to be unique. If two Podium contacts share an email address, they resolve to the same iPaaS.com Customer.
Email required: a contact must have an email address to be transferred, because iPaaS.com requires the Customer email address.
Setup Requirements
Automatic transfers require the subscriber to select the Podium contact events (contact.created, contact.updated, contact.deleted) under the subscription configuration's Inbound Data Flows section. The integration creates the corresponding webhook in Podium; its scope — the Organization, all Locations, or a specific Location — is controlled by the Webhook Subscription To Organization Or Location and Location subscription settings. See the Podium Installation Instructions for the full webhook setup. Until the events are enabled, no automatic transfers occur; Manual Sync is available regardless.
Integration Flow
A Podium contact event (created, updated, or deleted) is received, or a contact is synced manually by its Uid.
The integration retrieves the full contact record from Podium.
iPaaS.com checks for an existing Customer with the same email address; when one is found, the Podium contact is linked to that Customer instead of creating a duplicate.
The Customer is created or updated in iPaaS.com from the mapped contact fields.
When the contact has address details, the address is created through the Add Podium Contact Address TO iPaaS.com child collection.
When the event is a deletion, the linked Customer is removed instead.
Mappings
Add Podium Contact TO iPaaS.com
This collection has no mapping filter; all contacts are processed.
Mapping Type | Source Field (Podium) | Destination Field (iPaaS.com) | Description |
Field |
| CustomerNumber | Required. The Podium contact's unique identifier, written to CustomerNumber for identification and visibility on the Customer record. The external-ID link that routes later updates is keyed on the contact's phone number or email address (see ID Format), not on this value. |
Dynamic Formula | first word of | FirstName | Recommended. First word of the contact name. iPaaS.com requires at least one of first name, last name, or company. |
Dynamic Formula | remaining words of | LastName | Recommended. All words after the first, or the single word if only one is present. |
Dynamic Formula | first | EmailAddress | Required, must be unique. First email address on the contact; the transfer fails if the contact has none. |
Dynamic Formula | first | Phone Number | Optional. First phone number on the contact. |
Dynamic Formula | attribute labeled | Birthday | Optional. Value of the contact attribute whose label is Birthday. |
Dynamic Formula | attribute labeled | Secret | Optional. Placeholder value — replace during implementation: this is an example mapping — the attribute label Opportunity Value and the destination field Secret are example values; replace with the Podium attribute you actually want to capture, or remove the mapping. |
Dynamic Formula |
| Locations | Optional. The identifiers of the contact's locations, joined by the pipe character ( | ). |
Dynamic Formula |
| Conversations | Optional. The identifiers of the contact's conversations, joined by the pipe character ( | ). |
Add Podium Contact Address TO iPaaS.com (Child)
Mapping Filter
Parent.Address != null
Filter Description. This child collection only runs when the parent contact has an address. When the contact has no address details, no address record is created and the contact transfers without one.
Mapping Type | Source Field (Podium) | Destination Field (iPaaS.com) | Description |
Static |
| PreventDuplicate | System control value that prevents iPaaS.com from creating a duplicate address when a matching one already exists on the Customer. |
Dynamic Formula |
| Address1 | Recommended. First line of the contact's address. |
Dynamic Formula |
| Address2 | Optional. Second line of the address (for example, a suite or unit). |
Dynamic Formula |
| City | Recommended. City. |
Dynamic Formula |
| Region | Recommended. State or province (Podium records this as State). |
Dynamic Formula |
| Country | Recommended. Country. Add a lookup translation if a code-versus-name conversion is needed. |
Dynamic Formula |
| PostalCode | Recommended. Postal or ZIP code. |
Dynamic Formula | first | PhoneNumber | Optional. First phone number on the parent contact. |
Error Handling
Errors encountered during a transfer appear in Dashboard / Integration Monitoring / Error Logs. During duplicate matching, if the integration cannot link a contact to an existing Customer by email, the transfer surfaces an error indicating the link could not be completed and that duplicate customer records may result. 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 new contact in Podium with a name, email, and phone number, and verify a matching Customer appears in iPaaS.com with the mapped values.
Update the contact's email in Podium and verify the change propagates to the same Customer rather than creating a duplicate.
Create a contact with address details and verify the Customer's address is created; create one without an address and verify the Customer transfers without an address.
Attempt a contact with no email and confirm the transfer reports the required-field error.
Delete the contact in Podium and verify the matching Customer is removed in iPaaS.com.
Manually sync a contact by its Uid from the Manual Sync page and confirm success.
Additional Notes
Only the address carried on the Podium contact is transferred; the integration does not retrieve additional addresses.
Podium stores a single name value per contact; the first-word / remaining-words split may need review for contacts whose names do not follow a simple first-last pattern.