⚠️ Issues Page (19)
We added an Issues Page that shows any errors impacting your sync, added support for Airtable Lookup fields, and fixed a lot of bugs.
⚠️ Issues Page
🆙 Lookup field support in Airtable
You can now use Airtable Lookup fields as part of a sync. Like Formula fields, Lookup fields can be mapped to a variety of different Webflow fields. See our Docs for a full list of supported fields.
🐌 Remove Slug requirement
In the past, we required you to map a Slug field in order to set up a sync. You can now skip the Slug field and Webflow will auto-generate one for you.
🐞 Bug Fixes
Fixed the Calendar link on the Contact Us page
The calendar link on our Contact Us page was broken. If you tried to sync two tables with multi-reference fields that referenced each other it wouldn’t work. Now it does.
Greater than 9 bases would overflow the footer
If you had more than 9 Whalesync bases, it would look strange on the frontend. Now you can have as many bases as you want.
Require primary key
Previously we would let you create a sync without mapping the primary key (often the Name field). This would guarantee a bad sync since Webflow requires a primary key. Now that’s not possible.
➡️ What’s Next
Starting with the Issues Page, we’re making a big push towards self-serve. We’ll always be available to jump in, but want to give everyone the tools to use Whalesync on their own if they prefer. This includes features like base editing, API key editing, and issue notifications. Additionally, we’ll enable 2-way sync soon, so changes in Webflow sync back to Airtable.