How to Integrate Retool with Podia

Log in to your Podia account and navigate to Settings → Integrations. Look for the API section where your API key is displayed. If you don't see an API section, your current Podia plan may not include API access — check Podia's current plan features or contact Podia support to confirm API availability for your account. Copy your API key. Before creating the Retool resource, store your API key securely. Navigate to your Retool instance's Settings tab → Configuration Variables, click Create Variable, name it PODIA_API_KEY, paste your API key, and mark it as Secret to restrict visibility to resource configurations. Navigate to the Resources tab in your Retool instance and click Add Resource. Select REST API from the resource type list. Name the resource 'Podia API'. In the Base URL field, enter https://developers.podia.com (or the current API base URL from Podia's API documentation — verify at developers.podia.com). In the Authentication section, select Bearer Token and enter {{ retoolContext.configVars.PODIA_API_KEY }} in the Token field. Add a default header: Key = Content-Type, Value = application/json. Click Save Changes. Test the resource by querying a basic endpoint like /v1/products to confirm authentication works.

Create queries to retrieve your Podia product catalog. In your Retool app, open the Code panel and click the + icon to add a query. Name it getProducts, select the Podia API resource, set Method to GET, and set the path to /v1/products. POdia's products endpoint returns all products in your store — courses, digital downloads, memberships, coaching packages, and webinars. Each product has an id, name, type, price, status (published/draft), and sales count. Create a JavaScript transformer to format the products list and calculate revenue indicators: Bind a Retool Table component to the transformer output. Add a Select dropdown to filter products by type (course, membership, download). Add Stat components showing total products count, total published products, and a breakdown by product type. Create a second query named getProductDetails with Method GET and path /v1/products/{{ table_products.selectedRow.id }} to fetch detailed information about a selected product, including its price variants, enrollment count, and completion rates for courses.

1// JavaScript transformer — format Podia products for display
2const products = data?.products || data?.data || [];
3
4// Count by type
5const typeCounts = products.reduce((acc, p) => {
6  const type = p.type || p.product_type || 'unknown';
7  acc[type] = (acc[type] || 0) + 1;
8  return acc;
9}, {});
10
11const productList = products.map(product => {
12  const price = parseFloat(product.price || product.price_cents / 100 || 0);
13  const type = product.type || product.product_type || 'unknown';
14
15  return {
16    id: product.id,
17    name: product.name || 'Untitled Product',
18    type: type,
19    type_label: type === 'course' ? 'Course'
20      : type === 'membership' ? 'Membership'
21      : type === 'download' ? 'Digital Download'
22      : type === 'coaching' ? 'Coaching'
23      : type === 'webinar' ? 'Webinar'
24      : type,
25    price: price > 0 ? `$${price.toFixed(2)}` : 'Free',
26    price_num: price,
27    status: product.published ? 'Published' : 'Draft',
28    sales_count: product.sales_count || product.purchases_count || 0,
29    created_at: product.created_at
30      ? new Date(product.created_at).toLocaleDateString()
31      : 'N/A',
32    estimated_revenue: price > 0 && product.sales_count
33      ? `$${(price * product.sales_count).toFixed(2)}`
34      : 'N/A'
35  };
36});
37
38return productList;

