Introduction to Podium
Podium is an AI-powered lead generation and customer communication platform that consolidates chat, text, calls, and review management so businesses can capture and convert more inbound opportunities.
Used by local and multi-location businesses in retail, automotive, home services, and healthcare to manage customer communication at scale
Popular with sales and marketing teams that need a single inbox for all customer conversations regardless of channel
Connecting Podium to iPaaS.com enables lead and customer data captured through Podium to flow automatically into your CRM and ERP, keeping contact records current without manual data entry
API Version Support
The integration works with the Podium REST API (version 4), reached at Podium's API host with the credentials configured in your subscription's connection settings. See the Podium Connections and Settings and Podium API Endpoints articles for details.
Data Flows
The table below summarizes the data the integration can move between iPaaS.com and Podium, and in which direction. Arrows show the direction of transfer:
→ iPaaS.com writes the data to Podium
← iPaaS.com reads the data from Podium
←→ the data can move in both directions
Allow Initialization? indicates whether that data can be bulk-loaded from Podium when a subscription first connects. Whether a given flow is enabled, and in which direction, is configured per subscription during implementation.
iPaaS.com | Direction | Podium | Allow Initialization? |
Customer | ←→ | Contact | |
Invoice | ←→ | Invoice |
Contacts and invoices flow in both directions — written from iPaaS.com to Podium and captured back into iPaaS.com. Contacts carry their addresses, and invoices carry their line items and payment details. The integration synchronizes this contact and invoice data with your CRM and ERP; Podium's messaging channels (chat, text, calls, and reviews) are managed in Podium itself.
Versions and Release Notes
The integration follows its own version numbers. The current version is 1.0.1.
Version | Release Notes |
1.0.1 (current) | Every error the integration can record now carries a stable, searchable code and a plain-language explanation, so a message in the error logs identifies exactly what failed and what to do about it. Error wording was corrected throughout, operations a record type does not support now say so explicitly, and authentication failures no longer echo credential values. Includes routine platform maintenance. |
1.0.0 | Initial release: bi-directional synchronization of contacts (as customer records, with addresses) and invoices (with line items and payments) between iPaaS.com and Podium. |
Features by Release
The capabilities below are grouped by the version in which they became available. For the current behavior and any limitations of a given feature, see the linked reference articles and the Podium Known Limitations article.
Version 1.0.1 (current) — Coded error messages
Coded error messages: every error the integration can record now begins with a stable code in the form
PODM-{CATEGORY}-{NUMBER}— for examplePODM-EXTN-1004— which you can search for in the Error Messages article to find the cause and the steps to resolve it. A code never changes once published, so a message you look up today will still be findable later.Clearer error wording: messages were rewritten to describe the problem in subscriber terms rather than internal implementation detail, and several containing typos or naming the wrong thing were corrected.
Unsupported operations are now explicit: where a mapping collection is configured to perform an operation the integration does not implement for that record type, the error names the operation and the record type instead of reporting a generic failure.
Authentication errors no longer echo credential values: a failed token refresh now reports the failure without including the stored credential in the message.
Version 1.0.0 — Initial release
Contacts: contacts written to Podium as customer records, and captured back into iPaaS.com, including their addresses.
Invoices: invoices written to Podium, and captured back into iPaaS.com, including their line items and payment details.