Supported Fields

🖇️ Composite types
✅ Supported
🧑 Created by
➡️ Supported (1-Way)
🕠 Created date
➡️ Supported (1-Way)
📅 Date
✅ Supported
📅 Date interval
✖️ Not Yet
📅 Date range
✖️ Not Yet
📍Geographic address
✖️ Not Yet
📂 Image/file
✅ Supported
🕠 Modified date
➡️ Supported (1-Way)
#️⃣ Number
✅ Supported
#️⃣ Number interval
✖️ Not Yet
📝 Slug
➡️ Supported (1-Way)
📝 Text
✅ Supported
🫂 User
✅ Supported
☑️ Yes/no
✅ Supported

Things to Keep in Mind

Must enable data API Bubble requires the Data API to be enabled for syncing to work. Follow the instructions below to enable it.
  1. 1.
    Go to Settings > API
  2. 2.
    Check the box for "Enable Data API"
  3. 3.
    Check the box for all tables you plan to sync
Renaming schema, tables, or columns will break Whalesync mappings If you rename a table or column, you'll need to remap the impacted table/column in Whalesync. Note - remapping an impacted table will lead to duplicates unless you reset your data as well.
The email field for User "things" has a record sync delay if syncing with Airtable Bubble has a special data table called User that they treat differently than other tables. Specifically, you need to send it a valid email address. When syncing Bubble with Airtable, this can cause problems since Airtable saves every keystroke. To avoid this issue, Whalesync defaults to a 30-second record sync delay. See record sync delay for more details.

Bubble x Airtable

Use Airtable as a database for your Bubble app without running into API limits/performance issues (as is common with the Airtable plugin).

Bubble x Postgres

Make your Bubble app scale forever by syncing your Bubble data to a Postgres database.