How to optimize speed when syncing new members to personalized Webflow dashboards using Make.com or Whalesync? Answered

• 

  Jordan Ryskamp

  • April 17, 2025 18:10

  Make could be faster in firing things off between all the parts, however, setting the the syncs takes a lot of time and it’s not bi-directional, meaning you have to have an event to trigger the update on both sides.

  I’ve used Memberstack, Airtable, and Webflow together using Whalesync on a project and we just had to recognize that there’d be a small delay of 15-20 seconds in getting member data synced from Airtable to Memberstack (most of that delay is caused by a 5-10 second hold in Whalesync to let people finish typing in fields, look up how Airtable autosaves data—every character is a autosaved so each one can be a triggering event).

  A few ways we solved for this:

  • Store whatever we need in Memberstack on account creation.
  • Personalized member dashboards had pages with a strict url structure so, even if it wasn’t created yet, we would have the url ready.
  • Introduce small strategic delays to ensure everything had time to propagate (like giving a 30-45 second delay between account creation and sending the email to let all the syncs fire).

  Make might be faster but it’s much harder to keep things in sync because you need all the events dialed in. Whalesync is easier on the set-up and, if you know the limitations, you’ll be fine.

  0
• 

  Hashem Selim

  • April 17, 2025 18:11

  Awesome suggestions. Implementing some strategic delays sounds like a good path forward. Maybe a generic welcome screen with some membership guidance. or forcing an email verification step. Thanks for taking the time, Jordan.

  0

Please sign in to leave a comment.