Create queries to retrieve sales transactions and revenue data. Create getSales with Method GET and path /v1/sales. Add URL parameters for filtering: Key = page, Value = {{ pagination.pageNumber || 1 }}, Key = per_page, Value = 50. For date-range filtering (if supported by Podia's API), add: Key = from, Value = {{ dateRange.start.toISOString().split('T')[0] }}, Key = to, Value = {{ dateRange.end.toISOString().split('T')[0] }}. Podia's sales records typically include: sale_id, product_name, product_type, buyer_email, buyer_name, amount, currency, status (completed, refunded, disputed), and created_at timestamp. Create a JavaScript transformer that calculates revenue metrics from the sales data: Bind a Retool Table to the sales transformer output. Add Stat components at the top of your dashboard showing: total revenue in the selected period, number of sales, average order value, and refund rate. Add a Chart component showing revenue by day or week. Configure it as a Line chart with date on the X-axis and cumulative revenue on the Y-axis for the selected period. Add a second grouped bar chart showing sales count by product type. Create a separate query named getMembershipRevenue if Podia exposes a dedicated subscriptions/memberships endpoint — this gives you MRR (Monthly Recurring Revenue) data separate from one-time purchases.

1// JavaScript transformer — calculate revenue analytics from Podia sales
2const sales = data?.sales || data?.data || [];
3
4// Revenue calculations
5const completedSales = sales.filter(s =>
6  s.status === 'completed' || s.status === 'paid' || !s.status
7);
8const refundedSales = sales.filter(s => s.status === 'refunded');
9
10const totalRevenue = completedSales.reduce((sum, s) => {
11  const amount = parseFloat(s.amount || s.amount_cents / 100 || 0);
12  return sum + amount;
13}, 0);
14
15const refundedRevenue = refundedSales.reduce((sum, s) => {
16  return sum + parseFloat(s.amount || 0);
17}, 0);
18
19// Format individual sales for table
20const saleRows = sales.map(sale => {
21  const amount = parseFloat(sale.amount || (sale.amount_cents ? sale.amount_cents / 100 : 0) || 0);
22  return {
23    id: sale.id,
24    product_name: sale.product_name || sale.product?.name || 'Unknown Product',
25    product_type: sale.product_type || sale.product?.type || 'N/A',
26    buyer_name: sale.buyer_name || sale.customer_name || 'N/A',
27    buyer_email: sale.buyer_email || sale.customer_email || 'N/A',
28    amount: `$${amount.toFixed(2)}`,
29    amount_num: amount,
30    status: sale.status || 'completed',
31    currency: sale.currency || 'USD',
32    sale_date: sale.created_at
33      ? new Date(sale.created_at).toLocaleDateString()
34      : 'N/A'
35  };
36});
37
38return {
39  sales: saleRows,
40  summary: {
41    total_revenue: `$${totalRevenue.toFixed(2)}`,
42    total_sales: completedSales.length,
43    avg_order_value: completedSales.length > 0
44      ? `$${(totalRevenue / completedSales.length).toFixed(2)}`
45      : '$0',
46    refund_count: refundedSales.length,
47    refund_rate: sales.length > 0
48      ? `${((refundedSales.length / sales.length) * 100).toFixed(1)}%`
49      : '0%',
50    net_revenue: `$${(totalRevenue - refundedRevenue).toFixed(2)}`
51  }
52};

Create queries to manage Podia subscribers and customers. Create getSubscribers with Method GET and path /v1/subscribers (or /v1/customers depending on Podia's API). Add URL parameters: Key = page, Value = {{ pagination.pageNumber || 1 }}, Key = per_page, Value = 50. For search by email, create searchSubscriber with Method GET and path /v1/subscribers and URL parameter: Key = email, Value = {{ textInput_email.value }}. Podia subscriber records typically include: subscriber_id, email, name, created_at (join date), membership_status, total_spent, and product_enrollments. Create getSubscriberPurchases with Method GET and path /v1/subscribers/{{ table_subscribers.selectedRow.id }}/purchases (verify the exact endpoint with Podia's documentation). This provides the complete purchase history for a specific subscriber. Bind a Retool Table named table_subscribers to the subscriber query results. Add a search input that triggers searchSubscriber. When a subscriber is selected, trigger getSubscriberPurchases to populate a second Table showing that subscriber's complete purchase history. Add Stat components in the detail panel showing: subscriber lifetime value (sum of all purchases), membership status badge, number of products owned, and join date. For RapidDev-style comprehensive creator business dashboards combining Podia subscriber data with email engagement from Mailchimp or ConvertKit, Retool's multi-resource architecture lets you join platforms in the same app for a complete audience analytics view.

1// JavaScript transformer — format Podia subscribers with LTV calculation
2const subscribers = data?.subscribers || data?.customers || data?.data || [];
3
4return subscribers.map(sub => {
5  const totalSpent = parseFloat(sub.total_spent || sub.lifetime_value || 0);
6  const membershipStatus = sub.membership_status
7    || (sub.active_membership ? 'active' : 'none');
8
9  return {
10    id: sub.id,
11    name: sub.name || `${sub.first_name || ''} ${sub.last_name || ''}`.trim() || 'No Name',
12    email: sub.email || 'N/A',
13    membership_status: membershipStatus,
14    status_badge: membershipStatus === 'active' ? '✓ Active Member'
15      : membershipStatus === 'canceled' ? '✗ Canceled'
16      : membershipStatus === 'paused' ? '⏸ Paused'
17      : 'No Membership',
18    lifetime_value: totalSpent > 0 ? `$${totalSpent.toFixed(2)}` : '$0',
19    lifetime_value_num: totalSpent,
20    products_count: sub.products_count || sub.enrollments_count || 0,
21    joined: sub.created_at
22      ? new Date(sub.created_at).toLocaleDateString()
23      : 'N/A',
24    last_login: sub.last_login_at || sub.last_seen_at
25      ? new Date(sub.last_login_at || sub.last_seen_at).toLocaleDateString()
26      : 'Unknown',
27    segment: totalSpent >= 500 ? 'VIP'
28      : totalSpent >= 100 ? 'Regular'
29      : 'New'
30  };
31}).sort((a, b) => b.lifetime_value_num - a.lifetime_value_num);