LogoLogo
WelcomeGet Started
  • What is Whalesync?
  • Start Here
    • Quick start
    • Video tutorials
  • Popular Syncs
    • Webflow + Airtable
    • HubSpot + Notion
    • Supabase + Airtable
    • Notion + Google Sheets
  • Connectors
    • Affinity
      • Authorize Affinity
      • Full records vs. shallow records
      • List-specific fields
      • Notes in Affinity
    • Airtable
      • Airtable view sync
      • Airtable API quota
    • Attio
    • Google Sheets
      • Formatting columns
      • Foreign keys
      • Multi-select fields
      • Avoid sort range
      • Whalesync ID column
    • HubSpot
      • Associations
      • Webhooks
      • Merging records
    • Memberstack
      • Authorize Memberstack
      • Memberstack custom fields
    • Notion
      • Notion page sync
    • Postgres
      • Authorize Postgres
        • AWS (RDS)
        • Basedash
        • DigitalOcean
        • Heroku
        • Neon
        • Render
        • Supabase
      • SQL scripts
      • Primary key snippets
      • Foreign key snippets
      • Terminology
      • Multiple foreign keys in a single field
      • How to sync Postgres views
    • Salesforce
    • Stripe
      • Authorize Stripe
    • Supabase
      • Adding default values to primary keys
      • How to sync Airtable linked records with Supabase foreign keys
      • Why does Whalesync create a database user?
      • Why do I need an ID column?
      • SQL scripts
      • Primary key snippets
      • Foreign key snippets
      • Terminology
      • Multiple foreign keys in a single field
      • How to sync Postgres views
    • Webflow
      • Supported fields - (AT x WF)
      • Webflow Memberships sync
      • Webflow status field
  • Previous connectors
    • Bubble
      • Authorize Bubble
    • Close
    • Copper
    • MS Dynamics CRM
    • Outreach
    • Pipedrive
      • Pipelines
    • Shopify
      • Authorize Shopify
      • Syncing images
      • Syncing variants
      • Tutorial videos
      • Theme Template field
    • WordPress.com
    • WordPress.org
      • Quick Start Guide: WordPress.org
      • Authorize WordPress.org
      • Advanced Custom Fields (ACF)
      • How to sync images
      • Supporting tables
      • Tutorial
      • WordPress status field
    • Zoho CRM
  • Features
    • Two-way sync
    • Issues
    • Operations
    • Record matching
    • Filters
    • Auto-create tables
    • Additional features
      • Automapping
      • Creating users via Whalesync
      • Delete protection
      • File hosting
      • HTML and Markdown field extensions
      • Relation fields
      • Sync preview
  • Resources
    • Support
      • Sync behavior questions
      • Common errors - Airtable
      • Common errors - Notion
      • Common errors - Postgres
      • Common errors - Webflow
      • FAQ
      • Field compatibility
      • How to get record IDs
      • How to change your sign-in
      • How to change your email
      • How to add additional email addresses
      • How to update your tax ID number
      • How to create a slug field in Airtable
      • Known issues
      • Multi-select to multi-reference
      • Transfer Webflow site to another account
      • Troubleshooting attachment fields
      • Webflow deprecating v1 APIs
    • Template Packs
  • YouTube
  • Security
  • Changelog
Powered by GitBook
On this page
  • Setup Tips
  • Supported Schemas
  • Supported Fields
  • Things to Keep in Mind
  • During Setup
  • Handy Tips

Was this helpful?

  1. Connectors

Supabase

PreviousAuthorize StripeNextAdding default values to primary keys

Last updated 1 month ago

Was this helpful?

Setup Tips

All synced Supabase tables must have a primary key We use the primary key to keep your data in sync.

Primary keys must be auto-generated (i.e. have a default value) To ensure data consistency, we require primary keys have default values. See .

Supported Schemas

In general, Whalesync supports syncing custom Supabase tables. We want to prevent interfering with internal Supabase data, so we don't support syncing Postgres schemas that Supabase uses for its own internal purposes.

Schema
Status

public

✅ Supported

Any other non-Supabase provided schema

✅ Supported

auth

✖️ Not Supported

extensions

✖️ Not Supported

graphql

✖️ Not Supported

graphql_public

✖️ Not Supported

pgbouncer

✖️ Not Supported

pgsodium

✖️ Not Supported

pgsodium_masks

✖️ Not Supported

realtime

✖️ Not Supported

storage

✖️ Not Supported

vault

✖️ Not Supported

Supported Fields

Field
Status

🏷️ Array

✅ Supported

#️⃣ Bigint

✅ Supported

📝 Bit

✅ Supported

☑️ Boolean

✅ Supported

📝 Composite

➡️ Supported (1-Way)

📅 Date

✅ Supported

📅 Daterange

➡️ Supported (1-Way)

🔗 Domain

➡️ Supported (1-Way)

🔘 Enum

✅ Supported

🖇️ Foreign Key

✅ Supported

#️⃣ Geometric

➡️ Supported (1-Way)

#️⃣ Integer

✅ Supported

#️⃣ Interval

➡️ Supported (1-Way)

🗃️Json

✅ Supported

💱 Money

✅ Supported

📝 Network

✅ Supported

#️⃣ Numeric

✅ Supported

⏱️ Range

➡️ Supported (1-Way)

📝 Text

✅ Supported

📝 Textsearch

➡️ Supported (1-Way)

⏱️ Time

➡️ Supported (1-Way)

⏱️ Timestamp

✅ Supported

🆔 Uuid

✅ Supported

🗃️ XML

✅ Supported

🔦 Binary

✖️ Not Yet

Things to Keep in Mind

During Setup

Renaming schema, tables, or columns will break Whalesync mappings If you rename a table/column, you'll need to remap the impacted table/column in Whalesync.

Handy Tips

We support foreign keys (including two-way sync)! In order to sync a foreign key field, you'll need to also sync the table the field references.

Adding ".html" or "_html" to the end of a column name will preserve HTML For example, "text_html", will preserve that column's values as HTML while syncing.

Note that Whalesync does not yet support:

  • Whitelisted IP addresses

  • Custom SSL/TLS certificates

Adding default values to primary keys
Page cover image