--- title: "Connect Mindbody to Supabase - APIANT.ai" description: "When \"Class updated\" fires in Mindbody, your agent runs \"Create Project Signing Key\" in Supabase." canonical: "https://apiant.ai/connect/mindbody-to-supabase" --- # Connect Mindbody to Supabase When **Class updated** fires in [Mindbody](https://apiant.ai/connections/mindbody), 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. Mindbody **57** triggers Mindbody **122** actions Supabase **138** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. [ Mindbody Partner Award winner: Most Valuable Partner (opens the announcement in a new tab)](https://www.mindbodyonline.com/company/press/mindbody-announces-third-annual-bold-partner-award-winners) ## What do you want Mindbody 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 Mindbody can start in Supabase - When **Class updated** in Mindbody then **Create Project Signing Key** in Supabase - When **Completed appointment** in Mindbody 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 Mindbody and Supabase ## Triggers and actions 57 triggers · 260 actions - Trigger **Cancelled appointment booking** Triggered when an appointment booking is cancelled - Trigger **Cancelled class booking** Fires when a client's class booking is cancelled. - Trigger **Cancelled class schedule** Triggered when a class schedule is cancelled. When this occurs, all of the classes associated with the schedule are removed. - Trigger **Cancelled client contract** Triggered when a client's contract is cancelled - Trigger **Cancelled membership** Triggered when a membership is cancelled - Trigger **Class updated** Triggered when a single class is updated. - Trigger **Completed appointment** Triggered when an appointment is completed. - Trigger **Deactivated client** Triggered when a client is deactivated - Trigger **Deactivated location** Triggered when a location is deactivated - Trigger **Every appointment in date range** This is not a standard trigger! Always emits every appointment in the configured date range. - Trigger **Every class in date range** This is not a standard trigger! Always emits classes in the configured date range. - Trigger **Every uncanceled class in date range** This is not a standard trigger! Always emits uncanceled classes in the configured date range. - Trigger **Merged clients** Triggered when clients are merged - Trigger **New appointment booking** Triggered when an appointment booking is created - Trigger **New class booking** Triggered when a new booking is made for a class - Trigger **New class (integration setting)** Triggered when a class is created in the amount of time specified by an integration setting stored in a lookup table. The default is 24 hours. - Trigger **New class schedule** Triggered when a new class offering is scheduled - Trigger **New client** Triggered when a new client is added - Trigger **New client contract** Triggered when a new contract is sold to a client - Trigger **New completed class** Triggered when a class completes - Trigger **New completed class (integration setting)** Triggered when a class completes within a number of hours specified by an integration setting. - Trigger **New location** Triggered when a location is created - Trigger **New membership** Triggered when a new membership is created - Trigger **New or updated appointment -7d +30d for any connection** Triggered for new or updated appointments in the last 7 days or 30 days in the future, for any connected account. - Trigger **New or updated appointment in date range** Triggered for new or updated appointments in the specified date range. - Trigger **New or updated class** Triggered for new or updated classes in the configured date range. - Trigger **New or updated class (integration setting)** Triggered when a class is created or updated in the amount of time specified by an integration setting stored in a lookup table. The default is 24 hours. Updates are only triggered when the class name, staff id, resource id, or cancelled status are modified. - Trigger **New or updated client** Triggered when a client is added or updated - Trigger **New or updated client (integration setting)** Triggered when a client is added or modified. Will include inactive clients if specified by an integration setting. By default inactive clients are not included. NOTE: this trigger will only work when less than 200 clients are added/updated per day. - Trigger **New or updated gift card** Triggered when a gift card is created or updated - Trigger **New or updated package** Triggered when a package is created or updated - Trigger **New or updated product** Triggered when a product is created or updated - Trigger **New or updated product (integration setting)** Triggered when a product is created or updated. An integration setting is used to control the fetching of products only sold online. - Trigger **New or updated products inventory** Triggered when inventory changes for a product, or when products are added. - Trigger **New or updated service** Triggered when a service is created or updated - Trigger **New or updated session type** Triggered when session types are created or updated - Trigger **New or updated staff member** Triggered when staff member is created or updated - Trigger **New sale** Triggered when a new sale is made to a client. - Trigger **New sale for any connected account** Triggered when a new sale is made to a client for any connected MINDBODY account. - Trigger **New sale itemized payment** Triggered when a new sale is made to a client. Payments emitted as separate rows. NOTE: line items are not emitted, use the separate trigger to obtain them. - Trigger **New sale line item** Triggered when a new sale is made to a client. Line items are emitted as separate rows. NOTE: payments are not emitted, use the separate trigger to obtain them. - Trigger **New sales since days** Triggers for new sales that occur within the configured number of days - Trigger **Two-way sync new or updated clients** A polling trigger for two-way syncing new and updated clients, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping. - Trigger **Two-way sync new or updated clients (instant)** A trigger for two-way syncing new and updated clients, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping. - Trigger **Upcoming appointment in database** Triggered when an appointment in the database is scheduled to start within the account's "Email_notification_timing_hrs" setting. - Trigger **Upcoming appointment in database via setting** Triggered when an appointment in the database is scheduled to start within the specified "notification timing hours" setting. - Trigger **Upcoming class** Triggered when an uncanceled class is upcoming in the specified amount of time. - Trigger **Upcoming class in database** Triggered when a class in the database is scheduled to start within the account's "Email_notification_timing_hrs" setting. - Trigger **Upcoming class in database via entered time** Triggered when a class in the database is scheduled to start within the entered amount of time. - Trigger **Upcoming class (Zoom meeting creation)** Triggered when an uncanceled class is upcoming in the amount of time specified by a setting stored in a lookup table. The default is 24 hours. - Trigger **Updated appointment booking** Triggered when an appointment booking is updated - Trigger **Updated class booking** Triggered when a booking for a class is updated - Trigger **Updated class booking with service ID** Triggered when a booking for a class is updated - Trigger **Updated class schedule** Triggered when a scheduled class offering is modified. Note that if the class schedule’s endDate changes, classes are added or removed from the schedule accordingly. - Trigger **Updated client** Triggered when a client is updated - Trigger **Updated client contract** Triggered when a client's contract is updated - Trigger **Updated location** Triggered when a location is updated - Action **Add account credit to client** Adds credit to a client's account balance, recorded as a sale at the chosen location. - Action **Add appointment** Adds a new appointment - Action **Add client relationship** Adds a client relationship. Existing relationships are not removed. NOTE: custom relationships are not currently supported due to limitations with the MINDBODY API. - Action **Add client to enrollment** Enrolls a client in a class schedule and returns the enrollment details including start and end dates. - Action **Add client with on-the-fly custom field id lookup** Adds a client. Makes an additional API call to fetch client custom fields in order to determine custom field ids via matching names of custom fields. An error will occur if the client already exists or if a custom field does not exist. - Action **Add completed sale to client** Adds a completed sale to a client using a custom payment method. - Action **Add contact log** Creates a new contact log. - Action **Add or update client** Adds or updates a client based on the selected matching logic. - Action **Add or update client index** Adds or updates a client index. Existing indexes on the client are not removed. - Action **Add site client index** Adds a site client index. An error will occur if the index name already exists. - Action **Add staff** Adds a staff member - Action **Book client into a class** Books the specified client into the specified class. - Action **Calculate total spend for client** Returns the total amount of money received for the specified client, going back for the specified number of days. - Action **Cancel a class** Cancels a single scheduled class at the studio. The MINDBODY login used for the connection needs the Manage Class Schedules and Cancel Reservations permissions. - Action **Cancel Appointment** Cancels a MINDBODY appointment as a standard cancellation, never a late cancel, so no late-cancel fee is charged. It can optionally email the client. Runs as a dry run unless Test is set to false. - Action **Client purchases: fetch** Fetches client purchases that meet the search criteria from the MBO API. The API response is stored in the database. This action emits a transaction uuid and an array of records IDs. Use a loop and the "client purchases: get record" action to process all the fetched records. - Action **Client purchases: get record** Emits the client purchase record from the database that was previously fetched using the "Client purchases: fetch" action, which must be executed before this action is used in a loop to process all records. - Action **Deactivate Client** Marks a Mindbody client as inactive. The client record is kept and can be made active again with Reactivate Client. - Action **Find clients by email** Returns up to 100 clients that have the specified email address. - Action **Find clients by phone** Returns up to 100 clients that have the specified phone number. Can either be Mobile phone, Home phone or Work phone. - Action **Find contact log type by name** Returns the ID of the specified contact log type. An error occurs if zero or multiple are found. - Action **Find sales** Searches Mindbody sales and returns the matching sale records. Filter by sale date range, sale id, client id or payment method, and page through results with Limit and Offset. Use "Get sale" to retrieve a single sale by its id. - Action **Get accrual sales within date range** Emits accrual sales data over a given date range. - Action **Get activation code** Generates an activation code and link to access a Mindbody Site API. - Action **Get Active Memberships for Clients** Look up the current memberships for up to 200 Mindbody clients at once, returning each client's ID and the names of their active memberships. - Action **Get Active Session Times** Get the bookable appointment start times for one or more session types in a date range. - Action **Get all client contract IDs** Returns all contract IDs for the specified client. Use a Loop and the "get client contract by ID" action to fetch details for each contract. - Action **Get all products** Returns all products - Action **Get all products inventory** Returns inventory information for all products at all locations. - Action **Get all sellable online products** Returns all products only sold online. - Action **Get all services** Retrieves all services. - Action **Get all session types** Returns all session types - Action **Get all staff members** Returns all staff members - Action **Get appointment** Returns details for the specified appointment. If the appointment is not found an error occurs. - Action **Get bookable availabilities** Probe build: lists MBO session types to discover a valid appointment SessionTypeId before finalizing the bookable-availabilities query. - Action **Get cash sales within date range** Emits sales data over a given date range. Will return all sales, including products, account credits, gift cards, and autopays. Autopays will be notated in the response, and the product description will specify gift card and account credit purchases. - Action **Get class** Returns details for the specified class. If the class is not found no error will occur, so a conditional must be used for error checking. - Action **Get class description** Returns the class description for the specified ClassDescriptionId. Includes name, category, subcategory, program, and session type details. If not found, no error occurs — output is empty. - Action **Get classes** Returns scheduled classes for the site within an optional date range. - Action **Get class recently updated** Returns classes last modified on or after system time minus the entered amount of hours. No error will occur if no class is found. - Action **Get class schedules** Returns available class schedule templates, optionally filtered by date, location, staff, or program. - Action **Get class visits** Fetches the ids of all clients booked for the specified class. The output is suitable to use within a loop. - Action **Get client** Returns details for the specified client. If the client is not found an error will occur. - Action **Get client account balance** Returns account balance details for the specified client. If the client is not found no error will occur, so a conditional must be used for error checking. - Action **Get client appointments in date range** Returns details for all of the specified client's appointments in the specified date range. - Action **Get client complete info** Returns complete client information along with list of purchased services, contract details, membership details and arrival programs for a specific client. If the client is not found an error will occur. - Action **Get client contact logs in date range** Returns details for all of the specified client's contact logs in the specified date range. - Action **Get client contract** Returns details for the specified client contract. If the client contract is not found an error will occur. - Action **Get Client Membership** Returns details for one of a client's active memberships, selected by Membership ID. If no active membership matches that ID, the output fields come back empty. - Action **Get client purchased service by ID** Returns details for the specified service purchased by a specified client. No error occurs if none is found. - Action **Get client purchased services** Returns details for services purchased by a specified client. No error occurs if the client is not found. - Action **Get clients** Returns clients for the site, optionally filtered by a search term. - Action **Get client services totals by product ID** Returns details for services purchased by a specified client for a specified product ID. If more than 1 matching client service is found, 'Count' and 'Remaining' are totaled and the furthest expiration date is used. No error occurs if none are found, the output is empty instead. - Action **Get client visits** Returns details for client visits in the specified date range. - Action **Get contact log types** Returns all defined contact log types. NOTE: currently returns no more than 200, which should be more than enough for most sites. - Action **Get contract** Returns details for the specified contract. If the contract is not found an error will occur. - Action **Get custom payment method by name** Returns the ID of the custom payment method having the specified name. An error occurs if zero or multiple are found. - Action **Get enrollments** Returns enrollments for clients within a specified date range. - Action **Get gift card balance** Returns the remaining balance for the specified gift card. NOTE: no error occurs if the barcode ID is invalid. - Action **Get gift cards** Returns up to 200 gift cards. - Action **Get locations** Returns details for up to 200 locations. NOTE: currently only supports up to 200 locations, does not currently do pagination. - Action **Get membership** Returns details for the specified membership. If the membership is not found an error will occur. - Action **Get most recent client contract** Returns details for the most recent contract for the specified client. An error occurs no contract is not found. - Action **Get packages** Returns packages available for sale, optionally filtered to those sellable online. - Action **Get product** Returns details for the specified product. If the product is not found an error will occur. - Action **Get product filtered by sellable online** Returns details for the specified product, filtered by it being sellable online or not. If the product is not found an error will occur. - Action **Get product inventory** Returns inventory information for the specified product at all locations. - Action **Get program** Returns details for the specified program. If the program is not found an error will occur. - Action **Get required client fields** Returns the site's required client fields (e.g. Birthday, Gender). - Action **Get sale** Returns details for the specified sale. If the sale is not found an error will occur. - Action **Get sales in date range** Lists MINDBODY sales in a date range. Filters by StartSaleDateTime/EndSaleDateTime, optional PaymentMethodId, Limit/Offset pagination. Returns Sales[], SaleIds (Id), ClientIds (ClientId), TotalResults. - Action **Get scheduled client visits** Returns details for all of the specified client's scheduled visits, optionally in a specified date range. - Action **Get service** Returns details for the specified service. If the service is not found an error will occur. - Action **Get session type** Returns details for the specified session type. If the session type is not found an error will occur. - Action **Get site** Returns details for the site associated with the configured connection - Action **Get site for specified account** Returns details for the site connected to the specified account name. - Action **Get staff member** Returns details for the specified staff member. If the staff member is not found an error will occur. - Action **Get visits within date range** Emits all visits that occur in the specified date range, optionally filtered by a session type id and/or a location id. - Action **Get visits within date range for multiple session types** Emits all visits that occur in the specified date range, filtered by multiple session type ids and optionally a location id. - Action **List all clients** Returns every client on your MINDBODY site, across all pages, optionally including inactive clients. - Action **List Client Indexes** Lists the site's client indexes with their IDs, names and active values. - Action **List Client Memberships** Returns details for all of the specified client's memberships. - Action **List Custom Payment Methods** Returns every custom payment method set up for the Mindbody site, with each method's id and name. - Action **List Resources** List the rooms and resources available for given session types and a location in a date range. - Action **List Staff Appointments** Lists a staff member's appointments between a start and end date, with each appointment's time, status, session type and client. - Action **List Staff Unavailabilities** Lists the time blocks when staff members are unavailable for appointments within a date range, optionally filtered to specific staff. - Action **Lookup client payment** Returns payment information for the specified client and specified payment reference. - Action **Purchase contract** Purchases a contract - Action **Purchase gift card** Purchases a gift card - Action **Reactivate Client** Reactivates a deactivated Mindbody client by ID so they can book and buy again. - Action **Remove client from a class** Removes the specified client from the specified class. - Action **Return sale** Return a comped sale for a specified sale ID in business mode. The sale is returnable only if it is a sale of a service, product or gift card and it has not been used. Currently, only the comp payment method is supported. - Action **Select upcoming class** A utility action that lets an upcoming class in the specified timeframe to be selected from a dropdown. The selected class' id is emitted as output. - Action **Send password reset email** Sends a password reset email to the specified user. - Action **Shopping cart - add item: package** Adds a package to the shopping cart. - Action **Shopping cart - add item: product** Adds a product to the shopping cart. - Action **Shopping cart - add item: service** Adds a service to the shopping cart. - Action **Shopping cart - add item: tip** Adds a tip to the shopping cart. - Action **Shopping cart - add payment: cash** Adds a cash payment to the shopping cart. - Action **Shopping cart - add payment: check** Adds a check payment to the shopping cart. - Action **Shopping cart - add payment: comp** Adds a complimentary amount to the shopping cart. - Action **Shopping cart - add payment: custom** Adds a payment to the shopping cart using the specified custom payment method. - Action **Shopping cart - add payment: gift card** Adds a gift card payment to the shopping cart. - Action **Shopping cart - add payment: stored credit card** Adds a stored credit card payment to the shopping cart. - Action **Shopping cart - checkout** Submits the shopping cart for checkout. - Action **Shopping cart - create** Initializes a new shopping cart. Emits a cart ID that must be passed into other shopping cart actions to add items to the cart and checkout. - Action **Shopping cart - delete** Deletes the specified cart from the database. - Action **Shopping cart - get totals** Calculates the total amount of the cart. - Action **Terminate Client Contract** Ends a client's contract in MINDBODY on a set termination date, with an optional termination code and comments. - Action **Two-way sync add or update a client** An action for two-way syncing new and updated clients, with enhanced on-the-fly mapping using client email addresses for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping. - Action **Update appointment** Updates an existing appointment - Action **Update client** Updates a client by ID. - Action **Update client id** Updates an existing client's id. An error occurs if the id cannot be changed, for example if it already exists. - Action **Update Client Service Dates** Changes the expiration date, and optionally the active date, of a pricing option (pass, membership or class pack) on a client's account. - Action **Update client visit** Updates a client visit. - Action **Update client with on-the-fly custom field id lookup** Updates a client by ID. Makes an additional API call to fetch client custom fields in order to determine custom field ids via matching names of custom fields. An error will occur if a custom field does not exist. - Action **Update product price** Updates the price of the specified product. - Action **Update sale date** Updates the date of the specified sale. - Action **Update service price** Updates the price of the specified service. - Action **Update staff** Updates an existing staff member - Action **Upload client document** Uploads a client document from the provided URL. NOTE: the file must be no larger than 4MB - Action **Upload client profile photo** Uploads a client's profile photo from the provided URL. NOTE: the image file must be no larger than 4MB - 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 - [ **Mindbody** MINDBODY is a powerful business management software that combines your scheduling, task automation...](https://apiant.ai/connections/mindbody) - [ **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 Mindbody - [ **Mindbody to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/mindbody-to-salesforce) - [ **Mindbody to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/mindbody-to-google-calendar) - [ **Mindbody to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/mindbody-to-quickbooks-online) - [ **Mindbody to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/mindbody-to-trello) - [ **Mindbody to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/mindbody-to-zoom) - [ **Mindbody to PandaDoc** PandaDoc helps you build and deliver sales quotes and proposals and track presentations and close deals...](https://apiant.ai/connect/mindbody-to-pandadoc) ## 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 ## Mindbody and Supabase, answered ### ### What can start an automation from Mindbody? Any of Mindbody's 57 triggers in the catalog, including Class updated, Completed appointment, New appointment booking and New class booking. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Supabase when something happens in Mindbody? 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 Mindbody? Supabase has no triggers in the catalog today, so automations start in Mindbody. 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 Mindbody 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 Mindbody 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.