# Supabase Node Dynamic Table Fail

**URL:** <https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278>\
**Category:** Questions\
**Tags:** supabase, bug:confirmed\
**Created:** [August 18, 2026, 8:56pm UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278 "2026-08-18T20:56:40Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chainmaster](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/chainmaster/32/186390_2.png) [@Chainmaster](https://community.n8n.io/u/Chainmaster)\
**Post date:** [August 18, 2026, 8:56pm UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278/1 "2026-08-18T20:56:40Z")

</div>

Supabase Node Dynamic Table/Field Dropdowns Fail With “No bridge acquired for this context. Call acquire() first.”

I’m running into an issue with the native Supabase node in n8n Cloud where the Supabase credential works and the node can successfully query data, but the dynamic table and field dropdowns fail to load.

The issue appears to be isolated to n8n’s dynamic parameter loading rather than Supabase connectivity, authentication, RLS, or table access.

Environment

- n8n Cloud

- Native `n8n-nodes-base.supabase` node

- Supabase hosted project

- Using a newly created Supabase server-side Secret Key

- Resource: Row

- Operation: Get Many

Problem

The Supabase credential tests successfully in n8n.

However, when creating a Supabase node, the `Table Name or ID` dropdown displays:

`Error fetching options from Supabase`

The UI also reports:

`There was a problem loading the parameter options from server: "[object Object]"`

The same issue occurs when n8n attempts to dynamically load field/column names.

What is important is that the actual Supabase node works when the table and field names are entered manually as expressions.

Tests Performed

1. Supabase credential test

The n8n Supabase credential test succeeds.

Result:

`Connection successful`

1. Manual table name

Instead of using the broken Table Name dropdown, I switched the field to Expression mode and entered a known table manually:

`{{ 'example_table' }}`

I then ran:

- Resource: Row

- Operation: Get Many

- Limit: 50

- No filters

Result:

The Supabase node successfully returned rows from the table.

1. Manual field name and filter

I then added a filter and manually supplied a known field name as an expression:

`{{ 'status' }}`

Condition:

`Equals`

Value:

`Test`

Result:

The Supabase node successfully returned matching rows.

This confirms that:

- Supabase authentication works

- n8n can reach Supabase

- The table is accessible

- The fields are accessible

- Filters work

- Data retrieval works

- The Supabase node itself can execute successfully

The failure appears to be specifically related to dynamic parameter loading.

1. Direct Supabase Data API test

I also tested the Supabase REST API directly using an n8n HTTP Request node.

Request:

`GET https://[PROJECT].supabase.co/rest/v1/`

Headers:

`apikey: [REDACTED SERVER-SIDE SECRET]`

`Authorization: Bearer [REDACTED SERVER-SIDE SECRET]`

The request succeeds and Supabase returns the OpenAPI schema, including table paths and definitions.

So Supabase appears to be successfully exposing the metadata required for table and column discovery.

Network Error From n8n

I opened Chrome DevTools and captured the request generated when a brand-new Supabase node attempts to load the Table Name dropdown.

The dynamic parameter options request returns:

`HTTP 500`

Response:

```auto
{
  "code": 0,
  "message": "No bridge acquired for this context. Call acquire() first.",
  "level": "warning",
  "tags": {},
  "timestamp": "[REDACTED]",
  "context": {},
  "functionality": "regular",
  "name": "NodeApiError",
  "node": {
    "parameters": {
      "useCustomSchema": false,
      "resource": "row",
      "operation": "getAll",
      "tableId": "",
      "returnAll": false,
      "limit": 50,
      "filterType": "manual",
      "matchType": "anyFilter",
      "filters": {}
    },
    "id": "[REDACTED]",
    "name": "Temp-Node",
    "type": "n8n-nodes-base.supabase",
    "typeVersion": 1,
    "position": [
      0,
      0
    ],
    "credentials": {
      "supabaseApi": {
        "name": "Supabase account"
      }
    }
  },
  "messages": [
    "No bridge acquired for this context. Call acquire() first."
  ],
  "httpCode": null
}

```

Expected Behavior

When a valid Supabase credential is selected, the `Table Name or ID` dropdown should populate with the available Supabase tables.

After selecting a table, the field dropdowns should populate with the available columns.

Actual Behavior

The dropdown displays:

`Error fetching options from Supabase`

The dynamic parameter request returns HTTP 500 with:

`No bridge acquired for this context. Call acquire() first.`

Workaround

The Supabase node works if the table and field IDs are entered manually using expressions.

For example:

Table:

`{{ 'example_table' }}`

Field:

`{{ 'status' }}`

The node then successfully queries and filters Supabase data.

Additional Notes

I originally suspected RLS or Supabase permissions, but the testing above appears to rule that out.

The same server-side Supabase key:

- passes the n8n credential test

- retrieves the Supabase OpenAPI schema

- successfully queries rows through the native Supabase node

- successfully applies filters through the native Supabase node

Only the dynamic table/field option loading fails.

This appears to be an internal n8n dynamic parameter/load-options issue rather than a Supabase API issue.

I can provide additional logs, sanitized screenshots, workflow JSON, n8n Cloud version information, or other diagnostics if helpful.

---

<div class="post-metadata">

**Author:** ![achamm](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/achamm/32/143734_2.png) [@achamm](https://community.n8n.io/u/achamm)\
**Post date:** [August 18, 2026, 9:07pm UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278/2 "2026-08-18T21:07:23Z")

</div>

@Chainmaster 1 questions, whats your version on?

---

<div class="post-metadata">

**Author:** ![Chainmaster](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/chainmaster/32/186390_2.png) [@Chainmaster](https://community.n8n.io/u/Chainmaster)\
**Post date:** [August 18, 2026, 9:30pm UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278/3 "2026-08-18T21:30:00Z")

</div>

We’re on n8n Cloud, version 1.123.69.

---

<div class="post-metadata">

**Author:** ![n8n](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/n8n/32/26906_2.png) [@n8n](https://community.n8n.io/u/n8n)\
**Post date:** [August 18, 2026, 9:30pm UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278/4 "2026-08-18T21:30:20Z")

</div>

Thanks for letting us know about this, We have created `CAT-4130` as the internal dev ticket to look into it.

---

<div class="post-metadata">

**Author:** ![achamm](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/achamm/32/143734_2.png) [@achamm](https://community.n8n.io/u/achamm)\
**Post date:** [August 18, 2026, 9:30pm UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278/5 "2026-08-18T21:30:51Z")

</div>

@Chainmaster Update your version to 2.0, this was fixed in 2.19.3!

---

<div class="post-metadata">

**Author:** ![Chainmaster](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/chainmaster/32/186390_2.png) [@Chainmaster](https://community.n8n.io/u/Chainmaster)\
**Post date:** [August 18, 2026, 9:33pm UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278/6 "2026-08-18T21:33:11Z")

</div>

Thanks for letting us know! We were avoiding migrating to 2.x because of the breaks, but sounds like we will need to go through the migration tool

---

<div class="post-metadata">

**Author:** ![achamm](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/achamm/32/143734_2.png) [@achamm](https://community.n8n.io/u/achamm)\
**Post date:** [August 18, 2026, 9:34pm UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278/7 "2026-08-18T21:34:37Z")

</div>

@Chainmaster n8n has a migration guide in your admin panel, on what will break so you can plan ahead!

Fee free to mark any of the replies as the solution, and have a good day!

---

<div class="post-metadata">

**Author:** ![Anshul\_Namdev](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/anshul_namdev/32/178229_2.png) [@Anshul\_Namdev](https://community.n8n.io/u/Anshul_Namdev)\
**Post date:** [August 19, 2026, 6:35am UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278/8 "2026-08-19T06:35:56Z")

</div>

Hi @Chainmaster Welcome!  
The patch for this landed on the 1.x line, so you can stay on 1.x rather than take the 2.x migration for it. n8n released 1.123.73 with the fix. In the Cloud dashboard go to Manage \> Workspace \> Updates & maintenance, pick 1.123.73 in the n8n version dropdown and select Change version, that triggers a one to two minute restart.  
See this:

> [@Airtable node resource locator fails with "No bridge acquired for this context" — Cloud 1.123.69](https://community.n8n.io/t/airtable-node-resource-locator-fails-with-no-bridge-acquired-for-this-context-cloud-1-123-69/306956/8):
>
> New version n8n@1.123.73 got released which includes the GitHub PR 36494.

> **[Update your version | Deploy | n8n Docs](https://docs.n8n.io/deploy/use-n8n-cloud/update-your-version)**
>
> How to update your n8n version on Cloud.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/36532_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [August 26, 2026, 6:36am UTC](https://community.n8n.io/t/supabase-node-dynamic-table-fail/308278/9 "2026-08-26T06:36:56Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.