Postgres as a Live Export destination

Postgres as a Live Export destination. Export any Live Export source into your own Postgres database. Connects to databases that require certificates, like Cloud SQL with "Require trusted client certificates." Add a server CA certificate, client certificate, and client private key on the connect form.

‍

Also this week

• Pick which tables a large connection uses. Once a base has more than 200 tables, a picker lets you search for and choose the ones your sync works with, so huge Notion workspaces and Postgres or Supabase databases stay quick to set up. Notion also finds a database from a pasted link. Open it from the create-sync flow, the mapping panel, or Settings → Connections. The public API and MCP server can read and set the picked tables too.
• Live Export knows the destination's field limit. Fields past the limit start unselected with a note explaining why, and the table's count turns red if you select too many.
• Live Export lists fields the destination didn't create. The create step and the save dialog name each skipped field and the reason, instead of counting it as created.
• Certificate fields are real text boxes. Postgres and MySQL certificate and key fields keep their line breaks and have a "Load from file" button for .pem, .crt, .cer, and .key files. They live in a collapsed Advanced section, and field descriptions moved into a hover card, so the IP address to allowlist is easy to copy.
• Connect with Stripe in Live Export. Sign in to Stripe with a button instead of pasting a secret key.
• Older plans get the connectors their tier includes today. Native Copper, Zoho, and Framer, among others, now work on legacy plans at the matching tier, with no upgrade prompt.
• Postgres and Supabase date columns export as dates. Live Export destinations get date-only fields for them.
• Inactive syncs get a final warning a day before deletion. A sync is never marked for deletion without it.
• Updating a Webflow item that has never been published, like a draft, saves the change as a staged update and leaves the item unpublished.
• Records with a broken half-character in their text, often left behind by truncated emoji, sync with a placeholder character in its place.
• A failed connection's error shows once, in the sign-in dialog, rather than also behind it.
• The public API's create-fields call answers a stale source column with a 400 and its "Refresh table and try again" message.