Review Paddle Billing vs Postgres Cache Consistency (n8n)

Compare Paddle Billing vs Postgres cache consistency—generate a private HTML mismatch report in n8n

This read-only n8n workflow reviews subscription state by cross-checking Paddle Billing against a Postgres subscription cache. It takes two observations about 10 seconds apart, then produces a downloadable private HTML report that highlights only stable discrepancies in status, plan, and access decisions.

What this workflow does

• Loads review configuration when started manually, including demo/live mode, Paddle environment, a settle window, price-to-plan mapping, and access policy rules.
• In demo mode, runs with fictional Paddle and Postgres observations captured about 15 seconds apart—useful for validating configuration logic.
• In live mode, first validates configuration, then:
  • Fetches up to 200 subscriptions from the Paddle API.
  • Fetches up to 200 rows from Postgres to capture the first observation.
• Waits 10 seconds, then repeats both reads to capture the second observation.
• Compares Paddle vs Postgres using your configured mappings, deferring records updated too recently (or with overdue scheduled changes) and keeping only mismatches that appear identically in both observations.
• Renders results into an HTML report and outputs it as a downloadable file.

Use cases

• SaaS ops teams verifying that Paddle Billing subscription changes correctly propagate to a Postgres cache.
• Automation engineers diagnosing when status/plan/access decisions drift between billing and cached entitlement data.
• Post-deploy checks to confirm stable consistency before tightening access rules.

Technical details

• Paddle API: add an HTTP Header Auth credential with Authorization: Bearer <token> and ensure it can read subscriptions.
• Postgres: use credentials with SELECT-only access to the subscription cache.
• n8n nodes/logic: if, code, no op, wait, postgres, sticky note.