--- title: "Connect Gravity Forms to Supabase - APIANT.ai" description: "When \"Form Submission\" fires in Gravity Forms, your agent runs \"Create Project Signing Key\" in Supabase." canonical: "https://apiant.ai/connect/gravity-forms-to-supabase" --- # Connect Gravity Forms to Supabase When **Form Submission** fires in [Gravity Forms](https://apiant.ai/connections/gravity-forms), 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. Gravity Forms **1** trigger Gravity Forms **30** 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 Gravity Forms 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 Gravity Forms can start in Supabase - When **Form Submission** in Gravity Forms then **Create Project Signing Key** in Supabase - When **Form Submission** in Gravity Forms 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 Gravity Forms and Supabase ## Triggers and actions 1 trigger · 168 actions - Trigger **Form Submission** Triggers when the specified form is submitted. - Action **Add Entry Note** Adds a note to a form entry. Use it to write a progress record back onto a submission — for example noting that the submission was synced to your CRM, who handled it, or why it was skipped — so the note is visible to anyone reviewing that entry in WordPress. - Action **Create Entry** Creates a new form entry. - Action **Create Feed** Attaches a new add-on feed to a form. A feed is one add-on's configuration on a form — the rule that says what should happen when the form is submitted, such as creating a WordPress user, adding the person to a mailing list, or taking a payment. - Action **Create Form** Creates a new form on the WordPress site and returns its id. Supply the form's title and, if you want the form ready to collect data, the fields it should show. - Action **Create Form Feed** Attaches a new add-on feed to a named form. Does the same thing as Create Feed, but takes the form as part of the address rather than in the settings — use whichever reads better in your automation. - Action **Delete Entry** Removes a form entry. By default the entry is moved to the trash and can still be restored from the Entries list; you can choose instead to delete it outright so it cannot be recovered. - Action **Delete Feed** Permanently removes an add-on feed from a form, so that add-on no longer acts on the form's submissions. The form itself and its entries are untouched. - Action **Delete Form** Moves a form to the trash on the WordPress site. The form stops accepting submissions and disappears from the forms list, and the site owner can still restore it or empty the trash in WordPress. - Action **Delete Note** Permanently removes an entry note. Use it to clear a note you logged against a submission, for example after a failed sync was retried successfully. - Action **Get Entry** Retrieve a single form entry, including every field value the person submitted. - Action **Get Feed** Returns one add-on feed by its id, including the add-on's settings. A feed is one add-on's configuration attached to a form — the rule that says what should happen when the form is submitted. - Action **Get Form** Returns one form's full definition, including every field on it, its notifications and its confirmations. Use it to read a form's field ids and labels before mapping data into that form. - Action **Get Form Results** Returns the summarised answers for a survey, quiz or poll form — how many people picked each choice, and how many answered each free-text question — rather than the individual entries. On a form with a lot of entries the summary is built in the background, so the result can come back marked as still being calculated. - Action **Get Note** Returns a single entry note by its id, including the note text, the entry it belongs to, when it was recorded and who it is credited to. - Action **List Entries** Returns form entries from across every form on the site, newest first, and can narrow the results to one form or to entries whose answer to a chosen question matches a value you give. - Action **List Entry Notes** Returns every note attached to one form entry — both notes people have added and the notes Gravity Forms records automatically, such as notification failures. Use it to read back what has already been logged against a submission. - Action **List Feeds** Returns every add-on feed configured on the site. A feed is one add-on's configuration attached to a form — the rule that says what should happen to a submission, such as sending it to a mailing list or charging a payment. - Action **List Form Entries** Returns the entries submitted on one particular form, newest first, and can narrow them to entries whose answer to a chosen question matches a value you give. - Action **List Form Feeds** Returns the add-on feeds attached to one form — the rules that say what happens when that form is submitted. Returns an empty list when the form has no feeds. - Action **List Forms** Returns every active form on the WordPress site, with each form's id, title and entry count. Use it to look up the id a form needs before working with that form's entries. - Action **List Notes** Returns every entry note on the site, across all forms and entries. Use it to sweep recently logged notes when you do not already know which entry you are looking for; to read the notes on one known entry, use List Entry Notes instead. - Action **Send Entry Notifications** Sends the notification emails an entry's form is set up to send, for an entry that already exists — useful for re-sending a confirmation, or for notifying people about an entry that was created through the API rather than by someone filling the form in. - Action **Submit Form** Submit a form the way a visitor would — Gravity Forms runs the form's own validation, saves the entry, and fires its notifications and confirmation. - Action **Update Entry** Change the answers on an existing form entry. Answers you leave blank keep the values they already have. - Action **Update Entry Properties** Changes an entry's housekeeping flags without touching any of its answers — whether it is starred, whether it counts as read, and whether it sits in the active list, the trash or spam. - Action **Update Feed** Changes an existing add-on feed's settings. Settings you do not include are left as they are, so you can change one thing without restating the rest of the add-on's configuration. - Action **Update Feed Properties** Switches an add-on feed on or off, and sets the order it runs in. The add-on's own settings are left completely untouched, so this is the safe way to pause a feed without risking its configuration. - Action **Update Form** Replaces an existing form's definition with the one you supply. Gravity Forms overwrites the whole form, so read the form first with Get Form and send back every part of it you want to keep. - Action **Update Note** Replaces the text of an existing entry note. Use it to revise a note you logged earlier against a submission — for example updating "Sync started" to "Synced to CRM as contact 4821". - Action **Validate Submission** Checks a set of answers against a form's own validation rules without saving an entry or sending any notifications. Returns whether the answers would be accepted, and the per-field error messages when they would not. - 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 - [ **Gravity Forms** Gravity Forms is a premier WordPress plugin that makes it easy to create powerful forms on the fly.](https://apiant.ai/connections/gravity-forms) - [ **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 Gravity Forms - [ **Gravity Forms to Datamuse** Word-finding API for developers offering lexical search, thesaurus, and rhyming/word-relation lookups.](https://apiant.ai/connect/gravity-forms-to-datamuse) - [ **Gravity Forms to Harness.io** Harness.io is an AI-native software delivery platform to automate CI/CD pipelines, manage feature flags, and...](https://apiant.ai/connect/gravity-forms-to-harness-io) - [ **Gravity Forms to Persona** Identity verification API for KYC checks, document verification, and fraud prevention workflows.](https://apiant.ai/connect/gravity-forms-to-persona) - [ **Gravity Forms to XFlux** Read X/Twitter profiles, search, timelines; account monitors with signed webhooks](https://apiant.ai/connect/gravity-forms-to-xflux) - [ **Gravity Forms to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/gravity-forms-to-hubspot) - [ **Gravity Forms to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/gravity-forms-to-salesforce) ## 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 ## Gravity Forms and Supabase, answered ### ### What can start an automation from Gravity Forms? Any of Gravity Forms's 1 trigger in the catalog, including Form Submission. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Supabase when something happens in Gravity Forms? 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 Gravity Forms? Supabase has no triggers in the catalog today, so automations start in Gravity Forms. 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 Gravity Forms 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 Gravity Forms 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.