# Understanding Supabase Realtime Workflows

**URL:** <https://community.weweb.io/t/understanding-supabase-realtime-workflows/20564>\
**Category:** How do I?\
**Created:** [December 24, 2025, 5:19pm UTC](https://community.weweb.io/t/understanding-supabase-realtime-workflows/20564 "2025-12-24T17:19:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cheese\_pancake](https://avatars.discourse-cdn.com/v4/letter/c/3d9bf3/32.png) [@cheese\_pancake](https://community.weweb.io/u/cheese_pancake)\
**Post date:** [December 24, 2025, 5:19pm UTC](https://community.weweb.io/t/understanding-supabase-realtime-workflows/20564/1 "2025-12-24T17:19:03Z")

</div>

Hi everyone,

I’m a non-technical builder working with WeWeb and Supabase. Currently I’m a bit confused about how to properly implement **Supabase Realtime** within WeWeb. I have Realtime enabled on both ends and no RLS policies are currently blocking the traffic.

1. Do I actually need to “Subscribe” via a Workflow?\*\* I’ve noticed that sometimes I see data changes instantly without even setting up a “Subscribe” workflow. However, this seems very inconsistent.

My confusion - Is there a default sync happening? I want to know if a manual “Subscribe to Channel” workflow is the only way to ensure 100% consistent real-time updates.

1. Is Fetch Collection on DB Change the right way? Right now, my workflow is: On Realtime Database Change → Fetch Collection. This feels like it’s just doing a full refresh every time a single row changes. Is there a more optimal way to update just the changed row in the WeWeb variable without re-fetching the entire collection? But still it’s inconsistent , sometimes i don’t see instant updates , why is that?

 ![Screenshot 2025-12-24 at 10.30.33 pm](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/6/67d168904eba3f986e99fc980d7b31396ba6c1e0.png)

1. Additionally I tried to implement realtime presence so my admins can work together without overwriting each other, but it’s been a nightmare to get stable.

Appreciate any guidance!

---

<div class="post-metadata">

**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\
**Post date:** [December 29, 2025, 3:01pm UTC](https://community.weweb.io/t/understanding-supabase-realtime-workflows/20564/2 "2025-12-29T15:01:25Z")

</div>

Hey there 👋,

**Yes, you do need a “Subscribe to channel” workflow for reliable realtime in the live app.** ​

What you’re seeing “sometimes” without a Subscribe workflow is usually:

- The editor preview doing its own refresh (not true realtime in the browser).​
- Or a normal collection fetch happening right after the change, making it look instant.​

For production, always use:

1. **Enable Realtime** on the table in Supabase (Replication / Realtime).​
2. **Enable Realtime** on that table in the WeWeb Supabase data source.​
3. **Subscribe** to the channel in a page or app workflow (on page load).​
4. **On Realtime Database Change** → then do `Fetch Collection` (or update a variable).​

If updates are still inconsistent:

- Double-check that the channel name matches exactly in “Subscribe” and “On Realtime Database Change”.​
- Make sure the user is authenticated (if the channel is private).​
- Avoid using Realtime on collections in “advanced mode” (joins) — it can behave unpredictably.​

Docs:

- [Intro to Supabase Realtime](https://docs.weweb.io/websockets/supabase-realtime/intro-to-supabase-realtime.html)​
- [React to realtime database changes](https://docs.weweb.io/websockets/supabase-realtime/database-changes.html)