Board of Innovation•2w ago

Supabase New node is broken

Hi! Trying to create a new flow and the Supabase Node seems wrongly configured. Is missing the API key input. And gives this error when testing it. Any ideas to fix it?

4 Replies

AI Support•2w ago

AI Support Bot Information

<@1044594863544487946> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human! Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers. Please note: Team members will review and answer the questions on best efforts basis.

AI Support•2w ago

AI Response

It seems that the issue with the Supabase Node is related to the configuration of input parameters, particularly the absence of the API key input. To resolve this, you should ensure that the input parameters for the Supabase node are correctly defined and include all necessary fields such as the API key. Here's a general approach to resolve this issue: 1. Check the Node Configuration: Verify the structure of the input configuration by ensuring that the API key field is included as an input parameter. It should be defined as a string type, marked as sensitive, and have a user-friendly title like "API Key". 2. Correct the JSON Schema: In case the input parameters are set using a JSON schema, ensure that the configuration correctly lists the apiKey as one of the required fields. Here's how such configurations typically look:

   {
     "type": "object",
     "properties": {
       "apiKey": {
         "title": "API Key",
         "description": "Your Supabase API Key.",
         "type": "string",
         "pattern": "",
         "buildship": {
           "index": 1,
           "sensitive": true
         }
       }
       // other parameters
     }
     // required fields if necessary
   }

   {
     "type": "object",
     "properties": {
       "apiKey": {
         "title": "API Key",
         "description": "Your Supabase API Key.",
         "type": "string",
         "pattern": "",
         "buildship": {
           "index": 1,
           "sensitive": true
         }
       }
       // other parameters
     }
     // required fields if necessary
   }

3. Documentation and Support: Reference BuildShip documentation to better understand how to structure these inputs or seek help from their support if you are unable to resolve the issue yourself. You can contact BuildShip support or participate in community forums for additional guidance【4:0†buildship-docs.json】. If these initial steps do not resolve your issues, consider submitting a support request through your BuildShip Dashboard【4:0†buildship-docs.json】.

BuildShip AI Support

Luis•2w ago

Hi @Board of Innovation, in v2 you can set the integration key once and it'll be used for every node in that group.

Board of InnovationOP•2w ago

Is alreeady integrated, but is not working -