Schemas in Supabase node other than public (http custom settings ? )

Feature Requests
, ,
1

Describe the problem/error/question

Hello,
In the Supabase node, only the public schema is available.
See this post:

I’ve followed this

But it does not allow to change the schema, so I tried, but failed to customize the http node here

I’m not even sure of the config to set (tried import curl directly but didn’t get the url, at least, correctly.

Is there some advanced exemple of such configurations ? Would the Supabae API would allow the expected schemas in that case ?
Obviously a “select schema” box in the native Supabase node would be perfect, but I suppose I’ll have other problems with different services in the future so might be interesting to understand it a bit better…

Thanks for your support !

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
4

Hi @NiKoolass

Thanks for reporting this! Just had a play around and it indeed looks like we’re only fetching the public schemas.

Will raise an internal ticket and turn this into a feature request. Should be a low-hanging fruit to implement :slight_smile:

3 Likes