Hello,
I’m trying to filter data from supabase using the database element, I need to use 2 filters, eq and contains, they work well together as simple filters but once I use the filter combination OR to get the result I need, it stops working. Am I doing something wrong or is it a bug?
This is the set up I’m using:
Thanks for reaching out and for providing the setup screenshot.
At first glance, your configuration seems mostly correct.
However, it’s important to note that the OR logic for mixed filter types (like equal to and contains) can be limited depending on how the Supabase API parses the filter structure under the hood.
To help investigate this further, could you please confirm the following:
lider and usuarios in your Supabase table?usuarios field is a text array or a string with multiple user IDs?Also, as a workaround, you might consider splitting the request into two queries and combining the results in Bubble if the logic needs to span incompatible filter types under a single OR.
Let us know and we’ll be happy to look into it further!
Regards,
Support Team
Browse all Zeroqode Plugins for bubble
Just checking in to see if you had a chance to review my last message.
Let me know once you’ve had a moment to confirm the details - I’ll be happy to assist further!
Best regards,
Support Team
Browse all Zeroqode Plugins for bubble
Who at zeroqode is in charge of doing development on this plugin? Naas used to provide consulting support and I am in need of this from you guys so I can get this plugin to actually work. Realtime is so inconsistent for me that supabase is completely unusable in my production app which is extremely disappointing. Not blaming the plugin, just need support. Can I get a calendly link and an invoice?
Hi @arensbpa ,
Thanks for reaching out! 
We provide general support and address issues that can be reproduced on the plugin demo page. For any issues outside of that, we offer documentation and the demo editor page to guide you through setting things up.
If you need more tailored assistance, you can book a call with our PM team via our website for a paid consultancy service and custom integration support.
Feel free to reach out if you need more details! 
Best,
Support Team
Browse all Zeroqode Plugins for bubble
Thanks Mina I booked an appointment.
Anyone have suggestions on this bug? My users can’t store data from supabase in bubble within 10 seconds of the page loading even though the realtime event subscription is almost immediate and the data fetch is on page load.
UPDATE: issue is unrelated to time, it’s the first event on page load never works regardless of how much time elapses. This is one of the main issues i’ve been seeing with realtime - it says you’re subscribed to the channel but then it doesn’t work out of the gate you have to give it a kick in the ass to get it working
The inconsistencies with realtime for this plugin are insane. I don’t know how anyone uses this in a production environment.
Hey @arensbpa ,
Thanks for the video!
Looks like the JSON response is coming in later than when the create/modify thing action is triggered. This is likely causing the issue. The real-time event fires quickly, but the data fetch takes a bit longer to complete.
Instead of relying solely on the first real-time event, you could add a conditional workflow to handle this more reliably. Here’s what I recommend:
This should ensure the data is available and avoid relying solely on the first event.
Hope this helps.
Best,
Support Team
Browse all Zeroqode Plugins for bubble
@mina.rotari - I implemented the verify and save worfklow, however it didn’t solve the problem even though it should… I get a very interesting bug where the “only when” condition thinks there is text saved to the field when there is not. Please see this video and you can see for yourself: ClaimKit - 6 August 2025 | Loom
I showed bubble bug team this same exact video and they said “After reviewing your setup, it appears that the dynamic value you’re using user_condition(supabase)_id is being sourced from the Supabase plugin. Since this plugin is developed by a third party, our team has limited visibility into its internal functionality and how it processes data.”
Can you please let me know why you think this is occurring? The database fetch and the realtime subscription happen on page load as you can see in the console logs on the video
Hey @arensbpa,
Thanks for sharing the video!
It looks like the issue stems from the “Only When” condition. The debugger is showing that the ID exists in the field (because it’s being evaluated). This often happens because of timing issues , the real-time event fires before the data is fully available, causing a mismatch when the ID is checked.
Here’s how you can fix it:
Use the “Supabase Database Fetch” action to pull in the latest data, especially the ID. Make sure to filter by unique identifiers like user_id = Current User's ID.
After fetching, add a pause to give it time to fully load before the next action.
Instead of using the “Only When” condition in the modify action, schedule a custom event. In that event, check if:
user_condition(supabase)_id to the fetched Supabase ID.This approach checks if the ID is empty before setting the value, so it won’t try to set an ID until it’s correctly fetched. By using a custom event, we’re ensuring that the ID is only saved once the data is fully available, preventing the race condition where the data isn’t ready when the workflow runs.
Hope that helps.
Best,
Support Team
Browse all Zeroqode Plugins for bubble
Hi @mina.rotari Mina, thanks for the response 
I believe i’ve implemented this the way you suggested, here is a video demonstrating the race condition still occurring somehow ClaimKit - 7 August 2025 | Loom and here are images of the setup if you’d prefer to read:
Hi @arensbpa ,
Appreciate all the effort and the detailed info you’ve shared.
I took some time to create a test page on my side and was able to replicate the exact same output. Interestingly, the record in the DB is created with the creation date, but the actual text value is null.
I’ve gathered all the details and passed them on to our dev team for investigation. At this point, it could be related to Bubble’s async processing, but we’ll wait for the dev team’s update before making any conclusions.
I’ll make sure to keep you informed on any results we get.
Best,
Support Team
Browse all Zeroqode Plugins for bubble
While we wait on response from dev on that, can you @mina.rotari take a look at this for me? This is actually the main issue I have with the supabase plugin. What I seem to experience is even though the console shows that realtime channel is subscribed, when a realtime insert or update or event occurs, it shows up in my console but it doesn’t not actually trigger any of the realtime insert/update/event workflows that I have setup to refresh my UI. So I cannot trigger a refresh UI component event because it never fires. And so the end result is a realtime system that functions only periodically. Here’s a video illustrating this: Demonstration of Realtime Confusion | Loom
When I started using this plugin I didn’t expect to have to use those workflows to refresh the UI< I just expected the UI to refresh just like it does in bubble. So the fact that these aren’t working confounds me. I find the realtime in the plugin so unreliable that I cannot push anything to prod until I get this sorted, what am I doing wrong here? If you need more information on my setup please let me know
Hi @arensbpa,
Apologies for the delay and thanks a lot for walking through your setup in such detail — that’s super helpful.
Regarding the first issue: our dev team confirmed that everything works fine on their end. The key is to make sure you’re using the “DB Action Inserted” event, which confirms all incoming data before triggering anything else. We ran several tests, and the outcome was consistent every time. You can check out my test setup here:
For the second issue, I’ve recorded a short video showing how to verify if update it’s triggering or not.
I hope that helps, looking forward to your feedback.
Best,
Support Team
Browse all Zeroqode Plugins for bubble
Ok @mina.rotari thank you for these! I have implemented the “supabase database inserted” event instead of using the “realtime inserted” event and it works well thank you!
For the second topic we are discussing, I implemented the “supabase database updated” event and then a reset a group (instead of refresh page in my circumstance) like you suggested and I get weird behavior where only the removal of information triggers the workflow which is not the case in your demo video. Please see this video: tb1.mp4 - Google Drive - 12 August 2025 | Loom
Am I doing something wrong?
