Connect a module

Podium

Connect Podium so ShopMCP can mine customer conversations and reviews for FAQ opportunities, reputation themes, answer templates, and website content updates.

Read-only launch

Podium is available as a read-only connector. Customer-visible writes stay off while write scopes, app review, Data Feed setup, webhook signatures, and messaging safety are validated.

What Podium adds

Podium brings conversation and review demand into the same workspace as your store, CMS, Search Console, GA4, helpdesk, and lifecycle tools. The strongest first workflow is turning repeated customer questions into approved answers for PDPs, categories, blogs, support templates, and Podium templates.

Podium coverage in ShopMCP
Area	Examples
Customer voice	Conversations, conversation messages, reviews, feedback
Reputation	Review summaries, review-site summaries, review responses, review invites
Answer assets	Templates, campaigns, products, location context
Automation readiness	Locations, stored mappings, data-feed IDs, webhooks

Setup status

Open Settings - Integrations - Podium to connect a read-only Podium account. Podium's public API docs describe OAuth bearer tokens rather than Neto-style API keys, so ShopMCP supports a manual access-token fallback while the hosted OAuth app flow is pending.

Confirm the Podium developer app and redirect URI.
Confirm exact read scopes for locations, contacts, messages, reviews, templates, products, campaigns, feedback, and webhooks.
Leave the API version field blank unless Podium has confirmed a valid version value; ShopMCP otherwise uses the current unversioned API behavior.
Use the manual bearer-token fallback for sandbox validation when OAuth UI setup is not ready.
Confirm Data Feed fulfillment, field mapping, and webhook signature verification before enabling writes.

Read-only tools

Connected workspaces receive tools prefixed with podium_. The v1 read surface covers locations, contacts, conversations, messages, templates, campaigns, reviews, feedback, products, webhooks, invoices, payments, and compact playbook context tools. OAuth and manual-token connections register the same read tools; practical access is still limited by the scopes on the token Podium issued.

Writes and safety

Podium writes are not exposed in the first build. Future write candidates include templates, review responses, review invite links, customer-visible messages, Data Feed events, webhooks, contacts, and product images.

Customer-visible writes need approval

A Podium send, review response, template update, or Data Feed event can trigger a customer-facing workflow. ShopMCP must show the exact location, payload, customer-visible impact, and rollback limits before any write is enabled.

FAQ publishing boundary

Podium supplies the demand signal. Website FAQ publishing should happen through the connected website platform: Shopify, WordPress, BigCommerce, Magento, Neto, HubSpot CMS, or another CMS connector. Podium can then receive the approved answer as template or automation context.

Try these prompts

Run the Podium PDP FAQ Demand Miner over the last 60 days and tell me which questions should become PDP FAQs.
Use Podium reviews to find proof points we can safely add to product pages without overclaiming.
Audit Podium templates against recent conversations and reviews. Show missing, stale, duplicated, or risky templates.
Give me a Podium reputation snapshot by location and review site.
Check whether our Podium webhooks and data-feed mappings are ready for automation.
Blend Podium conversation themes with Shopify products and Google Search Console queries to find the best FAQ and content opportunities.