How to connect Supabase to n8n - automate database workflows

If you're building modern automation applications or systems, chances are you've heard of Supabase – an open-source backend platform often referred to as the "Firebase alternative," featuring a PostgreSQL database, authentication, storage, and real-time subscription. Combined with n8n, you can build automated pipelines for reading, writing, updating, and deleting data within Supabase without writing a single line of code for the connection.

Since the launch of n8n 2.0 in late 2025, the Supabase node has been significantly upgraded: in addition to basic CRUD operations, it can also be used as an AI tool – meaning the AI ​​Agent node can automatically call Supabase to query data when needed, without requiring manual configuration. This is a significant change compared to the previous version.

Step-by-step guide: Integrating Supabase into the n8n workflow

Step 1: Add the Supabase node to the workflow.

Open the workflow in n8n, press the "Add" button (1) to add a new node. In the right-hand panel, select "Action in an App" to filter nodes connecting to external applications. Type "Supabase" (2) into the search bar and select the Supabase node from the results list.

Supabase node in n8n fully supports CRUD operations:

1. Create a Row: Create a new record in the table
2. Get a Row / Get Many Rows: Read one or more records based on a given condition.
3. Update a Row: Update a record by ID or condition
4. Delete a Row: Delete a record based on conditions

Choose the action that best suits your workflow needs. I'll give you an example with "Get a row" .

Step 2: Configure Credentials

Click on "Credentials" → "Create New Credential" . You need to provide two pieces of information from Supabase:

1. Supabase URL: Your project address, in the formathttps://[project-ref].supabase.co
2. API Key: Get from Supabase Dashboard → Project Settings → API Keys > Secret Key

Important security note: Supabase has two types of keys - anon keypublic and private service_role key. The service_role key bypasses all Row Level Security (RLS), allowing read and write access to all data. In a production environment, create a dedicated Supabase user with restricted permissions instead of using the service_role key to protect sensitive data.

Step 3: Obtain Supabase ID and API Key

Go to Supabase.com, create and log in to an account, and in the Dashboard section, select Create Project. Click New Project and create a project with your information.

After creating the Project > go to the Project Overview section as shown below, you will see the URL connecting to the Supabase node on n8n. Select Copy (1) > select Project URL (2) and paste it into the Host section in Supabase Account above.

Next is the Service Role Secret . Go to Project Settings (1) > API Keys (2) and copy the API Key from the Secret Keys section below. Paste it into the Service Role Secret section in Supabase Account above and select Save at the bottom. You have now completed connecting Supabase with n8n.

For testing purposes, TipsMake has created a table in the Table Editor. Select Insert and choose to add a row or column; here, I will experiment with Insert Row and name the table "Ban1".

After setting up your Supabase Account in Credential, select the options you created in Supabase. Make sure to choose the correct Table Name or ID you created.

By default, Supabase node only accesses the public schema . If your database uses a custom schema, enable the "Custom Scheme" toggle and enter the corresponding schema name.

1. Table Name: The name of the table to be manipulated
2. Condition/Filter: Filtering condition (e.g., id = 123or status = active)
3. Fields: Fields that need to be read or written
4. Value: The value to be updated or created.

You can use dynamic expressions to get data from the node beforehand: {{ $json.user_id }}or {{ $json.email }}.

Step 4: Execution and testing

Click "Execute Step" to run the test with real data. If you see something like the image below, you've succeeded. The output panel will display the response from Supabase, allowing you to confirm the operation was successful before connecting to the next nodes.

Supabase Vector Store - a new feature for AI workflows

In addition to the basic Supabase node, n8n also has a separate Supabase Vector Store node , specifically designed for AI workflows that need to store and query embeddings (vectors). You can:

1. Insert documents into vector database
2. Retrieve documents to add to the chain or agent.
3. Connect directly to the AI ​​Agent node as a tool.

The most common pattern: AI Agent → (via tools connector) → Supabase Vector Store → query relevant data → return context to LLM. This is the foundation of the RAG (Retrieval-Augmented Generation) workflow, allowing the AI ​​to respond based on your real data rather than just training knowledge.

Advantages and disadvantages

Advantage

1. Full CRUD integration with no coding required: The five main operations (Create, Read, Update, Delete, and Get Many) are all available in the interface, eliminating the need for manual API calls.
2. Excellent integration with AI Agents: Starting with n8n 2.0, Supabase nodes can function as AI tools – AI independently decides when to query the database, significantly reducing the number of nodes required in the workflow.
3. Cross-platform data synchronization is easy: You can pull data from Typeform, HubSpot, Google Sheets , or any other application and push it into Supabase in the same workflow, thanks to its connectivity with over 400 applications.

Disadvantages

1. Public schema access is limited by default: Custom Scheme must be manually enabled if using a different schema – this can be confusing for beginners.
2. Real-time subscription is not supported: the n8n Supabase node only runs when the workflow is triggered and cannot listen for real-time changes from Supabase. If you need to handle real-time events, you must set up a separate Supabase Webhook to trigger n8n.
3. Limitations with complex queries: Complex SQL queries (JOIN, aggregate, subquery) cannot be executed directly through the Supabase node. An HTTP Request node calling the Supabase REST API or a Postgres node connecting directly to the database is required.

Conclude

Integrating Supabase with n8n is one of the fastest ways to build a powerful automation backend without writing code. With updates in n8n 2.x, especially the ability to use Supabase as an AI tool, this pairing is becoming increasingly suitable for AI-driven projects that need to store and query structured data.