# Connect Noloco to Supabase When **Record Created** fires in [Noloco](https://apiant.ai/connections/noloco), your agent runs **Alpha Creates A New Api Key For The Project** in [Supabase](https://apiant.ai/connections/supabase). Describe the whole flow and it is built, tested on every scenario and kept running. Noloco **2** triggers Noloco **4** actions Supabase **63** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Noloco and Supabase to do together? Give your AI client this address. `https://mcp.apiant.ai` 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 Noloco can start in Supabase - When **Record Created** in Noloco then **Alpha Creates A New Api Key For The Project** in Supabase - When **Record Updated** in Noloco 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 Noloco and Supabase ## Triggers and actions 2 triggers · 67 actions - Trigger **Record Created** Triggers when a new record is created in your app. - Trigger **Record Updated** Triggers when an existing record is updated in your app. - Action **Create a New Record** Creates a new record in a collection. - Action **Delete a Record** Deletes an existing record from a collection. - Action **Search for a Record** Search for an existing record by unique fields. - Action **Update a Record** Updates a existing record in a collection. - 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 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 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 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 **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 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 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 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 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 **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 **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 **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 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 **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 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 Database Branch Config** Retrieves the read-only configuration and status for a supabase database branch, typically for monitoring or verifying its settings. - 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 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 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 **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 Table Schemas** Retrieves column details, types, and constraints for multiple database tables to help debug schema issues and write accurate sql queries. - 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 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 **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 **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 **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 **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 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 **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. ## Each app on its own - [ **Noloco** Noloco is a no-code app platform that gives you the power to build the tools your business needs, with...](https://apiant.ai/connections/noloco) - [ **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 Noloco - [ **Noloco to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/noloco-to-salesforce) - [ **Noloco to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/noloco-to-slack) - [ **Noloco to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/noloco-to-stripe) - [ **Noloco to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/noloco-to-shopify) - [ **Noloco to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/noloco-to-quickbooks-online) - [ **Noloco to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/noloco-to-pipedrive) ## 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 ## Noloco and Supabase, answered ### ### What can start an automation from Noloco? Any of Noloco's 2 triggers in the catalog, including Record Created and Record Updated. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Supabase when something happens in Noloco? Any of Supabase's 63 actions, including Create A Database Branch, Create A Function, Update A Function and Update Database Branch Config. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Supabase to Noloco? Supabase has no triggers in the catalog today, so automations start in Noloco. 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 Noloco 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. ### ### 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.