Letterbook
All docs

Letterbook Docs

Connect Supabase

Query Supabase tables for customer context inside Letterbook.

Last updated June 25, 2026

What this guide covers#

Connect Supabase so Letterbook can reference customer, account, and usage data while drafting replies.

Supabase-backed products often keep account state, workspace membership, usage limits, and customer records in Postgres tables. Expose only the tables or views that are safe and useful for support.

Setup steps#

  1. Find the Supabase project Letterbook should reference.
  2. Create or choose a server-side credential for support access.
  3. Select the tables or views Letterbook can read.
  4. Map customer identifiers such as email, user ID, or account ID.
  5. Confirm how row-level security affects the integration.
  6. Test lookups with representative customers.
  7. Document the exposed fields in internal knowledge.

Configuration details#

  • Keep service credentials server-side and rotate them when ownership changes.
  • Prefer support-specific views over broad table access.
  • Exclude auth secrets, tokens, private logs, and data support does not need.
  • Confirm whether RLS applies to the access path you configure.

Support-friendly views usually include:

  • Customer email and user ID
  • Workspace or organization ID
  • Plan and entitlement state
  • Current feature flags
  • Recent sync or usage state
  • Billing customer ID if it links to Stripe, Paddle, or another provider

Testing checklist#

Test:

  • A normal active user
  • A user with multiple workspaces
  • A user whose email changed
  • A customer with no matching row
  • A table or view affected by RLS
  • Credential rotation and reconnection