Hi @alexandregalvaogarcia ,
Thanks for reaching out!
It looks like you’re following the steps correctly, but we understand that you’re running into an issue with the signed URL not being generated in the repeating group. We’re actively working on improving the plugin to meet our standards. As it was recently acquired, we’re still refining its functionality, and we’re addressing issues like this one as part of the ongoing improvements.
A couple of things to check in the meantime:
- Data Source Setup: Ensure the data source for the repeating group is correctly pulling the file information from Supabase. If the source is incorrect or missing data, it might not trigger the signed URL generation.
- Supabase Permissions: Double-check that the permissions for the files in Supabase are set to allow access and URL signing, as restricted access can sometimes prevent the signed URL from being created.
We’re working on updating the demo page and improving the documentation, and your feedback is incredibly helpful as we continue to refine the plugin. We really appreciate your patience, and we’ll make sure to update everything soon.
Let us know if you have any further questions!
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
1 Like
Hi @ZeroqodeSupport
Have just implemented the JWT generation through CustomAuth and have encountered that due the authentication is taking place through CustomAuth, mainly all the functionalities and states offered through Auth node do not exist.
For example would be looking to
- Send password reset request
- Change credentials (email)
- Custom claim of authenticated user Email (not the one set in JWT token but the actual in DB)
Some actions can be done through service account in the back-end but these are hitting Supabase as through Path: “/admin/Generate_Link” instead of “/Magiclink” which makes it not to trigger automated recovery emails in Supabase backend. Also could not get the normal Auth node to work simultaneously with Custom Auth on the page (I have SPA set-up)
Note also that there is server error for deprecation notice in the logs: “GOTRUE_JWT_ADMIN_GROUP_NAME not supported by Supabase’s GoTrue, will be removed soon”
Any plans to enhance Custom Auth node offering more Auth node functionalities as this would really make working with the plugin more versatile, while offering JWT for RLS security?
Hi @pulkkinen.juho ,
Thanks for reaching out with your detailed feedback. 
Just to update you, the Supabase plugin was recently acquired by Zeroqode, and we’re currently in the process of reviewing and improving its functionality. We’re also working on creating updated documentation and demo examples to help users better understand and utilize the plugin. Rest assured, I’ll be sure to pass along your feedback to our development team, and we’ll consider adding more features to the CustomAuth node to enhance its versatility.
Regarding your specific use cases:
- Password Reset Request / Change Credentials: Since you’re using CustomAuth, these actions may not be available directly through the Auth node, as it’s bypassing Supabase’s built-in Auth system. You can try leveraging Supabase’s API endpoints directly (for example, the /admin/Generate_Link and /Magiclink endpoints) for actions like password reset or changing credentials, although I understand this may not trigger automated recovery emails as expected.
- Custom Claims for User Email: You can manage custom claims in JWT tokens, but as you’ve pointed out, retrieving the actual email from the database may require a direct query to Supabase via its API. If you’re dealing with RLS and need more control over your JWT, it’s likely going to require custom logic on the backend to sync the data.
- Auth Node and CustomAuth Compatibility: Since your app is an SPA, it might be tricky to use both Auth and CustomAuth nodes on the same page, especially when they rely on different authentication flows. A possible workaround could be to handle the authentication logic separately on different pages or even combine the backend and frontend logic to synchronize user states more efficiently.
As for the deprecation notice you received about GOTRUE_JWT_ADMIN_GROUP_NAME, it’s important to keep an eye on that. Supabase’s GoTrue service is evolving, and we’ll stay updated on any breaking changes related to that.
We’re actively working on improving the overall experience with the Supabase plugin, so thank you for your patience and for bringing these points to our attention!
Looking forward to your reply.
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi- I just purchased the plug-in. I’m a little bit confused on what "initialize a new datatype in the API connector " means.
Do I need to set up API calls first? I checked the demo app, it seems the API Connect is just empty field.
@ZeroqodeSupport
Hey @steven.h.liu.1 ,
Thanks for reaching out!
You’re right to notice the API Connector fields might seem empty at first glance. The phrase “initialize a new datatype in the API Connector” refers to setting up API calls that allow Bubble to communicate with your Supabase backend — particularly when working with custom queries, authentication, or database actions that go beyond the plugin’s pre-built functions.
To answer your question:
Yes, you’ll need to configure API calls in the API Connector if you plan to use custom endpoints or call Supabase REST features that aren’t already built into the plugin actions.
However, if you’re using the plugin’s built-in actions and data calls, many common functions (like login, signup, fetching tables, etc.) are already set up for you. You won’t need to use the API Connector unless you’re extending the functionality.
Here’s the link to the full guide, including setup instructions and examples:
Supabase Pro Kit Plugin Docs
It explains where and when to use the API Connector depending on your use case, along with step-by-step examples.
Looking forward to your reply. 
Best,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi @steven.h.liu.1 
Just checking in to see if the explanation and guide about using the API Connector with Supabase Pro Kit helped clarify things for you.
Have you had a chance to try setting up any custom API calls or tested the built-in plugin actions? If you have any questions or need further clarification, feel free to reach out — we’re here to help!
Looking forward to your update 
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi- I haven’t had a chance to push it through yet. Let me try it and circle back.
