Summary
iPaaS.com Transactions of type Invoice can be transferred out to Podium as invoices. When such a Transaction is created in iPaaS.com, the integration creates the matching invoice in Podium, including its line items, and ensures the customer the invoice belongs to exists in Podium first. This keeps Podium invoices in step with iPaaS.com transaction data.
ID Format
Manual Sync ID Format: on the iPaaS.com Manual Sync page, enter the iPaaS.com Transaction identifier (for example, 197689).
External ID Format: after an invoice is written to Podium, iPaaS.com saves an external ID on a dedicated external-ID record that links the iPaaS.com Transaction to the Podium invoice, so later transfers route to the existing invoice rather than creating a duplicate.
Deleted Record Support
Outbound deletion is not supported. Deleting a Transaction in iPaaS.com does not remove the corresponding invoice in Podium, and delete mappings are not included in the default templates at the time this documentation was written.
Custom Field Support
This integration does not expose a separate custom-field configuration step. The Podium location for the invoice is read from an iPaaS.com Transaction custom field named locationUid, which subscribers or their MiSP must populate with a valid Podium location identifier.
Mapping Collection Status
Enabled. The parent invoice collection processes only Transactions of type Invoice. The line child collection enforces a minimum invoice total (see its filter below).
Trigger Events: Create (an iPaaS.com Transaction of type Invoice created).
Duplicate or Conflicting Mappings
The following collections operate on the iPaaS.com Transaction / Podium invoice:
Add Podium Invoice TO iPaaS.com and Update Podium Invoice TO iPaaS.com bring invoices from Podium into iPaaS.com (the opposite direction).
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 invoice data so a Transaction is not written in two directions in a way that conflicts.
Supported Child Collections
Parent Collection: Add Podium Invoice FROM iPaaS.com
Add Podium Invoice Line FROM iPaaS.com sends the Transaction's line items to the Podium invoice as part of the invoice transfer.
System Caveats
Podium Caveats
Location required: the invoice must carry a valid Podium location identifier in the locationUid custom field, or Podium cannot place the invoice.
Minimum line total: Podium requires the combined total of an invoice's line items to be greater than 50 cents. An invoice whose lines total 50 cents or less is rejected.
Customer ensured automatically: the customer the invoice belongs to is transferred to Podium automatically as a prerequisite (see Integration Flow). Subscribers do not need to sync the contact first.
iPaaS.com Caveats
Customer required: the Transaction must be linked to a customer (by customer identifier or email) so the invoice can be attached to the right Podium contact.
Setup Requirements
Automatic transfers require the subscriber to subscribe to the iPaaS.com Transaction created trigger under the subscription configuration's Outbound Data Flows section. The locationUid custom field on the Transaction must be populated with a valid Podium location identifier. Manual Sync is available regardless.
Integration Flow
An iPaaS.com Transaction of type Invoice is created, or a Transaction is synced manually by its identifier. Transactions of any other type are skipped.
The integration ensures the customer the invoice belongs to exists in Podium: it looks up the customer using the customer linked to the Transaction and, when the customer does not yet exist in Podium, creates it. If the customer cannot be created, the invoice transfer stops and the invoice is not sent.
The invoice is created in Podium with its number, location, and customer.
The Transaction's line items are sent to the Podium invoice through the Add Podium Invoice Line FROM iPaaS.com child collection, provided the combined line total meets Podium's minimum.
Mappings
Add Podium Invoice FROM iPaaS.com
Mapping Filter
Type == "Invoice"
Filter Description. Only Transactions with a type of Invoice are transferred to Podium. Transactions of any other type are skipped.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Podium) | Description |
Field |
| InvoiceNumber | The iPaaS.com transaction number, used as the Podium invoice number. |
Field |
| LocationUid | Required. The Podium location the invoice belongs to; populate the locationUid custom field with a valid Podium location identifier. |
Dynamic Formula | customer email resolved from the linked customer | ChannelIdentifier | Recommended. Identifies the customer the invoice is for; resolved from the linked customer, falling back to the Transaction email address. |
Dynamic Formula | customer name resolved from the linked customer | CustomerName | Recommended. The customer name on the invoice; resolved from the linked customer, falling back to the Transaction email address. |
Add Podium Invoice Line FROM iPaaS.com (Child)
Mapping Filter
if (Parent.Lines.Sum(x => x.UnitPrice*100*Qty) < 50)
{
throw new Exception("The total amount of all line items must be greater than 50.");
}
else
return true;Filter Description. Podium requires the combined total of all of an invoice's line items to be greater than 50 cents. When the total is below that amount, the transfer stops and the invoice is not sent, with the message: The total amount of all line items must be greater than 50.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Podium) | Description |
Dynamic Formula |
| Amount | Recommended. The line total, calculated from unit price and quantity and sent in the smallest currency unit (cents). |
Field |
| Description | Recommended. The line item description, so each line is labeled on the Podium invoice. |
Error Handling
Errors appear in Dashboard / Integration Monitoring / Error Logs. If the customer the invoice belongs to cannot be created in Podium, the invoice transfer stops and reports that the customer could not be created, which prevents the invoice from being sent. If the invoice's line items total 50 cents or less, the transfer stops with the message The total amount of all line items must be greater than 50. 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 Transaction of type Invoice in iPaaS.com with a linked customer, a populated locationUid custom field, and line items totaling more than 50 cents, and verify a matching invoice appears in Podium with its lines.
Verify that a Transaction whose linked customer does not yet exist in Podium causes the customer to be created automatically before the invoice is sent.
Verify that an invoice whose lines total 50 cents or less reports the minimum-total error and is not sent.
Verify that a Transaction of a type other than Invoice is skipped.
Manually sync a Transaction by its identifier from the Manual Sync page and confirm success.
Additional Notes
The customer is ensured in Podium automatically as a prerequisite; a failure to create the customer blocks the invoice transfer.
Populate the locationUid custom field on the Transaction with a valid Podium location identifier before enabling this collection.