Context:
I previously had a reliable realtime setup using the legacy Supabase plugin with an app-level trigger listening for realtime events and updating a variable list that rendered in the UI. Use case is a simple AI chat pattern across a conversations table and a messages table.
I’m trying to figure out the best approach in the new Data & API backend architecture, and the docs haven’t quite caught up yet (totally understand, things are moving fast). Before I go too deep, I wanted to check with the community on a few things:
**1. Are you running the legacy Supabase plugin and the new Supabase integration side by side?
**
To preserve legacy workflows while adopting the new features. If that’s not feasible on the current billing plan, would the fallback be going back to Table Views with the advanced frontend display? A lot of the help materials feel like they’re pushing a choice between plugin or integration so curious what others are doing here when core workflows depend on the old setup.
2. If you’re on the new integration, how are you handling realtime?
Are people using a backend API call to Supabase and piping the result back into the interface via variables, polling on an interval, or something else?
3. Is there a realtime listener node in the new integration/update I’m missing?
or is this realtime doc still the current path and Im just missing something on my end? maybe its labeled differently or is a new action node like table fetch that we are recently getting a custom to…
Appreciate any feelers from folks who’ve already worked through this or have some ideas thanks!
