> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/integrations/data-analytics-and-bi/supabase.md).

# Supabase

How to connect using the Supabase system integration

<div align="left"><figure><img src="https://391958821-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpokYqd27yrOUxIBhyvbF%2Fuploads%2FG07CVXwWkLgvwxQUfvzA%2Fsuperbase.png?alt=media&amp;token=e85767a8-c00d-49e7-9ae7-e327fda3b459" alt=""><figcaption></figcaption></figure></div>

## Overview

Couchdrop supports inserting data into Supabase through file actions and Automations. This allows data received from cloud storage, SFTP/FTP, APIs, inbound webhooks, and other Couchdrop workflows to be written into a Supabase table.

Supabase is configured in Couchdrop as a **system integration** rather than a virtual folder. Once connected, you can select Supabase as a file action inside an Automation and configure the table that Couchdrop will insert data into.

## How to connect Supabase to Couchdrop

{% hint style="warning" %}

#### Before you start

To connect Supabase to Couchdrop, you will need:

* A Supabase account and project
* A Supabase table that you want Couchdrop to insert data into
* Access to create or retrieve a Supabase API key
* A location or inbound method in Couchdrop that will provide the data you want to ingest
  {% endhint %}

{% stepper %}
{% step %}

### Generate a Supabase access key

In Supabase, open your project and navigate to **Settings > API Keys**.

Create or retrieve a **Secret key** for the Couchdrop integration. Secret keys use the `sb_secret_...` format and are intended for backend services and data pipelines.

Copy the key so you can enter it into the **Supabase Access Key** field in Couchdrop.

{% hint style="warning" %}
Supabase secret keys provide elevated access to your project and can bypass Row Level Security. Store the key securely and do not expose it publicly.
{% endhint %}

For more information, see the [Supabase API keys documentation](https://supabase.com/docs/guides/getting-started/api-keys).
{% endstep %}

{% step %}

### Create the Supabase system integration

Log in to Couchdrop and add a new **System Integration**.

Select **Supabase** from the list of available integrations.
{% endstep %}

{% step %}

### Configure the Supabase connection

Configure the following fields:

| Setting                 | Description                                                                                            |
| ----------------------- | ------------------------------------------------------------------------------------------------------ |
| **Integration name**    | A name used to identify the Supabase integration within Couchdrop.                                     |
| **Supabase URL**        | The URL for your Supabase project. The standard format is `https://<supabase_project_id>.supabase.co`. |
| **Supabase Access Key** | Enter the Supabase API key generated in the previous step.                                             |
| **Supabase Table**      | Enter the Supabase table that Couchdrop will insert data into.                                         |

Click **Add System Integration** and follow the wizard to complete the connection.
{% endstep %}

{% step %}

### Use Supabase in your Workflows

Create an Automation or file action and select **Supabase** as the platform type.

Select the Supabase connection you created and configure the file action for the data being inserted into your Supabase table.
{% endstep %}
{% endstepper %}


---

# 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.couchdrop.io/integrations/data-analytics-and-bi/supabase.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.