---
title: "Connect Google Docs to Supabase - APIANT.ai"
description: "When \"Document Structure Changed\" fires in Google Docs, your agent runs \"Create Project Signing Key\" in Supabase."
canonical: "https://apiant.ai/connect/google-docs-to-supabase"
---

# Connect Google Docs to Supabase

When **Document Structure Changed** fires in [Google Docs](https://apiant.ai/connections/google-docs), your agent runs **Create Project Signing Key** in [Supabase](https://apiant.ai/connections/supabase). Describe the whole flow and it is built, tested on every scenario and kept running.

Google Docs **10** triggers Google Docs **46** actions Supabase **138** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Google Docs and Supabase to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Google Docs can start in Supabase

- When **Document Structure Changed** in Google Docs then **Create Project Signing Key** in Supabase
- When **Document Updated** in Google Docs then **Create A Database Branch** in Supabase

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Google Docs and Supabase

## Triggers and actions 10 triggers · 184 actions

- Trigger

**Document Deleted**

Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.

- Trigger

**Document Placeholder Filled**

Triggers when a Google Doc's plain text changes such that a configured placeholder token/pattern is no longer present (i.e., the document has been filled in). This trigger monitors a specific Google Doc and fires when a placeholder pattern that was previously present is no longer found in the document's plain text.

- Trigger

**Document Search Update**

Triggers when a Google Doc matching a user-defined search query is newly created or updated since the last poll. This trigger uses timestamp filtering to efficiently monitor documents.

- Trigger

**Document Structure Changed**

Triggers when a Google Doc's structure changes (headers/footers added/removed, tables/images count changes). This trigger monitors a specific document for structural changes like: - Headers added or removed - Footers added or removed - Tables added or removed - Images (inline objects) added or removed - Positioned objects added or removed - Footnotes added or removed

- Trigger

**Document Updated**

Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.

- Trigger

**Document Word Count Threshold**

Triggers when a Google Doc's word/character count crosses a user-defined threshold. This trigger monitors a specific Google Doc and fires when its word or character count becomes greater than or equal to the configured threshold value.

- Trigger

**Keyword Detected in Document**

Triggers when a specific keyword or phrase first appears in a Google Doc. This trigger monitors a Google Doc and fires once when the specified keyword is detected. After the keyword is found, the trigger will not fire again until reset.

- Trigger

**New Document Added**

Triggers when a new Google Doc is added/created. This trigger monitors Google Docs and fires when new documents are detected.

- Trigger

**New Document Created**

Triggers when a new Google Doc is created. This trigger monitors Google Docs and fires when new documents are detected. Uses timestamp filtering to efficiently poll for new documents.

- Trigger

**New Folder Created in Root**

Triggers when a new folder is created in the root folder of Google Drive. This trigger monitors Google Drive and fires when new folders are detected in the root directory.

- Action

**Copy Document**

Tool to create a copy of an existing google document. use this to duplicate a document, for example, when using an existing document as a template. the copied document will have a default title (e.g., 'copy of [original title]') if no new title is provided, and will be placed in the user's root google drive folder.

- Action

**Create And Populate Table**

Creates a new table in a Google Document and populates its cells with provided text data in a single operation. Use this action when you need to insert a structured table with predefined content into a document. The action handles both table creation and cell population automatically, eliminating the need for separate operations.

- Action

**Create Document**

Creates a new google docs document using the provided title as filename and inserts the initial text at the beginning if non-empty, returning the document's id and metadata (excluding body content).

- Action

**Create Document Markdown**

Creates a new google docs document, optionally initializing it with a title and content provided as markdown text.

- Action

**Create Footer**

Tool to create a new footer in a google document. use when you need to add a footer, optionally specifying its type and the section it applies to.

- Action

**Create Footnote**

Tool to create a new footnote in a google document. use this when you need to add a footnote at a specific location or at the end of the document body.

- Action

**Create Header**

Tool to create a new header in a google document. use this tool when you need to add a header to a document, optionally specifying the section it applies to.

- Action

**Create Named Range**

Tool to create a new named range in a google document. use this to assign a name to a specific part of the document for easier reference or programmatic manipulation.

- Action

**Create Paragraph Bullets**

Tool to add bullets to paragraphs within a specified range in a google document. use when you need to format a list or a set of paragraphs as bullet points.

- Action

**Create Tab**

Creates a new tab in a Google Docs document. Tabs allow you to organize document content into separate sections within a single document. Use this action when you need to add a new organizational tab to a document. When a tab is added at a specified index, all subsequent tabs' indexes are automatically incremented.

- Action

**Delete Content Range**

Tool to delete a range of content from a google document. use when you need to remove a specific portion of text or other structural elements within a document.

- Action

**Delete Footer**

Tool to delete a footer from a google document. use when you need to remove a footer from a specific section or the default footer.

- Action

**Delete Header**

Deletes the header from the specified section or the default header if no section is specified. use this tool to remove a header from a google document.

- Action

**Delete Named Range**

Tool to delete a named range from a google document. use when you need to remove a previously defined named range by its id or name.

- Action

**Delete Paragraph Bullets**

Tool to remove bullets from paragraphs within a specified range in a google document. use when you need to clear bullet formatting from a section of a document.

- Action

**Delete Tab**

Deletes a tab from a Google Document. This action is irreversible — the tab cannot be recovered once removed. Use when you need to remove a tab and all its child tabs from a document's tab structure.

- Action

**Delete Table**

Tool to delete an entire table from a google document. use when you have the document id and the specific start and end index of the table element to be removed. the table's range can be found by inspecting the document's content structure.

- Action

**Delete Table Column**

Tool to delete a column from a table in a google document. use this tool when you need to remove a specific column from an existing table within a document.

- Action

**Delete Table Row**

Tool to delete a row from a table in a google document. use when you need to remove a specific row from an existing table.

- Action

**Export Document As Pdf**

Tool to export a Google Docs file as PDF using the Google Drive API. Use when you need to generate a PDF version of a Google Docs document for download or distribution. Note: Google Drive enforces a 10MB limit on export content.

- Action

**Get Docs Drive File Metadata**

Get selected metadata fields for one Google Drive file by ID.

- Action

**Get Docs Spreadsheet Values**

Read cell values from one range in a Google Sheets spreadsheet.

- Action

**Get Document By Id**

Retrieves an existing google document by its id; will error if the document is not found.

- Action

**Get Document End Index**

Retrieves the end index and paragraph structure of a Google Document or specific segment. Use this action when you need to determine valid insertion points for text operations, especially before using insertText requests. The end index represents the maximum boundary of the document body or specified segment (header, footer, footnote, or tab).

- Action

**Get Document Plaintext**

Retrieve a Google Doc by ID and return a best-effort plain-text rendering. Converts document structure into plain text including paragraphs, lists, and tables without requiring clients to traverse complex Docs API JSON.

- Action

**Insert Image In Table Cell**

Inserts an image from a given URI into a specific table cell in a Google Document. Use this action when you need to add an image to a particular cell within a table. The action identifies the target cell by table start index, row index, and column index, then inserts the image at the specified position within that cell's content.

- Action

**Insert Inline Image**

Tool to insert an image from a given uri at a specified location in a google document as an inline image. use when you need to add an image to a document programmatically.

- Action

**Insert Page Break**

Tool to insert a page break into a google document. use when you need to start new content on a fresh page, such as at the end of a chapter or section.

- Action

**Insert Table Action**

Tool to insert a table into a google document. use when you need to add a new table at a specific location or at the end of a segment (like document body, header, or footer) in a document.

- Action

**Insert Table Column**

Tool to insert a new column into a table in a google document. use this tool when you need to add a column to an existing table at a specific location.

- Action

**Insert Table Row**

Inserts a new row into a table in a Google Document at a specified location. Use this action when you need to add a row to an existing table, either above or below a reference cell location.

- Action

**Insert Text Action**

Tool to insert a string of text at a specified location within a google document. use when you need to add new text content to an existing document.

- Action

**Insert Text In Table Cell**

Inserts text into a specific cell of a table in a Google Document by row and column position. Use this action when you need to add or update text content in a table cell at a known row and column index. To use this action, you must first retrieve the document structure using GOOGLEDOCS_GET_DOCUMENT_BY_ID to find the table's start index. Then specify the target cell by its zero-based row and column indices (e.g., row_index=0, column_index=0 for the top-left cell).

- Action

**List Drive Item Permissions**

List permissions for a Google Drive file, folder, or shared drive.

- Action

**List Spreadsheet Charts**

Tool to retrieve a list of all charts from a specified Google Sheets spreadsheet. Use when you need to get chart IDs and their specifications for embedding or referencing elsewhere, such as in Google Docs.

- Action

**Replace All Text**

Tool to replace all occurrences of a specified text string with another text string throughout a google document. use when you need to perform a global find and replace operation within a document.

- Action

**Replace Image**

Tool to replace a specific image in a document with a new image from a uri. use when you need to update an existing image within a google doc.

- Action

**Search Documents**

Search for google documents using various filters including name, content, date ranges, and more.

- Action

**Unmerge Table Cells**

Tool to unmerge previously merged cells in a table. use this when you need to revert merged cells in a google document table back to their individual cell states.

- Action

**Update Document Markdown**

Replaces the entire content of an existing google docs document with new markdown text; requires edit permissions for the document.

- Action

**Update Document Section Markdown**

Tool to insert or replace a section of a Google Docs document with Markdown content. Use when you need to update only a section of a document by specifying start and optional end indices. Supports full Markdown formatting.

- Action

**Update Document Style**

Tool to update the overall document style, such as page size, margins, and default text direction. use when you need to modify the global style settings of a google document.

- Action

**Update Existing Document**

Applies programmatic edits, such as text insertion, deletion, or formatting, to a specified google doc using the `batchupdate` api method.

- Action

**Update Table Row Style**

Tool to update the style of a table row in a google document. use when you need to modify the appearance of specific rows within a table, such as setting minimum row height or marking rows as headers.

- Action

**Update Tab Properties**

Updates properties of a document tab such as title, parent tab, index, and icon emoji. Use this action when you need to rename a tab, change its emoji icon, move it within the tab hierarchy, or reorganize tab structure.

- Action

**Upload Drive File**

Upload a file of 5 MiB or less to Google Drive using multipart upload.

- Action

**Alpha Create Api Key**

Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates.

- Action

**Alpha Creates A New Api Key For The Project**

Creates a 'publishable' or 'secret' api key for an existing supabase project, optionally with a description; 'secret' keys can have customized jwt templates.

- Action

**Alpha Delete Api Key**

Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.

- Action

**Alpha Delete Third Party Auth Integration**

Removes a third-party authentication provider (e.g., Google, GitHub) from a Supabase project's configuration; this immediately prevents users from logging in via that method.

- Action

**Alpha Get A Third Party Integration**

Retrieves the detailed configuration for a specific third-party authentication (tpa) provider, identified by `tpa id`, within an existing supabase project specified by `ref`.

- Action

**Alpha Lists All Third Party Auth Integrations**

Lists all configured third-party authentication provider integrations for an existing supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.

- Action

**Alpha List Third Party Auth Integrations**

Lists all configured third-party authentication provider integrations for an existing Supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.

- Action

**Alpha Removes A Third Party Auth Integration**

Removes a third-party authentication provider (e.g., google, github) from a supabase project's configuration; this immediately prevents users from logging in via that method.

- Action

**Alpha Update Api Key**

Updates an existing Supabase project API key's `description` and/or `secret_jwt_template` (which defines its `role`); does not regenerate the key string.

- Action

**Alpha Updates An Api Key For The Project**

Updates an existing supabase project api key's `description` and/or `secret jwt template` (which defines its `role`); does not regenerate the key string.

- Action

**Apply A Migration**

Tool to apply database migrations to a Supabase project. Use when you need to execute SQL schema changes, create tables, alter columns, or run other DDL/DML operations as part of a tracked migration. This is a Beta feature in the Supabase Management API.

- Action

**Beta Activates A Vanity Subdomain For A Project**

Activates a vanity subdomain for the specified supabase project, requiring subsequent dns configuration for the subdomain to become operational.

- Action

**Beta Activate Vanity Subdomain**

Activates a vanity subdomain for the specified Supabase project (e.g., 'my-brand.supabase.co'). Important notes: - Vanity subdomains require a paid plan (Pro/Team/Enterprise) - Usage of vanity subdomains and custom domains is mutually exclusive - After activation, your project's auth services will no longer work on the original {project-ref}.supabase.co hostname - Schedule a downtime window to update client code and OAuth providers before activating

- Action

**Beta Checks Vanity Subdomain Availability**

Checks if a specific vanity subdomain is available for a supabase project; this action does not reserve or assign the subdomain.

- Action

**Beta Check Vanity Subdomain Availability**

Checks if a specific vanity subdomain is available for a Supabase project; this action does not reserve or assign the subdomain.

- Action

**Beta Enable Database Webhooks**

Enables database webhooks for the Supabase project `ref`, triggering real-time notifications for INSERT, UPDATE, or DELETE events.

- Action

**Beta Get Project Network Bans**

Retrieves the list of banned IPv4 addresses for a Supabase project using its unique project reference string; this is a read-only operation.

- Action

**Beta Get Project Network Restrictions**

Retrieves the network restriction settings (IP allowlists) for a Supabase project. Use this action to: - Check which IPv4/IPv6 CIDR blocks are allowed to connect to the project's database - Verify if network restrictions are enabled (entitlement: "allowed") or disabled ("disallowed") - Audit current network security configuration - Check if network restrictions have been modified (old_config present) Note: Default values 0.0.0.0/0 (IPv4) and::/0 (IPv6) mean all IPs are allowed. Network restrictions require a Pro, Team, or Enterprise plan.

- Action

**Beta Get Project Pgsodium Config**

Retrieves the PGSodium configuration, including the root encryption key, for an existing Supabase project identified by its `ref`.

- Action

**Beta Get Project Ssl Enforcement Config**

Retrieves the SSL enforcement configuration for a specified Supabase project, indicating if SSL connections are mandated for its database.

- Action

**Beta Get Project S Ssl Enforcement Configuration**

Retrieves the ssl enforcement configuration for a specified supabase project, indicating if ssl connections are mandated for its database.

- Action

**Beta Gets Current Vanity Subdomain Config**

Fetches the current vanity subdomain configuration, including its status and custom domain name, for a supabase project identified by its reference id.

- Action

**Beta Gets Project S Network Bans**

Retrieves the list of banned ipv4 addresses for a supabase project using its unique project reference string; this is a read-only operation.

- Action

**Beta Gets Project S Network Restrictions**

Retrieves the current network restriction settings (e.g., ip whitelists) for a supabase project using its reference id; this is a read-only operation for auditing or verifying network security.

- Action

**Beta Gets Project S Pgsodium Config**

Retrieves the pgsodium configuration, including the root encryption key, for an existing supabase project identified by its `ref`.

- Action

**Beta Get Vanity Subdomain Config**

Fetches the current vanity subdomain configuration, including its status and custom domain name, for a Supabase project identified by its reference ID.

- Action

**Beta Remove Network Bans**

Removes specified ipv4 addresses from a supabase project's network ban list, granting immediate access; ips not currently banned are ignored.

- Action

**Beta Run Sql Query**

Executes a given sql query against the project's database; use for advanced data operations or when standard api endpoints are insufficient, ensuring queries are valid postgresql and sanitized. use the get table schemas or generate type script types tool to retrieve the table schema, then base your query on it.

- Action

**Beta Update Project Network Restrictions**

Updates and applies network access restrictions (IPv4/IPv6 CIDR lists) for a Supabase project, which may terminate existing connections not matching the new rules.

- Action

**Beta Updates Project S Network Restrictions**

Updates and applies network access restrictions (ipv4/ipv6 cidr lists) for a supabase project, which may terminate existing connections not matching the new rules.

- Action

**Config Pgsodium Update With Root Key Warning**

Critically updates or initializes a supabase project's pgsodium root encryption key for security setup or key rotation, requiring secure backup of the new key to prevent irreversible data loss.

- Action

**Count Action Runs**

Counts the number of action runs for a Supabase project using a HEAD request. Use this when you need to retrieve the total count of action runs without fetching the full list of runs.

- Action

**Create A Database Branch**

Creates a new, isolated database branch from an existing supabase project (identified by `ref`), useful for setting up separate environments like development or testing, which can optionally be linked to a git branch.

- Action

**Create A Function**

Creates a new serverless edge function for a supabase project (identified by `ref`), requiring valid javascript/typescript in `body` and a project-unique `slug 1` identifier.

- Action

**Create Bulk Secrets**

Tool to bulk create secrets for a Supabase project. Use when you need to create multiple project secrets at once. Each secret name must not start with SUPABASE_.

- Action

**Create Login Role**

Creates a temporary CLI login role for database access with specified permissions; use when setting up CLI authentication for development or administrative tasks.

- Action

**Create Project Signing Key**

Create a new signing key for JWT authentication in a Supabase project. The key is created in standby status by default and must be activated separately.

- Action

**Creates A New Sso Provider**

Creates a new saml 2.0 single sign-on (sso) provider for a supabase project, requiring either `metadata xml` or `metadata url` for saml idp configuration.

- Action

**Creates A New Third Party Auth Integration**

Call this to add a new third-party authentication method (oidc or jwks) to a supabase project for integrating external identity providers (e.g., for sso); the api may also support `custom jwks` if sent directly.

- Action

**Create Signed Upload Url**

Create a two-hour signed authorization for uploading a Storage object. OAuth connections need ``secrets:read``. Fine-grained personal access tokens need ``api_gateway_keys_read`` and ``api_gateway_keys_secret_read``.

- Action

**Create Sso Provider**

Creates a new SAML 2.0 Single Sign-On (SSO) provider for a Supabase project, requiring either `metadata_xml` or `metadata_url` for SAML IdP configuration.

- Action

**Create Third Party Auth Integration**

Call this to add a new third-party authentication method (OIDC or JWKS) to a Supabase project for integrating external identity providers (e.g., for SSO); the API may also support `custom_jwks` if sent directly.

- Action

**Delete A Database Branch**

Permanently and irreversibly deletes a specific, non-default database branch by its `branch id`, without affecting other branches.

- Action

**Delete A Function**

Permanently deletes a specific edge function (by `function slug`) from a supabase project (by `ref`); this action is irreversible and requires prior existence of both project and function.

- Action

**Delete Edge Function**

Deletes an Edge Function from a Supabase project by its slug. Use this action when you need to permanently remove a deployed Edge Function that is no longer needed or should be replaced. This action is irreversible — the function cannot be recovered once deleted, though you can redeploy it from source if needed.

- Action

**Delete Login Roles**

[Beta] Deletes existing login roles used by the Supabase CLI for the specified project. Use when you need to remove CLI authentication roles that were previously created for project access.

- Action

**Delete Project Vanity Subdomain**

Permanently and irreversibly deletes an active vanity subdomain configuration for the specified supabase project, reverting it to its default supabase url.

- Action

**Delete Sso Provider**

Deletes a specific SSO provider by its ID (`provider_id`) from a Supabase project (`ref`), which disables it and returns its details; ensure this action will not inadvertently lock out users.

- Action

**Deploy Function**

Deploys edge functions to a supabase project using multipart upload.

- Action

**Disable Project Readonly**

Temporarily disables a supabase project's read-only mode for 15 minutes to allow write operations (e.g., for maintenance or critical updates), after which it automatically reverts to read-only.

- Action

**Disables Preview Branching**

Disables the preview branching feature for an existing supabase project, identified by its unique reference id (`ref`).

- Action

**Generate Typescript Types**

Generates and retrieves TypeScript types from a Supabase project's database; any schemas specified in `included_schemas` must exist in the project.

- Action

**Generate Type Script Types**

Generates and retrieves typescript types from a supabase project's database; any schemas specified in `included schemas` must exist in the project.

- Action

**Get Auth Config**

Retrieves the complete authentication configuration for a Supabase project. Use this action when you need to inspect auth settings, OAuth provider configurations, MFA policies, email/SMS templates, security policies, or webhook hooks. Returns all auth configuration fields including enabled providers (Apple, Google, GitHub, etc.), JWT settings, rate limits, password requirements, session policies, and mailer configuration. This is a read-only operation that does not modify any settings.

- Action

**Get Available Regions**

Tool to get the list of available regions for creating a new Supabase project. Use when you need to determine which regions are available for project deployment, or to get region recommendations based on geographic location and instance size requirements. Note: This is a Beta endpoint.

- Action

**Get Branch**

Retrieves detailed information about a specific database branch by its name and project reference. Use this to check branch status, configuration, and metadata before performing operations on the branch.

- Action

**Get Database Branch Config**

Retrieves the read-only configuration and status for a supabase database branch, typically for monitoring or verifying its settings.

- Action

**Get Database Metadata**

Gets database metadata for the given project. Returns information about databases, schemas, and tables structure. Note: This endpoint is deprecated and may be removed in future versions.

- Action

**Get Function**

Retrieves detailed information, metadata, configuration, and status for a specific Edge Function using its project reference ID and function slug.

- Action

**Get Function Body**

Retrieves the source code (body) for a specified serverless Edge Function using its project reference and function slug; this is a read-only operation that does not execute the function or return runtime logs.

- Action

**Get Legacy Signing Key**

Retrieves the signing key information for the JWT secret imported as signing key for this project. This endpoint is deprecated and will be removed in the future; check for HTTP 404 Not Found which indicates the endpoint is no longer available.

- Action

**Get Migration**

Retrieves a specific database migration entry from the migration history using its version identifier. Use when you need to inspect migration details, SQL statements, or rollback commands for a specific migration version.

- Action

**Get Organization**

Fetches comprehensive details for a specific Supabase organization using its unique slug.

- Action

**Get Performance Advisors**

Retrieves project performance advisors for a Supabase project. Returns a list of performance lints that identify potential issues and optimization opportunities. Note: This endpoint is deprecated.

- Action

**Get Project**

Retrieves detailed information about a specific Supabase project by its unique reference ID. Use when you need to get comprehensive project details including status, database configuration, and metadata. Authentication: - Requires a valid Bearer token in the Authorization header.

- Action

**Get Project Api Key**

Retrieves details of a specific API key for a Supabase project by its UUID. Use when you need to inspect a single key's configuration, type, or metadata.

- Action

**Get Project Api Keys**

Retrieves all api keys for an existing supabase project, specified by its unique reference id (`ref`); this is a read-only operation.

- Action

**Get Project Legacy Api Keys**

Checks whether JWT-based legacy API keys (anon, service_role) are enabled for a Supabase project. This API endpoint is deprecated and may be removed in the future (returns HTTP 404 Not Found when unavailable).

- Action

**Get Project Logs**

Retrieves the unified logs stream for a Supabase project, including database, API, and edge function logs, for monitoring and debugging. Custom queries use ClickHouse SQL against the logs table, filtering by source; legacy source tables and metadata joins must be migrated. Provide both UTC timestamps for a time window; Supabase documents a last-minute fallback without both and a maximum 24-hour range. Check the response's error field even when execution reports success. Returned row fields depend on the query.

- Action

**Get Project Metrics**

Retrieve a Supabase project's Prometheus/OpenMetrics exposition.

- Action

**Get Project Postgres Config**

Retrieves the current read-only PostgreSQL database configuration for a specified Supabase project's `ref`, noting that some advanced or security-sensitive details might be omitted from the response.

- Action

**Get Project Postgrest Config**

Retrieves the PostgREST configuration for a specific Supabase project.

- Action

**Get Project Readonly Mode Status**

Retrieves the read-only mode status for a specified Supabase project to check its operational state; this action does not change the read-only state.

- Action

**Get Project Signing Keys**

Tool to list all signing keys for a Supabase project. Use when you need to retrieve JWT signing keys for authentication verification or rotation management.

- Action

**Get Project S Pgbouncer Config**

Retrieves the active pgbouncer configuration (postgresql connection pooler) for a supabase project, used for performance tuning, auditing, or getting the connection string.

- Action

**Get Project Supavisor Config**

Retrieves the Supavisor (connection pooler) configuration for a specified Supabase project, identified by its reference ID.

- Action

**Get Project Upgrade Eligibility**

Checks a supabase project's eligibility for an upgrade, verifying compatibility and identifying potential issues; this action does not perform the actual upgrade.

- Action

**Get Project Upgrade Status**

Retrieves the latest status of a supabase project's database upgrade for monitoring purposes; does not initiate or modify upgrades.

- Action

**Gets A Specific Sql Snippet**

Retrieves a specific sql snippet by its unique identifier.

- Action

**Gets A Sso Provider By Its Uuid**

Retrieves the configuration details for a specific single sign-on (sso) provider (e.g., saml, google, github, azure ad), identified by its uuid, within a supabase project.

- Action

**Get Security Advisors**

Retrieves security advisor findings and recommendations for a Supabase project. Use when you need to audit project security posture, identify SQL-based security issues, or get remediation guidance. Note: This endpoint is deprecated and may be removed in future API versions.

- Action

**Gets Information About The Organization**

Fetches comprehensive details for a specific supabase organization using its unique slug.

- Action

**Gets Project S Auth Config**

Retrieves the project's complete read-only authentication configuration, detailing all settings (e.g., providers, mfa, email/sms, jwt, security policies) but excluding sensitive secrets.

- Action

**Gets Project S Postgres Config**

Retrieves the current read-only postgresql database configuration for a specified supabase project's `ref`, noting that some advanced or security-sensitive details might be omitted from the response.

- Action

**Gets Project S Postgrest Config**

Retrieves the postgrest configuration for a specific supabase project.

- Action

**Gets Project S Service Health Status**

Retrieves the current health status for a supabase project, for specified services or all services if the 'services' list is omitted.

- Action

**Gets Project S Supavisor Config**

Retrieves the supavisor (connection pooler) configuration for a specified supabase project, identified by its reference id.

- Action

**Get Sql Snippet**

Retrieves a specific SQL snippet by its unique identifier.

- Action

**Get Sso Provider**

Retrieves the configuration details for a specific Single Sign-On (SSO) provider (e.g., SAML, Google, GitHub, Azure AD), identified by its UUID, within a Supabase project.

- Action

**Get Table Schemas**

Retrieves column details, types, and constraints for multiple database tables to help debug schema issues and write accurate sql queries.

- Action

**Invoke Database Function**

Invoke a known exposed Postgres function with named JSON arguments. Supports custom exposed schemas and table-valued result selection, filters, ordering, pagination, and counts. The function runs with a service-role project key that bypasses Row Level Security and may create, update, or delete data or execute DDL.

- Action

**Invoke Edge Function**

Tool to invoke a deployed Supabase Edge Function over HTTPS. Use for testing and debugging Edge Functions with configurable method, headers, body, and authentication.

- Action

**List All Database Branches**

Lists all database branches for a specified supabase project, used for isolated development and testing of schema changes; ensure the project reference id is valid.

- Action

**List All Functions**

Lists metadata for all edge functions in a supabase project (specified by 'ref'), excluding function code or logs; the project must exist.

- Action

**List All Organizations**

Lists all organizations (id and name only) associated with the supabase account, excluding project details within these organizations.

- Action

**List All Projects**

Retrieves a list of all supabase projects, including their id, name, region, and status, for the authenticated user.

- Action

**List All Secrets**

Retrieves all secrets for a supabase project using its reference id; secret values in the response may be masked.

- Action

**List Backups**

Lists all database backups for a Supabase project, providing details on existing backups but not creating new ones or performing restores; availability may depend on plan and configuration.

- Action

**List Branches**

Lists all database branches for a specified Supabase project, providing information about each branch's status, configuration, and metadata. Use this action when you need to view all branches in a project, check branch statuses, or identify available branches before performing operations. Database branches are useful for isolated development and testing of schema changes.

- Action

**List Buckets**

Retrieves a list of all storage buckets for a Supabase project, without returning bucket contents or access policies.

- Action

**List Database Branches**

Lists all database branches for a specified Supabase project, used for isolated development and testing of schema changes; ensure the project reference ID is valid.

- Action

**List Functions**

Lists metadata for all Edge Functions in a Supabase project (specified by 'ref'), excluding function code or logs; the project must exist.

- Action

**List Members Of An Organization**

Retrieves all members of a supabase organization, identified by its unique slug, including their user id, username, email, role, and mfa status.

- Action

**List Migration History**

Retrieves the list of applied database migration versions for a Supabase project. Use this to track which migrations have been applied to the project's database. This is a read-only operation that requires the project reference ID.

- Action

**List Project Secrets**

Retrieves all secrets (environment variables) for a Supabase project by its reference ID. Use this action when you need to view the secrets configured for a project, such as API keys, database URLs, or other environment variables. Note that secret values in the response may be masked for security reasons.

- Action

**Lists All Backups**

Lists all database backups for a supabase project, providing details on existing backups but not creating new ones or performing restores; availability may depend on plan and configuration.

- Action

**Lists All Buckets**

Retrieves a list of all storage buckets for a supabase project, without returning bucket contents or access policies.

- Action

**Lists All Sso Providers**

Lists all configured single sign-on (sso) providers for a supabase project, requiring the project reference id (`ref`) of an existing project.

- Action

**List Secrets**

Retrieves all secrets for a Supabase project using its reference ID; secret values in the response may be masked.

- Action

**List Sso Providers**

Lists all configured Single Sign-On (SSO) providers for a Supabase project, requiring the project reference ID (`ref`) of an existing project.

- Action

**Lists Sql Snippets For The Logged In User**

Retrieves a list of sql snippets for the logged-in user, optionally filtered by a specific supabase project if `project ref` is provided.

- Action

**List Tables**

Lists all tables and views in specified database schemas, providing a quick overview of database structure to help identify available tables before fetching detailed schemas.

- Action

**Merge Branch**

Merges a database branch, applying all schema changes and migrations from the branch to the target database. Use this action when you need to promote changes from a database branch to production or another target environment after testing and validation are complete. This operation is irreversible - once merged, the changes cannot be automatically rolled back.

- Action

**Patch Migration**

[Beta] Patches an existing entry in the project's migration history, updating the name or rollback script. Use this to correct migration metadata after the migration has been created.

- Action

**Patch Network Restrictions**

Updates project's network restrictions by incrementally adding or removing IPv4/IPv6 CIDR blocks. Use when you need to modify existing restrictions without replacing the entire configuration.

- Action

**Push Branch**

Pushes a database branch, applying migrations and changes to the specified branch. Use when you need to deploy schema changes or migrations to a database branch.

- Action

**Removes A Sso Provider By Its Uuid**

Deletes a specific sso provider by its id (`provider id`) from a supabase project (`ref`), which disables it and returns its details; ensure this action will not inadvertently lock out users.

- Action

**Resets A Database Branch**

Resets an existing supabase database branch, identified by `branch id`, to its initial clean state, irreversibly deleting all its current data and schema changes.

- Action

**Retrieve A Function**

Retrieves detailed information, metadata, configuration, and status for a specific edge function using its project reference id and function slug.

- Action

**Retrieve A Function Body**

Retrieves the source code (body) for a specified serverless edge function using its project reference and function slug; this is a read-only operation that does not execute the function or return runtime logs.

- Action

**Returns Project S Readonly Mode Status**

Retrieves the read-only mode status for a specified supabase project to check its operational state; this action does not change the read-only state.

- Action

**Run Read Only Query**

[Beta] Run a SQL query as supabase_read_only_user. Use when you need to safely execute SELECT queries without risk of modifying data. Only read operations are allowed.

- Action

**Select From Table**

Tool to select rows from a Supabase/PostgREST table. Use for read-only queries with filtering, sorting, and pagination.

- Action

**Update A Function**

Updates an existing supabase edge function's properties (like name, slug, source code, jwt settings, import map) identified by project `ref` and `function slug`, supporting plain text code or eszip for the body.

- Action

**Update Api Key**

Updates an existing Supabase project API key's metadata including name, description, and JWT template configuration. This action modifies key properties without regenerating the actual key value. Use this action when you need to change a key's display name, update its description for better organization, or modify the JWT role template for secret-type keys. Note: This does not rotate or regenerate the key string itself - the key value remains unchanged unless explicitly revealed with reveal=true.

- Action

**Update Database Branch Config**

Updates the configuration of a supabase database branch, allowing modification of its name, associated git branch, reset-on-push behavior, persistence, and status.

- Action

**Update Project**

Updates a Supabase project's configuration (currently supports updating the project name). Use when you need to rename an existing project.

- Action

**Update Project Auth Config**

Update Supabase project Auth configuration via the Management API. Use to fix misconfigured Auth redirects, SMTP settings, or other auth parameters. Only provided fields are updated; others remain unchanged. Before updating, confirm the Auth service status is ACTIVE_HEALTHY by checking project health.

- Action

**Update Project Postgres Config**

Updates specified PostgreSQL configuration parameters for an existing Supabase project (`ref`) to optimize database performance; note that unspecified parameters remain unchanged, and caution is advised as incorrect settings can impact stability or require a restart.

- Action

**Update Project Postgrest Config**

Updates PostgREST configuration settings (e.g., `max_rows`, `db_pool`, `db_schema`, `db_extra_search_path`) for a Supabase project to fine-tune API performance, data exposure, and database resource usage.

- Action

**Update Project Supavisor Config**

Updates the Supavisor (database pooler) configuration, such as `default_pool_size`, for an existing Supabase project identified by `ref`; the `pool_mode` parameter in the request is deprecated and ignored.

- Action

**Updates A Sso Provider By Its Uuid**

Updates an existing sso provider's saml metadata, associated email domains, or attribute mappings for a supabase project, identified by `ref` and `provider id`.

- Action

**Updates Project S Postgres Config**

Updates specified postgresql configuration parameters for an existing supabase project (`ref`) to optimize database performance; note that unspecified parameters remain unchanged, and caution is advised as incorrect settings can impact stability or require a restart.

- Action

**Updates Project S Postgrest Config**

Updates postgrest configuration settings (e.g., `max rows`, `db pool`, `db schema`, `db extra search path`) for a supabase project to fine-tune api performance, data exposure, and database resource usage.

- Action

**Updates Project S Supavisor Config**

Updates the supavisor (database pooler) configuration, such as `default pool size`, for an existing supabase project identified by `ref`; the `pool mode` parameter in the request is deprecated and ignored.

- Action

**Update Ssl Enforcement Config**

Updates the ssl enforcement configuration (enable/disable) for a specified supabase project's database.

- Action

**Update Sso Provider**

Updates an existing SSO provider's SAML metadata, associated email domains, or attribute mappings for a Supabase project, identified by `ref` and `provider_id`.

- Action

**Upsert Migration**

Tool to upsert a database migration without applying it. Use when you need to track migration changes for a project. [Beta] This endpoint stores migration metadata without executing the SQL.

## Each app on its own

- [ **Google Docs** Google Docs is a cloud-based word processor with real-time collaboration, version history, and integration...](https://apiant.ai/connections/google-docs)
- [ **Supabase** Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...](https://apiant.ai/connections/supabase)

Reviews

## What our customers say

## More from Google Docs

- [ **Google Docs to Google Drive** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-docs-to-google-drive)
- [ **Google Docs to Contentful** Contentful is a headless CMS allowing developers to create, manage, and distribute content across multiple...](https://apiant.ai/connect/google-docs-to-contentful)
- [ **Google Docs to Minecraft Server Status** Minecraft Server Status pings a Minecraft server address and reports what it finds.](https://apiant.ai/connect/google-docs-to-minecraft-server-status)
- [ **Google Docs to Mistral AI** Mistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...](https://apiant.ai/connect/google-docs-to-mistral-ai)
- [ **Google Docs to Onepage** Onepage helps you build landing pages in minutes.](https://apiant.ai/connect/google-docs-to-onepage)
- [ **Google Docs to Raider** Raider.IO scores and ranks World of Warcraft characters and guilds on Mythic+ dungeon and raid progression.](https://apiant.ai/connect/google-docs-to-raider)

## More into Supabase

- [ **Airtable to Supabase** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-supabase)
- [ **Benetics to Supabase** Benetics is a construction efficiency platform built in the cloud.](https://apiant.ai/connect/benetics-to-supabase)
- [ **Erpnext to Supabase** Open-source ERP system for accounting, inventory, manufacturing, sales, projects, and CRM.](https://apiant.ai/connect/erpnext-to-supabase)
- [ **Form Io to Supabase** Form-builder platform that auto-generates REST APIs for form submissions, data validation, and workflow...](https://apiant.ai/connect/form-io-to-supabase)
- [ **ONLYOFFICE DocSpace to Supabase** ONLYOFFICE DocSpace is a room-based collaboration environment for organizing teamwork on an any content.](https://apiant.ai/connect/onlyoffice-docspace-to-supabase)
- [ **HubSpot to Supabase** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-supabase)

Questions

## Google Docs and Supabase, answered

###

### What can start an automation from Google Docs?

Any of Google Docs's 10 triggers in the catalog, including Document Structure Changed, Document Updated, New Document Added and New Document Created. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Supabase when something happens in Google Docs?

Any of Supabase's 138 actions, including Create A Database Branch, Create A Function, Create Bulk Secrets and Create Login Role. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Supabase to Google Docs?

Supabase has no triggers in the catalog today, so automations start in Google Docs. If you need the other direction, ask: your agent reads Supabase's API documentation and adds it.

###

### Do I have to build a connector for Google Docs or Supabase?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Google Docs and Supabase without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
