Integration
Connect Privy to Supabase
When New Contact fires in Privy, your agent runs Create Project Signing Key in Supabase. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Privy and Supabase to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)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)Example flows
What Privy can start in Supabase
When New Contact in Privy
then Create Project Signing Key in Supabase
When New Order in Privy
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 Privy and Supabase
Triggers and actions 2 triggers · 169 actions
Trigger
New ContactTriggers when a new contact is added to your Privy account.
Trigger
New OrderTriggers when a new order is recorded in your Privy account.
Action
Check Coupon CodeCheck a coupon code. Check whether an individual code from a Shopify or BigCommerce pool has been redeemed, read live from the connected store's per-code usage counter (Privy stores no redemption events).
Action
Delete ContactDelete a contact by ID. Soft-delete a contact identified by its unique `id`.
Action
Find ContactList contacts. Retrieve a paginated list of contacts, most recently created first. Optionally filter by email, phone number, or consent status.
Action
Get AccountGet account. Retrieve information about the Privy account associated with the API token.
Action
Get CouponGet a coupon. Retrieve a single coupon pool by its identifier — the list rows' inventory and health, plus `usage_count`, the connected store's pool-wide redemption counter read live.
Action
Get Display ReportGet display performance. The full performance stat set for one display over a period, including average order value and, when the display has run an A/B test, per-variation participants, conversions, and conversion rates.
Action
Get FlowGet a flow. Retrieve a single flow by its identifier, including its full configuration: re-entry behavior, flow filters, effective exit behavior, a server-generated behavior summary, and the node tree — each step's configuration (`data`) plus the branch graph, with split conditions and the nodes on each branch.
Action
Get ImportGet a contact import. Retrieve a single contact import — the same row `/v1/imports` lists for it.
Action
Get ProductGet a product. Retrieve a single product from your connected store's catalog by its store product id.
Action
Get Product CollectionGet a product collection. Retrieve one collection (Shopify) or category (BigCommerce) of your connected store by its store id, the `id` a `purchase_history` segment condition's `collection` filter holds.
Action
Get SegmentGet a segment. Retrieve a single segment by its identifier. The members themselves are `/v1/segments/{id}/contacts`. A campaign's `audience` segment ids resolve here when the segment was saved to the account. There is no per-segment performance report anywhere in the API.
Action
Get Segment CountsReturns how many contacts a segment reaches today: total, mailable and textable counts.
Action
Get TagGet a tag. Retrieve a single tag by its prefixed id — the same row `/v1/tags` lists for it. This is how to name the `tag_…` and `stag_…` ids that appear in a flow's condition tree.
Action
List Campaign ReportsList campaign performance. Every message campaign **sent in the period**, ranked by attributed revenue, each row carrying the full channel stat block (delivery, engagement, unsubscribes, attribution) scoped to the same period — so period comparisons need no per-campaign detail calls. Zero-revenue sends are listed too, ranked after the revenue rows; at most 100 campaigns are ranked, and a send with
Action
List CampaignsList campaigns. Retrieve a paginated list of your message campaigns, newest first.
Action
List Collection ProductsList a collection's products. Retrieve the products in one collection (Shopify) or category (BigCommerce) of your connected store, in the same shape as `/v1/products`.
Action
List Contact ActivityList a contact's activity. Retrieve the contact's activity timeline — signups, email and SMS sends, opens and clicks, orders, checkouts, tag changes — newest first. This is the same record the Privy dashboard's contact page shows, so "why did this contact get X?" can be answered from the API alone: find the send, the signup that triggered it, and the display or campaign each traces to.
Action
List CouponsList coupons. Retrieve a paginated list of your coupon pools with their code inventory and health status.
Action
List Display ReportsList display performance. Rank your displays by performance over a period — signups by default, or any of the documented sort keys. Displays whose value for the chosen sort key is zero are left out entirely, and ranking stops at 50 displays, which also caps the reported `total_count`. Use `/v1/reports/displays/{display_id}` for one display's full stat set, including average order value and A/B tes
Action
List DisplaysList displays. Retrieve a paginated list of your on-site displays, newest first. Archived displays are excluded by default — pass `status=archived` to list them.
Action
List Email TemplatesList email templates. The templates an email draft may start from: the account's own saved newsletter templates, listed first, and then Privy's gallery. Names and facets only; the design and HTML stay on the server, and a template is branded for the account only when a draft uses it. Templates with product blocks are offered only to an account with a connected catalog store. Templates whose produc
Action
List Flow ReportsList flow performance. Rank your flows by performance over a period — best performers first, remaining flows by recency. Each row combines email and SMS stats across the flow's message steps. Use `/v1/reports/flows/{flow_id}` for one flow's report including the per-node message breakdown.
Action
List FlowsList flows. Retrieve a paginated list of your automation flows, including each flow's trigger and steps.
Action
List ImportsList contact imports. Retrieve a paginated list of your contact imports — CSV uploads and connected-provider syncs — most recently requested first. Each row mirrors the dashboard's import history: type, processing status, contact counts, who requested it, when, and its review status.
Action
List OrdersList orders. Retrieve a paginated list of your orders across every source (Shopify, BigCommerce, Weebly, Wix, and orders reported via this API), most recently created first.
Action
List Product CollectionsList product collections. Retrieve the collections of your connected store, proxied live from the store's API: Shopify collections, or BigCommerce categories.
Action
List Product Collections For ProductList a product's collections. Retrieve the collections (Shopify) or categories (BigCommerce) one product of your connected store belongs to, by its store product id.
Action
List ProductsList products. Retrieve the product catalog of your connected store (Shopify or BigCommerce), proxied live from the store's API.
Action
List Segment ContactsList a segment's contacts. Retrieve the segment's members as a paginated list of contacts, in the same shape as the Contacts API, most recently created first.
Action
List SegmentsList segments. Retrieve a paginated list of your customer segments with their mailable/textable member counts.
Action
List TagsList tags. Retrieve a paginated list of the account's contact tags, ordered by name. Tag names are lower-cased and trimmed. Some older tags have not been merged yet, so the same name can appear on more than one row, each with its own id.
Action
List Top Products ReportList top products. Retrieve your store's top products ranked by views or sales over a 30, 60, or 90 day window, or all-time where the platform supports it.
Action
Alpha Create Api KeyCreates 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 ProjectCreates 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 KeyPermanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.
Action
Alpha Delete Third Party Auth IntegrationRemoves 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 IntegrationRetrieves 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 IntegrationsLists 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 IntegrationsLists 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 IntegrationRemoves 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 KeyUpdates 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 ProjectUpdates 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 MigrationTool 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 ProjectActivates a vanity subdomain for the specified supabase project, requiring subsequent dns configuration for the subdomain to become operational.
Action
Beta Activate Vanity SubdomainActivates 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 AvailabilityChecks 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 AvailabilityChecks if a specific vanity subdomain is available for a Supabase project; this action does not reserve or assign the subdomain.
Action
Beta Get Project Network BansRetrieves 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 RestrictionsRetrieves 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 ConfigRetrieves the PGSodium configuration, including the root encryption key, for an existing Supabase project identified by its `ref`.
Action
Beta Get Project Ssl Enforcement ConfigRetrieves 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 ConfigurationRetrieves the ssl enforcement configuration for a specified supabase project, indicating if ssl connections are mandated for its database.
Action
Beta Gets Current Vanity Subdomain ConfigFetches 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 BansRetrieves 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 RestrictionsRetrieves 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 ConfigRetrieves the pgsodium configuration, including the root encryption key, for an existing supabase project identified by its `ref`.
Action
Beta Get Vanity Subdomain ConfigFetches 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 BansRemoves specified ipv4 addresses from a supabase project's network ban list, granting immediate access; ips not currently banned are ignored.
Action
Beta Run Sql QueryExecutes 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 RestrictionsUpdates 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 RestrictionsUpdates 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 WarningCritically 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 RunsCounts 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 BranchCreates 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 FunctionCreates 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 SecretsTool 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 RoleCreates 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 KeyCreate 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 ProviderCreates 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 IntegrationCall 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 UrlCreate 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 ProviderCreates 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 IntegrationCall 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 BranchPermanently and irreversibly deletes a specific, non-default database branch by its `branch id`, without affecting other branches.
Action
Delete A FunctionPermanently 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 FunctionDeletes 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 SubdomainPermanently and irreversibly deletes an active vanity subdomain configuration for the specified supabase project, reverting it to its default supabase url.
Action
Delete Sso ProviderDeletes 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 FunctionDeploys edge functions to a supabase project using multipart upload.
Action
Disable Project ReadonlyTemporarily 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 BranchingDisables the preview branching feature for an existing supabase project, identified by its unique reference id (`ref`).
Action
Generate Typescript TypesGenerates 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 TypesGenerates and retrieves typescript types from a supabase project's database; any schemas specified in `included schemas` must exist in the project.
Action
Get Auth ConfigRetrieves 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 RegionsTool 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 BranchRetrieves 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 ConfigRetrieves the read-only configuration and status for a supabase database branch, typically for monitoring or verifying its settings.
Action
Get Database MetadataGets 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 FunctionRetrieves detailed information, metadata, configuration, and status for a specific Edge Function using its project reference ID and function slug.
Action
Get Function BodyRetrieves 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 KeyRetrieves 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 MigrationRetrieves 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 OrganizationFetches comprehensive details for a specific Supabase organization using its unique slug.
Action
Get Performance AdvisorsRetrieves 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 ProjectRetrieves 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 KeyRetrieves 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 KeysRetrieves 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 KeysChecks 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 LogsRetrieves 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 MetricsRetrieve a Supabase project's Prometheus/OpenMetrics exposition.
Action
Get Project Postgres ConfigRetrieves 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 ConfigRetrieves the PostgREST configuration for a specific Supabase project.
Action
Get Project Readonly Mode StatusRetrieves 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 KeysTool 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 ConfigRetrieves 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 ConfigRetrieves the Supavisor (connection pooler) configuration for a specified Supabase project, identified by its reference ID.
Action
Get Project Upgrade EligibilityChecks 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 StatusRetrieves the latest status of a supabase project's database upgrade for monitoring purposes; does not initiate or modify upgrades.
Action
Gets A Specific Sql SnippetRetrieves a specific sql snippet by its unique identifier.
Action
Gets A Sso Provider By Its UuidRetrieves 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 AdvisorsRetrieves 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 OrganizationFetches comprehensive details for a specific supabase organization using its unique slug.
Action
Gets Project S Auth ConfigRetrieves 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 ConfigRetrieves 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 ConfigRetrieves the postgrest configuration for a specific supabase project.
Action
Gets Project S Service Health StatusRetrieves 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 ConfigRetrieves the supavisor (connection pooler) configuration for a specified supabase project, identified by its reference id.
Action
Get Sql SnippetRetrieves a specific SQL snippet by its unique identifier.
Action
Get Sso ProviderRetrieves 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 SchemasRetrieves column details, types, and constraints for multiple database tables to help debug schema issues and write accurate sql queries.
Action
Invoke Database FunctionInvoke 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 FunctionTool 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 BranchesLists 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 FunctionsLists metadata for all edge functions in a supabase project (specified by 'ref'), excluding function code or logs; the project must exist.
Action
List All OrganizationsLists all organizations (id and name only) associated with the supabase account, excluding project details within these organizations.
Action
List All ProjectsRetrieves a list of all supabase projects, including their id, name, region, and status, for the authenticated user.
Action
List All SecretsRetrieves all secrets for a supabase project using its reference id; secret values in the response may be masked.
Action
List BackupsLists 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 BranchesLists 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 BucketsRetrieves a list of all storage buckets for a Supabase project, without returning bucket contents or access policies.
Action
List Database BranchesLists 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 FunctionsLists 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 OrganizationRetrieves all members of a supabase organization, identified by its unique slug, including their user id, username, email, role, and mfa status.
Action
List Migration HistoryRetrieves 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 SecretsRetrieves 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 BackupsLists 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 BucketsRetrieves a list of all storage buckets for a supabase project, without returning bucket contents or access policies.
Action
Lists All Sso ProvidersLists all configured single sign-on (sso) providers for a supabase project, requiring the project reference id (`ref`) of an existing project.
Action
List SecretsRetrieves all secrets for a Supabase project using its reference ID; secret values in the response may be masked.
Action
List Sso ProvidersLists 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 UserRetrieves a list of sql snippets for the logged-in user, optionally filtered by a specific supabase project if `project ref` is provided.
Action
List TablesLists 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 BranchMerges 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 RestrictionsUpdates 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 BranchPushes 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 UuidDeletes 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 BranchResets 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 FunctionRetrieves detailed information, metadata, configuration, and status for a specific edge function using its project reference id and function slug.
Action
Retrieve A Function BodyRetrieves 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 StatusRetrieves 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 TableTool to select rows from a Supabase/PostgREST table. Use for read-only queries with filtering, sorting, and pagination.
Action
Update A FunctionUpdates 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 KeyUpdates 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 ConfigUpdates the configuration of a supabase database branch, allowing modification of its name, associated git branch, reset-on-push behavior, persistence, and status.
Action
Update ProjectUpdates a Supabase project's configuration (currently supports updating the project name). Use when you need to rename an existing project.
Action
Update Project Auth ConfigUpdate 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 ConfigUpdates 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 ConfigUpdates 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 ConfigUpdates 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 UuidUpdates 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 ConfigUpdates 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 ConfigUpdates 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 ConfigUpdates 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 ConfigUpdates the ssl enforcement configuration (enable/disable) for a specified supabase project's database.
Action
Update Sso ProviderUpdates 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 MigrationTool 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.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Privy
Privy to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Privy to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Privy to StripeStripe is a payment processing platform for online businesses.
Privy to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Privy to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Privy to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Supabase
Airtable to SupabaseOrganize anything with Airtable, a modern database created for everyone.
Benetics to SupabaseBenetics is a construction efficiency platform built in the cloud.
Erpnext to SupabaseOpen-source ERP system for accounting, inventory, manufacturing, sales, projects, and CRM.
Form Io to SupabaseForm-builder platform that auto-generates REST APIs for form submissions, data validation, and workflow...
ONLYOFFICE DocSpace to SupabaseONLYOFFICE DocSpace is a room-based collaboration environment for organizing teamwork on an any content.
HubSpot to SupabaseHubSpot is your all-in-one stop for all of your marketing software needs.
Questions
Privy and Supabase, answered
What can start an automation from Privy?
Any of Privy's 2 triggers in the catalog, including New Contact and New Order. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Supabase when something happens in Privy?
Any of Supabase's 137 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 Privy?
Supabase has no triggers in the catalog today, so automations start in Privy. 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 Privy 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 Privy 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.