All connectors
Supabase integration
Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and real-time subscription APIs for building modern applications
Connect Supabase to Xenition and work with it from chat, from an agent, or on a schedule — alongside every other app you have connected, in one workspace.
What you can do with Supabase
Ask in plain language and Xenition calls the right one:
- 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 feature in the Supabase Management API.
- 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 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 upd
- 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 application. Without a valid registered OAuth application, this endpoint will return a 400 error. To use this action: 1. Register an OAuth application in the Supabase dashboard 2. Use th
- 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 are enabled (entitlement: "allowed") or disabled ("disallowed") - Audit current network security configuration - Check if network restrictions have been modified (old_config prese
- 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 application traffic is redirected from the replica to the primary database. Requirements: - Project must be on Pro plan or higher - Bearer token with infra_read_replicas_write permission
- 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 or generate_type_script_types tool to retrieve the table schema, then base your query on it.
- 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 available in the chosen channel.
- 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.
…and 20 more Supabase actions available in the workspace.
Give an agent access to Supabase
An agent you create can use Supabase on your behalf and keep working while you do something else. Every action an agent takes goes through an approval gate first, so nothing touches your Supabase account without you agreeing to it.
Other connectors
Frequently asked questions
How do I connect Supabase to Xenition?
Open the connectors directory in Xenition, find Supabase, and sign in when the authorisation window opens. The connection is managed for you — there is no API key to create, paste or rotate.
What can Xenition do with Supabase?
Xenition can run 50 different Supabase actions, including Create project api key, Delete an API key from the project, Delete third party auth config. You ask in plain language and the right one is called for you.
Can an agent use Supabase on my behalf?
Yes. Agents can use Supabase while you do something else, and every action passes through an approval gate before it runs.
Is there a free plan?
Yes. Xenition starts free with 25,000 credits a month and no credit card, and all connectors are available on every plan.