Hello Bubble Support Team,
I’m encountering an issue with Bubble’s API Connector and Workflow editor that’s preventing me from proceeding with my app development. I’ve spent significant time troubleshooting, but the problem persists, and I’d greatly appreciate your assistance in resolving it.
Issue Description: I’m integrating Supabase authentication into my Bubble app. I’ve set up a “Supabase SignUp” API call in the API Connector to sign up users via Supabase’s /auth/v1/signup endpoint. The API call is configured correctly (as far as I can tell), but when I add the “Supabase API - Supabase SignUp” action to my workflow, the parameters (email, password, user_type) do not appear for configuration. Instead, I only see the “Only when” condition option, which prevents me from setting the values dynamically (e.g., Input_Email’s value for email).
App Context:
- App Name: MyApp
- Page: signup
- Workflow Event: “Button_Sign Up is clicked”
- API Call Name: “Supabase SignUp”
- Purpose: To sign up a user in Supabase, store the access_token and userId, create a profile in a profiles table, and redirect to a dashboard page.
API Call Configuration in API Connector:
- Name: Supabase SignUp
- Use as: Action
- Method: POST
- URL: https://xxxxxxxxx.supabase.co/auth/v1/signup
- Headers:
- apikey: [My Supabase Anon Key]
- Content-Type: application/json
- Body (JSON):
json
CollapseWrapCopy
{ "email": "<email>", "password": "<password>", "user_metadata": {"user_type": "<user_type>"} }
- Parameters:
- email: Private box checked
- password: Private box checked
- user_type: Private box checked
Initialization:
- I’ve initialized the API call multiple times using temporary values:
- email: testuser29@gmail.com
- password: Test123!
- user_type: “General”
- The initialization succeeds with a 200 OK response from Supabase, returning a JSON body like:
json
CollapseWrapCopy
{ "id": "user-id", "email": "testuser29@gmail.com", "user_metadata": {"user_type": "General"}, "access_token": "jwt-token", "refresh_token": "refresh-token", "expires_in": 3600 }
- After initialization, I revert the values back to placeholders (, , <user_type>).
Expected Behavior: When I add the “Supabase API - Supabase SignUp” action to my workflow, I expect to see the parameters email, password, and user_type so I can configure them (e.g., set email to Input_Email’s value).
Actual Behavior: No parameters are visible in the Workflow editor. I only see the “Only when” condition option, which prevents me from configuring the API call.
Steps I’ve Taken to Troubleshoot:
- Verified API Call Setup:
- Ensured the JSON body has placeholders (, , <user_type>).
- Confirmed the Private box is checked for all parameters.
- Double-checked the URL, headers, and apikey.
- Reinitialized the API Call:
- Initialized multiple times with different test emails (e.g., testuser24@gmail.com, testuser29@gmail.com).
- The call initializes successfully, and Bubble detects the response structure (e.g., id: text, access_token: text).
- Deleted and Recreated the API Call:
- Deleted the “Supabase SignUp” call and recreated it from scratch with the same configuration.
- Reinitialized after recreating.
- Refreshed the Bubble Editor:
- Saved my work, closed the editor, and reopened it to clear any caching issues.
- Tested with a Simpler API Call:
- Created a test API call with a simpler body (without user_metadata), but the parameters still didn’t show.
- Checked for Syntax Errors:
- Ensured the JSON body has no syntax issues (e.g., missing quotes, extra spaces).
- Confirmed API Response:
- Tested the endpoint manually using Postman to confirm Supabase returns the expected response (it does).
Impact: This issue is blocking my ability to implement user authentication in my app. I’m unable to configure the signup API call in the workflow, which prevents me from signing up users, creating profiles, and proceeding with other features like enforcing valuation limits.
Request: Could you please help me identify why the parameters aren’t showing in the Workflow editor and provide a solution? I’ve spent a lot of time troubleshooting, and I’m concerned there might be a bug in Bubble’s API Connector or Workflow editor. Any assistance or workaround would be greatly appreciated so I can move forward with my app development.
Thank you for your help!