I’m trying to move from Xano to Supabase with WeWeb. One of the things I’m missing is possibility to pass parameters to Supabase collection as I can do with Xano or REST API (or I can’t find the way to add it). Right now I have to create the variable bind it to the filter in Supabase plugin, change its value and refresh the Supabase collection and reset its value. This is not a very convenient way of doing things and make actions longer… I thing that possibility of passing parameters directly to the plugin will make life much easier.
The other thing is about Real Time Tabes. After enabling Realtime Table and set up sorting in Supabase Plugin, added rows (records) don’t reflect sorting - they appear on the very end of the collection. In order to sort it properly you have to Fetch the collection (which cannot be done automatically due to lack of appropriate No-Code actions) or apply sorting on the front end which is problematic when using paginated data. This complicates the logic unnecessarily and forces to use client side sorting which is not always a good idea.
Now in Action flow we can only SELECT the whole Supabase collection. Allowing to pass the parameter from the Action Flow (As we can in REST API or Xano with Headers) would greatly simplify the application and eliminate the need of using variables to achieve this.
You can bind the filters directly to a variable in the collection setup (your second screenshot) and then after changing the variable (meaning you change parameters of your query) you will refetch the collection. This way you apply the new parameters
