General notes on Bubble setup
The Auth element has to be visible to work. This is the only element which require to be not hidden at any point. As all the other elements rely on Authentication in one way or another.
For the Data element, when you specify the Table name in the element or in workflows, you only need to say "user" not "public.user" otherwise it'll throw an error.
Not necessary to save the Access Token/Refresh Token, the plugin will keep track of that and refresh it when necessary, basically all of that is automatically done for us by the Supabase SDK. Also the Access Token is only there for you if you need to use the API Connector for any call.
Filters for the Data element do not need to include dots, only the name of the column, and the value you're searching for. This only true for the table's columns, for foreign tables you need to use dots to target the columns
Table names and Column names are case-sensitive.
For the Realtime functionality you might need to enable some things in your Supabase Project. Please check their documentation and limitations.
If you'd like to do multiple steps in one Workflow during Loggin in or Signing up, please use the Events for that, as actions work asynchronously. So if you want to create a new enry in your "users" table use the event "User Signed Up", so that the Data action waits for any Auth action to run.
If you want to Insert into a table with the API connector use the Header: "Prefer - return=representation" to return the newly created entry with the response.
Last updated