Skip to content
ClickRuntime

Connect Google Drive to Supabase

Drive is where documents are kept, and Supabase is where an app can search and use them. Index a folder for search, answer questions from your documents, and keep records in your database matched to the files they describe.
Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Ideas

What you can do with Google Drive and Supabase

Document indexing, search and backups between Google Drive and your Supabase project. These are ready-made starting points. Anything else you can describe works too.
Every 15 minutes

Keep a Drive folder searchable in your Supabase vector table

New and updated documents in your Drive Knowledge folder are split into chunks, embedded and kept in step in your Supabase documents table, so your app always searches current content.

See how it works
The moment it happensAI

Draft answers to support questions from your own documents

Each question from your support form comes back to you as a drafted answer with links to the documents it used.

See how it works
The moment it happensAI

Turn a website address into a company profile in Supabase and Drive

Submit a company's website and get its mission, services, contacts and keywords saved as a row in Supabase and a profile doc in Drive.

See how it works
On a schedule

Back up your Supabase storage files to Google Drive every night

Every night new and changed files in your Supabase storage bucket are copied to a Drive folder, and you get an email summary.

See how it works
Every 30 minutesAI

Categorise bank statement transactions into Supabase

Drop a bank statement CSV into Drive and each transaction is sorted into your own categories and saved to your Supabase database.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Google Drive and Supabase, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Google Drive and Supabase automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between Google Drive and Supabase in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every 15 minutes, check my Drive Docs folder for changed files, re-chunk only those, and replace their rows in my Supabase chunks table.

Every night, export rows from my Supabase orders table created yesterday as a CSV into my Drive Reports folder, named by date.

Use cases

Why people connect Google Drive and Supabase

How the two apps work together

  • ClickRuntime checks Drive folders every few minutes for new or changed files.
  • File details or extracted text go into Supabase tables, updating rows when a file changes.
  • In the other direction, a schedule can query Supabase and save results as files in Drive.

  • Developer builds search over company files

    Text from Drive Docs and PDFs can be split, embedded and stored in a Supabase table with pgvector. An app or assistant can then search it.

  • Product team tracks files in a database

    A Supabase table of file names, owners and modified dates gives an app a current list of Drive files.

  • Support team indexes help documents

    Help docs in a Drive folder can be kept in sync with a Supabase table that powers a support bot.

  • Ops exports reports to Drive

    Rows from Supabase can be written into CSV files saved in Drive on a schedule for people who don't use the database.

More apps

Google Drive, Supabase and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

Drive docs embedded with OpenAI into Supabase

Embed every Doc in my Drive Knowledge folder with OpenAI embeddings and store the chunks in my Supabase documents table.

Weekly Supabase report to Drive and Slack

Every Monday, export last week's signups from Supabase to a CSV in Drive and post the link to #growth in Slack.

Index of indexed files

Keep a Google Sheet listing every Drive file stored in Supabase with its last indexed time.

Setup

Connect Google Drive and Supabase once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

Google Drive

File storage

  1. At console.cloud.google.com, create a project and enable the Google Drive API.
  2. Set up the OAuth consent screen and add the scope https://www.googleapis.com/auth/drive.
  3. Create an OAuth client of type Web application with the redirect URI https://clickruntime.com/oauth/callback.
  4. In the ClickRuntime dashboard, open Connections, choose Google Drive and enter the client ID and secret, then connect.
  5. Prefer a service account? Under IAM & Admin → Service Accounts, create one and add a JSON key, share your folders or a Shared Drive with its email, and save the key as a secret on Connections & secrets.

Supabase

Developer / Database & backend

  1. In your Supabase project, open Settings, then API Keys, and copy or create a secret key (it starts with sb_secret_).
  2. Note your project URL, which looks like https://<project-ref>.supabase.co.
  3. If an automation needs the Management API, go to Account, then Access Tokens, and generate a new token.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the project URL and secret key (and the access token, if you made one).

FAQ

Questions about connecting Google Drive and Supabase

How does ClickRuntime connect to Supabase?
With your project URL and a service key saved as secrets in your ClickRuntime dashboard. The key stays on the server and is never shown in logs.
Does it keep the index up to date?
Yes. It checks the folder on a schedule, adds new files, and updates rows for files that changed.
Do I need a particular table layout?
It needs a table with columns for the file, its text and, for search, an embedding. You can use your own table names.
Are the files themselves copied to Supabase?
Usually only the text and details are stored. The original file stays in Drive, linked from the row.
Does it remove deleted files from Supabase?
It can. The script can compare the folder with the table and delete rows for files that are gone.
Which Supabase key does it use?
You add your project URL and a key in the ClickRuntime dashboard. Use a key with only the access the script needs.
How quickly do changes reach Supabase?
Drive is checked on a schedule, as often as every 5 minutes.

Related pages

Keep exploring

Tell your assistant what Google Drive and Supabase should do together

Free plan. No credit card.

Add to ChatGPTAdd to Claude