Supabase Integration — Automate Supabase with AI on Beauto

Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and real-time subscription APIs for building modern applications

Category: developer tools, databases · 124 actions available

What you can automate with Supabase

Beauto connects Supabase with 900+ other apps so you can build AI-powered workflows in minutes. Trigger automations from Supabase events, enrich Supabase data with AI, or sync Supabase with the rest of your stack — without writing code.

  • Sync Supabase data with Gmail, Slack, Notion, HubSpot, Google Sheets, and more
  • Trigger AI agents on new Supabase events and route the output anywhere
  • Schedule recurring Supabase tasks — daily reports, cleanups, or bulk updates
  • Use natural language to describe the workflow; Beauto builds it for you

Supabase actions Beauto supports

  • Create project 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.
  • Delete an API key from the project — Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.
  • Delete third party auth config — 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.
  • 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`.
  • List third-party auth integrations for project — 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.
  • Update 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.
  • Apply a database 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 featu
  • Beta activate custom hostname for project — Activates a previously configured custom hostname for a Supabase project, assuming DNS settings are verified externally.
  • Activate vanity subdomain for project — 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 domai
  • Authorize user through OAuth — Generates a Supabase OAuth 2.0 authorization URL for user redirection. IMPORTANT: This action requires a pre-registered OAuth client_id and a redirect_uri that matches one of the pre-registered URIs for that OAuth applic
  • 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.
  • Setup read replica for project — Provisions a read-only replica for a Supabase project in a specified, Supabase-supported AWS region to enhance read performance and reduce latency.
  • Enable project database webhooks — Enables database webhooks for the Supabase project `ref`, triggering real-time notifications for INSERT, UPDATE, or DELETE events.
  • Beta get project's custom hostname config — Retrieves a Supabase project's custom hostname configuration, including its status, SSL certificate, and ownership verification, noting that availability may depend on the project's plan.
  • Retrieve network bans for project — Retrieves the list of banned IPv4 addresses for a Supabase project using its unique project reference string; this is a read-only operation.
  • 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
  • Get project pgsodium config — Retrieves the PGSodium configuration, including the root encryption key, for an existing Supabase project identified by its `ref`.
  • Get project SSL enforcement configuration — Retrieves the SSL enforcement configuration for a specified Supabase project, indicating if SSL connections are mandated for its database.
  • Get 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.
  • Remove project network bans — Removes specified IPv4 addresses from a Supabase project's network ban list, granting immediate access; IPs not currently banned are ignored.
  • Remove read replica — Remove a read replica from a Supabase project (Pro plan or higher required). This beta endpoint initiates the removal of a specified read replica database. The operation is irreversible. Before removal, ensure all applic
  • Execute project database 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
  • 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.
  • Upgrade the project's PostgreSQL version — Initiates an asynchronous upgrade of a Supabase project's PostgreSQL database to a specified `target_version` from a selected `release_channel`, returning a `tracking_id` to monitor status; the `target_version` must be a
  • 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.
  • Create new project — Creates a new Supabase project, requiring a unique name (no dots) within the organization; project creation is asynchronous.
  • Bulk create 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_.
  • 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.
  • 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` identifier.
  • Create CLI 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.
  • Create an organization — Creates a new Supabase organization, which serves as a top-level container for projects, billing, and team access.
  • 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.
  • Create SSO provider configuration — 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.
  • Create 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.
  • Delete custom hostname config — Deletes an active custom hostname configuration for the project identified by `ref`, reverting to the default Supabase-provided hostname; this action immediately makes the project inaccessible via the custom domain and r
  • Delete branch by id — Permanently and irreversibly deletes a specific, non-default database branch by its `branch_id`, without affecting other branches.
  • Delete an edge function by slug — 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.
  • Delete CLI 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.
  • Delete project by ref — Permanently and irreversibly deletes a Supabase project, identified by its unique `ref` ID, resulting in complete data loss.
  • Delete vanity subdomain for project — Permanently and irreversibly deletes an active vanity subdomain configuration for the specified Supabase project, reverting it to its default Supabase URL.

Related integrations

Browse all 900+ integrations →

Get started with Supabase on Beauto

Sign up free, connect your Supabase account in one click, and describe the workflow you want in plain English. Beauto's AI handles the rest — no API keys or code required.

Try Beauto free · Browse all 900+ integrations · How it works