> For the complete documentation index, see [llms.txt](https://docs.glbnxt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glbnxt.com/tutorials/guides/n8n/supabase-in-n8n.md).

# Using Supabase in n8n

### Introduction

Supabase is an open-source Postgres development platform that gives you a full backend — database, authentication, instant APIs, file storage, realtime subscriptions, and vector search — built on top of standard, unmodified Postgres. Rather than stitching together separate services for auth, storage, and data, Supabase exposes them all through one project, with every table automatically available as a REST and realtime API the moment you create it. Because it's just Postgres underneath, nothing about your data is proprietary or locked into a vendor-specific format: it's the same database and SQL you already know, with a managed layer of tooling on top.

Using Supabase within n8n workflows provides a seamless, zero-lock-in data backend that natively integrates standard PostgreSQL capabilities alongside realtime triggers and built-in vector storage. Through n8n’s native Postgres and Supabase nodes, automation workflows can directly execute complex SQL queries, automatically sync incoming webhooks or API payloads into relational tables, leverage Row Level Security for precise multi-tenant data access, and instantly run vector similarity searches for AI agent memory—all without needing custom middleware or extra storage tools.

***

### Steps

#### Step 1: Find your API keys

1. Open your Supabase dashboard and select your project.
2. In the bar next to the Supabase logo and your project name you will find `Connect`, click on it.
3. Select `Server Build APIs`.
4. Look on the page until you find "Set environment variables".
5. You will see `SUPABASE_URL=` and `SUPABASE_PUBLISHABLE_KEY=`
6. Copy the URL and the Key, you will need them both later in n8n.

#### Step 2: Add Supabase credentials in n8n

1. Open your n8n instance.
2. In the left sidebar, click **Credentials**.
3. Click **New Credential**.
4. Search for **`Supabase API`** and select it.
5. Paste in:
   * **Host** — `SUPABASE_URL` from Step 1.
   * **Service Role Secret** — `SUPABASE_PUBLISHABLE_KEY` from Step 1.
6. Click **Save**.

Your n8n instance can now connect to your Supabase project.

#### Step 3: Use Supabase inside a workflow

1. Create a new workflow, or open an existing one.
2. Click the **+** button to add a node, and search for **Supabase**.
3. Select the credential you just created in Step 3.
4. Choose an operation — for example **Get Rows**, **Insert Row**, or **Update Row** — and pick the table you want to work with.
5. Click **Execute Node** to test it. If it's set up correctly, you'll see your table's data appear directly inside n8n.

> 💡 **Tip:** Start with a simple **Get Rows** action on a test table first. It's the quickest way to confirm the connection works before building anything more complex.

> 💡 **Tip:** When your Supabase returns no output, check if RLS is enabled on the table you are trying to get rows from. Disabling RLS allows n8n to "see" the rows and return them as output. For more information on RLS, check [GLBNXT Docs: Understanding Row Level Security](https://docs.glbnxt.com/tutorials/guides/supabase/supabase-rls).

***

### What happens next?

With this connection in place, you can build workflows that read from and write to your Supabase tables automatically — for example, saving form submissions, updating records based on an incoming webhook, or feeding data into an AI workflow.

***

*Need help? Contact the GLBNXT support team or ask a GLBNXT agent to walk you through the steps.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.glbnxt.com/tutorials/guides/n8n/supabase-in-n8n.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.