# Podium setup for PopMCP If PopMCP shows Sign in with Podium with no fields, click it, sign in with your Podium login and approve. If it asks for a Client ID and Client Secret, apply for a developer account at developer.podium.com, create an app with PopMCP's redirect URL and the scopes listed here, and enter the app's details. - Auth: OAuth authorization - Setup time: 10 min, after Podium approves your developer account - API base URL: https://api.podium.com - Credentials screen: https://developer.podium.com/ - Provider docs: https://docs.podium.com/docs/oauth ## Approval required before this works Podium has no API keys, so connecting needs an OAuth app. To make one you apply for a developer account at developer.podium.com, and Podium reviews it. When PopMCP's own Podium sign-in is switched on, a person just signs in and none of this applies. - Typical wait: A few days for the developer account, according to Podium. After that an app takes minutes. - Cost: Podium's documents list no fee for a developer account or for using the API. You need a Podium account for your business: a developer account alone only reaches free test accounts. - Blocked until approved: Your own app cannot be created until Podium approves the developer account, so the connection cannot start before then. - Works meanwhile: Nothing on Podium's side until the welcome email arrives. PopMCP's other connectors work as usual. ## Before you begin - A Podium login at the business you want to connect. What the AI can do follows what this person can do in Podium. - To use your own app: a developer account at developer.podium.com. Podium reviews each application for a few days and sends a welcome email when you are in. - PopMCP's redirect URL from the connect form: https://app.popmcp.com/api/providers/podium/callback ## Get your credentials ### 1. Check whether you need an app at all Open Podium in PopMCP. If you see Sign in with Podium and no fields, click it, sign in with your Podium login and approve. You are done, so skip the rest of these steps. If the form asks for a Client ID and Client Secret, carry on. ### 2. Apply for a developer account Go to developer.podium.com and apply for a developer account. Podium takes a few days to review it and sends a welcome email to the address you gave. Nothing below can start until then. Screen: https://developer.podium.com/ ### 3. Create an app Log in at developer.podium.com, go to Dashboard and select Create App. Follow the steps on screen and name it something like `PopMCP`. You can change the name later. Screen: https://developer.podium.com/dashboard ### 4. Add the redirect URL and scopes On the app's side menu select OAuth. Set the redirect URL to `https://app.popmcp.com/api/providers/podium/callback` exactly, and tick the scopes you want the AI to have (the list is below). Podium suggests only the ones you need, and the scopes you tick in PopMCP must match this list. Screen: https://developer.podium.com/dashboard ### 5. Copy the Client ID and Client Secret Saving generates the app's credentials. Copy the Client ID and Client Secret now: the secret cannot be read again once you leave the page. You can regenerate it later, which does not revoke tokens already issued. Screen: https://developer.podium.com/dashboard ### 6. Enter them in PopMCP and sign in Enter the Client ID and Client Secret in PopMCP. Under More options, untick any scope your app does not hold. Click Sign in with Podium, sign in with a login from your business and approve what the page asks for. Then choose the organization and the PopMCP workspace. ## Fields PopMCP asks for - Client ID (clientId) [required]: Only needed for your own app. At developer.podium.com open your app, then its OAuth tab, and add the redirect URL shown here and the scopes below. Saving shows the Client ID and the Client Secret; the secret appears once, so copy it then. A new developer account waits a few days for Podium's review. - Client Secret (clientSecret) [required]: On the same tab, shown once when you save. Stored encrypted and used only on our server. - Scopes to ask for (scopes): These must match what you ticked on your app's OAuth tab: Podium can refuse a sign-in that asks for more than the app holds. write_users is off because only the two SCIM tools need it. ## Callback URL to register https://app.popmcp.com/api/providers/podium/callback ## Scopes requested - read_appointments - read_campaigns - read_contacts - read_feedback - read_locations - read_messages - read_organizations - read_payments - read_phones - read_products - read_reviews - read_templates - read_users - write_appointments - write_campaign_messages - write_campaigns - write_contacts - write_data_feed_event - write_locations - write_messages - write_payments - write_products - write_reviews - write_templates - write_writebacks ## Verify PopMCP shows Podium as Connected under your business name, and podium_account_overview returns your locations with their review scores. ## Troubleshooting ### Podium shows an error page instead of asking for access Cause: PopMCP's redirect URL is not on your app, it differs by a character, or the sign-in asks for a scope your app does not hold. Fix: On your app's OAuth tab set the redirect URL to `https://app.popmcp.com/api/providers/podium/callback`. In PopMCP, under More options, untick the scopes your app does not hold, and connect again. ### "Podium did not accept this app's Client ID and Client Secret" Cause: A value was mistyped, or the secret was regenerated. Fix: Copy the Client ID again from developer.podium.com and regenerate the Client Secret if you no longer have it. ### "Podium signed in but refused to list your locations" Cause: The app lacks read_locations, or the person who signed in cannot see locations. Fix: Tick read_locations on the app's OAuth tab and in PopMCP, then sign in as someone who can see your locations. ### "This login has no Podium location PopMCP can see" Cause: The login belongs to a test account with no locations, or a person with no location access. Fix: Sign in with a login from your business that has at least one location. ### A tool answers 403 and names a scope Cause: The app or the person who signed in does not have that permission. Fix: Add the scope on the app's OAuth tab and tick it in PopMCP, then connect again. If the scope is there, check what this person can do in Podium. ### A tool says Podium must allow-list the app Cause: Podium keeps listing payment accounts and changing opt-outs for apps it has allow-listed. Fix: Ask Podium's support team to allow-list your app. ### A contact cannot be found by its uid Cause: Podium finds a contact by email, phone number or a conversation uid, not by the contact's own uid. Fix: Use the email or phone number, or podium_find_contact to search by name. --- Source: https://www.docs.popmcp.com/docs/integrations/podium/