--- title: "Connect Shopify to Supabase - APIANT.ai" description: "When \"New cart\" fires in Shopify, your agent runs \"Create Project Signing Key\" in Supabase." canonical: "https://apiant.ai/connect/shopify-to-supabase" --- # Connect Shopify to Supabase When **New cart** fires in [Shopify](https://apiant.ai/connections/shopify), 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. Shopify **17** triggers Shopify **78** 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 Shopify 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 Shopify can start in Supabase - When **New cart** in Shopify then **Create Project Signing Key** in Supabase - When **New customer** in Shopify 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 Shopify and Supabase ## Triggers and actions 17 triggers · 216 actions - Trigger **New cart** Triggered when a cart is created. - Trigger **New customer** Polling trigger that fires for each newly created Shopify customer. Fetches the 50 most recently created customers (sorted by creation date, newest first) via the GraphQL Admin API customers connection. - Trigger **New customer (instant)** Triggered when a customer is added. - Trigger **New order** Polls Shopify for orders (most recent first), returning a list of orders. - Trigger **New order (instant)** Triggered when an order is created. - Trigger **New paid order** Triggered when an order is paid. - Trigger **New product** Triggers when a new product is created in Shopify. Polls the GraphQL Admin API products connection (first 50, sorted by createdAt ascending) and returns each product's id, title, handle, vendor, product_type, status, created_at, updated_at. - Trigger **Order fulfilled** Triggered when an order is fulfilled. - Trigger **Order partially fulfilled** Triggered when an order is partially fulfilled. - Trigger **Two-way sync new or updated customers** Polling fetch body for the two-way customer sync trigger. Lists Shopify customers ordered oldest-to-newest by updated_at (GraphQL customers connection, sortKey: UPDATED_AT, reverse:false, first:250) so newly created or updated customers are surfaced for two-way synchronization. - Trigger **Updated cart** Triggered when a cart is updated. - Trigger **Updated customer** Triggered when a customer is updated. - Trigger **Updated fulfillment status** Polling trigger: fetches recently-updated Shopify orders (any status) and returns each order's fulfillment status. - Trigger **Updated order** Polls Shopify for recently updated orders (any status), most-recently-updated first. - Trigger **Updated order (instant)** Triggered when an order is updated. - Trigger **Updated order payment status** Polling trigger: fires when an order's payment (financial) status changes. Lists the 50 most recently updated orders via the GraphQL Admin API (orders sorted by UPDATED_AT desc) and dedups on order id + financial status so a new event fires only when the payment status changes. - Trigger **Updated product** Polling trigger: fires for products that were recently updated. Fetches up to 50 products sorted by update time (most recent first) via the Shopify GraphQL Admin API, projecting id, title, handle, vendor, product_type, status, created_at and updated_at for each. - Action **Activate Inventory Item at Location** Stocks an inventory item at a store location so it can hold quantity there, and returns the location's available quantity. - Action **Add customer** Create a new Shopify customer (first name, last name, email, phone, note, tags) via the GraphQL Admin API customerCreate mutation. Returns the created customer's id, email, phone, first/last name and created_at. - Action **Add metafield to customer** Add (set) a metafield on a Shopify customer, with the customer as the metafield owner. Inputs: Customer ID, Namespace, Key, Type (default single_line_text_field), Value. Returns the created/updated metafield's id, namespace, key, type, value. - Action **Add metafield to product** Adds a metafield to the specified product. - Action **Add or update customer** Creates a new customer if the email does not exist, otherwise updates the existing customer. - Action **Add product image** Adds a new product image from the image at the specified URL. - Action **Add Product Option** Adds one or two new options (for example Size or Color) to an existing product and gives every existing variant a value for them. Does nothing if the product already has an option with that name. - Action **Add tags to customer** Adds one or more tags to the customer with the specified email. An error occurs if more than one customer is found. Existing tags on the customer are not removed. - Action **Add tags to order** Adds the given comma-separated tags to a Shopify order (GraphQL Admin API tagsAdd mutation). Existing order tags are preserved; tagsAdd merges new tags onto the current set. Inputs: Order ID (numeric REST id, converted to a gid://shopify/Order GID), Tags (comma-separated). Returns the order GID (id) and the full resulting tag list (tags). - Action **Add transaction to order** Add a transaction to an order. Captures payment for the order's authorized amount. Inputs: Kind (default capture), Amount, Currency, Parent Transaction ID, plus the Order ID setting. Returns the transaction id, kind, status and order id. - Action **Adjust Inventory Quantity** Change an inventory item's available quantity at a location by a positive or negative amount. - Action **Apply gift card adjustment** Apply an adjustment (credit) to a Shopify gift card's balance. Inputs: Gift Card ID, Amount, optional Note. Returns the resulting credit transaction id, note, amount, creation time, and the gift card's numeric id. - Action **Change product option names** Update a Shopify product's core fields and (re)name its product options. Inputs: Product ID plus optional Title, Body HTML, Handle, Type, Published scope, Tags, Template suffix, Vendor, and Option 1/2/3 name. Returns the updated product id, title, options (name+position), and updated_at. - Action **Change product option names and values** Change a product's option names and their values. Inputs: Product ID, Option 1/2/3 Name, Option 1/2/3 Values (comma-separated). Returns the product id, title, and the resulting options array. - Action **Complete draft order** Completes a draft order. - Action **Create Metafield Definition** Create a metafield definition (namespace, key, type, validations) for an owner type. - Action **Create Order with Calculated Tax** Creates an order for a product variant, with Shopify calculating the tax from the shipping address, and returns the order totals and tax lines. - Action **Create or Update Theme File** Create or replace a file in a theme. The store's Shopify app needs the write_themes scope. - Action **Create product** Creates a new product. - Action **Create product variant** Creates a new variant on an existing Shopify product. Inputs: SKU, Price, Weight, Barcode, Option1-3, Compare At Price, Inventory Quantity, plus the Product ID setting. Returns the created variant id, sku, price, title, option1, product_id and inventory_item_id. - Action **Create Product with Variants** Create a product with up to three options and its variants (price, SKU, barcode, inventory settings) in one step. - Action **Delete item from location** Disconnect (deactivate) an inventory item from a location, removing the inventory level — GraphQL Admin API equivalent of. - Action **Delete product** Deletes an existing product. - Action **Delete product variant** Deletes an existing product variant. - Action **Delete Theme File** Delete a file from a theme. The store's Shopify app needs the write_themes scope. - Action **Find custom collection by name** Returns details for the specified custom collection. If the custom collection is not found, an error occurs. - Action **Find customer by email** Find a Shopify customer by email address. GraphQL Admin API: customers(first:1, query:"email:...") connection query; returns the first matching customer's email and numeric (legacyResourceId) customer_id. - Action **Find location by name** Find a Shopify location by its exact name and return its Location ID. Fails if no location matches or if more than one location shares the name. (GraphQL Admin API port of the REST locations.json lookup.) - Action **Find orders** Finds orders based upon search criteria. Emits the IDs of any matching orders. Use the "get order" action to fetch details for found orders. - Action **Find product by title** Finds a product by a title search. An error occurs if zero or multiple match. - Action **Find product variant by SKU** Find a single Shopify product variant by its SKU. Searches product variants for an exact SKU match, fails if zero or more than one variant matches. Returns the variant's id, sku, price, title, product id, inventory item id, and the full variant object. - Action **Find product variant by title** Finds a product variant by a title search. An error occurs if zero or multiple match. - Action **Get all product ids in custom collection** Returns all products (and their numeric ids) in a given custom collection. - Action **Get Base URL** Returns the connected Shopify store's base URL and derives the store subdomain (store_name) from it. Pure-compute helper; makes no Shopify API call (nothing to migrate to GraphQL). - Action **Get customer** Retrieve a single Shopify customer by Customer ID. Returns the customer's id, email, phone, state, first/last name, tags, created/updated timestamps, total spent, and orders count. - Action **Get customer metafield value** Get a customer's metafield value by namespace and key. Returns its type, value, and numeric metafield id. - Action **Get fulfillment order** Returns details for the specified order ID and fulfillment order ID. If either the order or fulfillment order is not found, an error occurs. Use the "get fulfillment order ids for order" action to fetch the fulfillment order ids for an order. - Action **Get fulfillment order ids for order** Get the fulfillment order IDs for a Shopify order. Given a numeric Order ID, returns the count of fulfillment orders and their IDs. - Action **Get fulfillment order line items** Lists the line items on a fulfillment order, with the quantity still left to fulfill. - Action **Get inventory item** Returns details for the specified inventory item. - Action **Get inventory quantity** Get available inventory quantity for an inventory item, optionally filtered to a single location. - Action **Get locations** Retrieve the list of Shopify store locations. Returns each location's id, legacyResourceId, name, active state, and address. - Action **Get metafields for customer** Get all metafields for a Shopify customer by Customer ID. Returns the list of metafield records (id, namespace, key, value, type) for the customer. - Action **Get metafields for product** Retrieve all metafields for a product (up to 250). Takes the numeric Product ID setting and returns the list of metafields (id, namespace, key, value, type). - Action **Get order** Get an order from Shopify by its numeric Order ID. Reads the order via the GraphQL Admin API (order(id:) query) and returns its name, email, currency, created date, total price, financial status, fulfillment status, and the full order object. - Action **Get product** Returns all fields for the specified product ID. If the product is not found, an error occurs. - Action **Get product count: active products** Returns a count of active products. - Action **Get product count: all products** Returns a count of all products. - Action **Get product count: archived products** Returns the number of archived products in the Shopify store. - Action **Get product count: draft products** Returns the number of draft products in the Shopify store (status:draft). - Action **Get product metafield value** Returns the value of a single product metafield identified by Namespace and Key for the given Product ID. - Action **Get Product Options** Get a product's options and their values. - Action **Get product variant** Get a single Shopify product variant by its numeric Variant ID. Returns id, sku, price, title, inventory_quantity, product_id, inventory_item_id, and the full variant object. - Action **Get product variant by SKU** Look up a single Shopify product variant by its SKU. Searches product variants for the given SKU, fails if zero or more than one match. Returns the matched variant's id, sku, price, title, product id, inventory item id, and the full variant object. - Action **Get Sales Tax Rates by Location** Returns the sales tax lines and total tax rate that apply at each active store location. - Action **Get Theme File** Get a theme file's contents by theme and filename. - Action **Move fulfillment order line item** Changes the location which is assigned to fulfill a number of unfulfilled fulfillment order line items. - Action **Order - add discount code** Append a discount code to an in-progress order object before it is submitted to Shopify. GraphQL-shaped: the discount entry carries DraftOrderAppliedDiscountInput fields (title/code, value, valueType FIXED_AMOUNT|PERCENTAGE, amount) so the assembled order is ready for the draftOrderCreate / draftOrderUpdate GraphQL mutation. Mirrors the REST builder that appended {code, amount, type} to order.discount_codes; same inputs (Code, Type, Amount, Order) and outputs (order, discount_codes). - Action **Order - add line item** Appends a line item to an in-memory order object (built by Order - initialize) before the order is created. Carries the same inputs (Variant ID, Quantity, Price, Total discount, Origin location ID, Is gift card, Fulfillment status). - Action **Order - add line item property** Adds a custom line-item property (name/value pair) to the LAST line item of an in-flight Shopify order object being assembled in the Order builder chain (initialize -> add line item -> add line item property -> create). Pure in-memory mutation of the draft order; no API call. Returns the updated order object and its JSON encoding. (No REST->GraphQL change applies: this op never called the REST Admin API; it is a local order-builder helper. The eventual draftOrderCreate/orderCreate happens in the separate 'Order - create' op.) - Action **Order - add line item tax line** Adds a tax line to the last line item of an in-memory order payload (builder, no API call). This op shapes the legacy order JSON structure; it does not call Shopify. Same inputs/outputs as the REST builder. Note: this never touched the Shopify REST API, so there is no GraphQL request equivalent — per-line-item user-supplied tax_lines are a REST Order-payload construct with no GraphQL counterpart (GraphQL computes tax lines server-side). - Action **Order - create** Creates a new order. - Action **Order - initialize** Starts a new Shopify order in your automation from the customer email, currency, billing and shipping addresses, tags, taxes and status you choose. It does not contact Shopify: pass the result through the Order - add steps (line items, discount codes) and then Order - create to place the order. - Action **Remove tags from customer** Remove one or more comma-separated tags from a Shopify customer (looked up by email). GraphQL Admin API port: finds the customer via a customers(query:"email:...") query, then calls the tagsRemove mutation with the customer GID and the tag list. Returns the customer's numeric id and remaining tags. - Action **Remove tags from order** Removes the given comma-separated tags from a Shopify order (by Order ID). Uses the GraphQL Admin API tagsRemove mutation; tags not present are ignored. Returns the order id and its remaining tags. - Action **Send customer invite** Sends an account invite to a customer specified by their email address. - Action **Set Product Variant Metafield** Create or update a metafield value on a product variant. - Action **Two-way sync add or update a customer** Two-way sync: find a Shopify customer by email (or by the previously mapped customer id) and update it, otherwise create a new customer. Sets email, name, phone, note, tags, marketing consent and a single address. GraphQL Admin API port of the legacy REST customers create/update flow. Returns the customer id and updated_at. - Action **Update customer** Updates an existing customer. - Action **Update Customer Default Address** Updates a customer's default address, or adds one as the default if they have none. Fields left blank are not changed. - Action **Update Customer Email Marketing Consent** Sets a Shopify customer's email marketing consent state and opt-in level. - Action **Update inventory item** Updates a Shopify inventory item (sku, cost, tracked, country code of origin, harmonized system code). Takes the numeric Inventory Item ID. - Action **Update inventory quantity** Set the absolute available inventory quantity for an inventory item at a specific location. GraphQL inventorySetQuantities mutation (name: available) replacing the REST inventory_levels/set.json endpoint. Returns the resulting available quantity, inventory item id, and location id. - Action **Update order** Update an existing Shopify order's financial status by Order ID. Returns the order's numeric id, name, updated timestamp, and financial status. - Action **Update order as fulfilled** Marks an order's fulfillment order as fulfilled by creating a fulfillment, optionally attaching tracking number/company and notifying the customer. GraphQL fulfillmentCreateV2 mutation. - Action **Update order line item as fulfilled** Creates a fulfillment for an order's fulfillment order (optionally a specific line item) with tracking info, via the GraphQL fulfillmentCreateV2 mutation. - Action **Update product** Update an existing product in Shopify (GraphQL Admin API, productUpdate mutation). Updates title, description, vendor, product type, tags, and/or status on the product identified by the Product ID setting; only provided fields are changed. Returns the product id, title, handle, status, updated timestamp, and admin GraphQL id. - Action **Update product variant** Updates an existing variant of a Shopify product — its price, compare-at price, SKU, barcode, weight and option values. Fields left blank keep their current values. - 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 - [ **Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connections/shopify) - [ **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 Shopify - [ **Shopify to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/shopify-to-slack) - [ **Shopify to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/shopify-to-google-sheets) - [ **Shopify to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/shopify-to-gmail) - [ **Shopify to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/shopify-to-mailchimp) - [ **Shopify to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/shopify-to-stripe) - [ **Shopify to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/shopify-to-trello) ## 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 ## Shopify and Supabase, answered ### ### What can start an automation from Shopify? Any of Shopify's 17 triggers in the catalog, including New cart, New customer, New customer (instant) and New order. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Supabase when something happens in Shopify? 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 Shopify? Supabase has no triggers in the catalog today, so automations start in Shopify. 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 Shopify 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 Shopify 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.