--- title: "Connect HubSpot to Supabase - APIANT.ai" description: "When \"Deal stage changed\" fires in HubSpot, your agent runs \"Create Project Signing Key\" in Supabase." canonical: "https://apiant.ai/connect/hubspot-to-supabase" --- # Connect HubSpot to Supabase When **Deal stage changed** fires in [HubSpot](https://apiant.ai/connections/hubspot), 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. HubSpot **29** triggers HubSpot **137** 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 HubSpot 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 HubSpot can start in Supabase - When **Deal stage changed** in HubSpot then **Create Project Signing Key** in Supabase - When **Form submitted** in HubSpot 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 HubSpot and Supabase ## Triggers and actions 29 triggers · 275 actions - Trigger **Company deleted** Triggered on deletion of existing company. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Trigger **Contact deleted** Triggered on deletion of existing contact. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Trigger **Deal deleted** Triggered on deletion of existing deal. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Trigger **Deal stage changed** Triggers when a deal moves to a new stage in a pipeline. - Trigger **Form submitted** Triggers when a contact submits the chosen HubSpot form. Turning the automation on creates a HubSpot workflow that forwards each submission; turning it off deletes that workflow. Requires a HubSpot plan whose workflows can send webhooks. - Trigger **New associated object** Triggers when a new record of one CRM object type becomes associated with a record of another object type (for example, a deal linked to a company). - Trigger **New blog post** Triggers on a new blog post added to the selected blog. - Trigger **New calendar task +30d** Triggered when a new calendar task is created in the next 30 days. Note: this applies to HubSpot (Marketing), and not HubSpot CRM's tasks. Note: only supports up to 499 tasks in the next 30 days, an error will occur if more than 499 tasks exist. - Trigger **New company** Triggered when a new company is added. - Trigger **New company (instant)** Triggered on creation of new company. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Trigger **New contact** Triggered on creation of new contact. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Trigger **New deal** Triggered on creation of new deal. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Trigger **New note added to contact** Triggers when a note linked to a contact is added in HubSpot. - Trigger **New or changed engagements** Triggers on new or changed engagements. - Trigger **New or updated company** Triggered when a company is created or modified - Trigger **New or updated contact** Triggers on new or updated contacts. - Trigger **New or updated contact (Custom Fields Included)** Triggered when a contact is created or updated. - Trigger **New or updated deal** Triggered when a deal is created or updated. - Trigger **New or updated ticket** Triggered when a ticket is created or updated. - Trigger **New social media message** Triggered when a new social media message is added. - Trigger **New ticket** Triggers when new ticket is available. - Trigger **Ticket property changed** Triggered when the chosen property changes on a ticket - Trigger **Two-way sync new or updated companies** A trigger for two-way syncing new and updated companies, 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 contacts** A trigger for two-way syncing new and updated contacts, with enhanced on-the-fly mapping. Can only be used with enhanced two-way sync actions that support on-the-fly mapping. - Trigger **Updated company custom property** Triggered when the selected custom property is updated on a company. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Trigger **Updated contact** Triggered when a contact is updated. - Trigger **Updated contact custom property** Triggered when the selected custom property is updated on a contact. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Trigger **Updated contact custom property by name** Triggered when the specified custom property is updated on a contact. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Trigger **Updated deal custom property** Triggered when the selected custom property is updated on a deal. Should only be set up with one account per organization, as all user accounts within an organization share the same portalId (unique identifier). - Action **Add company** Adds a new company. - Action **Add contact** Adds a new contact. An error occurs if the email already exists. If a company name is found, the contact is associated with the company. Emits the contact ID if added. - Action **Add contact to list** Adds a contact to the specified contact list. - Action **Add contact to workflow** Enrolls a contact to a workflow provided the workflow ID and the contact email. - Action **Add custom object record** Adds a record to the specified custom object. - Action **Add deal** Creates a new deal and optionally associates it with a contact and/or company. - Action **Add meeting** Creates a meeting engagement. - Action **Add or update company** Adds a new company if the name does not already exist, otherwise updates the existing company. Only non-empty properties are updated. - Action **Add or update contact** Adds or updates a contact. If a company name is found, the contact is associated with the company. The ID of the added/updated contact is emitted as output. - Action **Add or update deal** Searches for a deal by name. If found it updates it, if not it adds it. If a contact email or company name is provided, the deal is associated with them if found. - Action **Add ticket** Adds a new ticket. - Action **Append company dropdown property values** Appends one or more values to a company dropdown property. An error occurs if the named property is not found. - Action **Append company multi-select property dropdown values** Appends one or more dropdown values to a company multi-select property. An error occurs if the named property is not found. - Action **Append contact dropdown property values** Appends one or more values to a contact dropdown property. An error occurs if the named property is not found. - Action **Append contact multi-select property dropdown values** Appends one or more dropdown values to a contact multi-select property. An error occurs if the named property is not found. - Action **Append deal dropdown property values** Appends one or more values to a deal dropdown property. An error occurs if the named property is not found. - Action **Append deal multi-select property dropdown values** Appends one or more dropdown values to a deal multi-select property. An error occurs if the named property is not found. - Action **Append ticket dropdown property values** Appends one or more values to a ticket dropdown property. An error occurs if the named property is not found. - Action **Append ticket multi-select property values** Appends one or more values to a ticket multi-select property. An error occurs if the named property is not found. - Action **Clear contact property value** Erases the value of specified property for the specified contact. - Action **Clear deal property value** Erases the value of specified property for the specified deal. - Action **Clear ticket property value** Erases the value of specified property for the specified ticket. - Action **Convert to valid property name** Converts a string value into a valid property name. Property names must begin with a letter and contain only up to 100 lowercase letters, numbers, or underscores, without any spaces, commas, or special characters. - Action **Copy workflow** Copies the specified workflow. The new workflow will have "COPY" appended to its name. - Action **Create a blog post** Creates a new blog post - Action **Create a company property: boolean checkbox** Creates a boolean checkbox company property. No error occurs if the property already exists. - Action **Create a company property: dropdown select** Creates a dropdown select list company property. No error occurs if the property already exists. - Action **Create a company property group** Creates a company property group. No error occurs if the group already exists. - Action **Create a company property: multi-select** Creates a multi-select list company property. No error occurs if the property already exists. - Action **Create a company property: single value** Creates a company property that can be a single value such as text strings, numbers, dates, and datetimes. No error occurs if the property already exists. - Action **Create a contact list** Creates a contact list. An error occurs if the list already exists. - Action **Create a contact property: boolean checkbox** Creates a boolean checkbox contact property. No error occurs if the property already exists. - Action **Create a contact property: dropdown select** Creates a dropdown select list contact property. No error occurs if the property already exists. - Action **Create a contact property group** Creates a contact property group. No error occurs if the group already exists. - Action **Create a contact property: multi-select** Creates a multi-select list contact property. No error occurs if the property already exists. - Action **Create a contact property: single value** Creates a contact property that can be a single value such as text strings, numbers, dates, and datetimes. No error occurs if the property already exists. - Action **Create a deal pipeline and stages** Creates a new deal pipeline and up to 10 stages. - Action **Create a deal property** Creates a deal property. No error occurs if the property already exists. - Action **Create a deal property: boolean checkbox** Creates a boolean checkbox deal property. No error occurs if the property already exists. - Action **Create a deal property: dropdown select** Creates a dropdown select list deal property. No error occurs if the property already exists. - Action **Create a deal property group** Creates a deal property group. No error occurs if the group already exists. - Action **Create a deal property: multi-select** Creates a multi-select list deal property. No error occurs if the property already exists. - Action **Create a deal property: single value** Creates a deal property that can be a single value such as text strings, numbers, dates, and datetimes. No error occurs if the property already exists. - Action **Create an email engagement** Logs an incoming email in HubSpot and links it to the given contacts, companies and deals. - Action **Create a note engagement** Creates a note in HubSpot and links it to the given contacts, companies, deals and tickets. - Action **Create association** Creates an association between two objects - Action **Create association: contact to contact** Creates an association between two contacts - Action **Create association type** Creates an association type between two objects. An error occurs if the association already exists. - Action **Create a task engagement** Creates a new task engagement. - Action **Create a ticket property: boolean checkbox** Creates a boolean checkbox ticket property. No error occurs if the property already exists. - Action **Create a ticket property: dropdown select** Creates a dropdown select list ticket property. No error occurs if the property already exists. - Action **Create a ticket property group** Creates a ticket property group. No error occurs if the group already exists. - Action **Create a ticket property: multi-select** Creates a multi-select list ticket property. No error occurs if the property already exists. - Action **Create a ticket property: single value** Creates a ticket property that can be a single value such as text strings, numbers, dates, and datetimes. No error occurs if the property already exists. - Action **Create custom association** Creates an association between two objects using a custom association type. Use the "get association types" action to obtain the custom association type. - Action **Create record** Creates a record of the selected CRM object type with the supplied properties. - Action **CRM card: set display values** Builds the results payload a HubSpot CRM card data-fetch request expects: one card entry carrying the record id it describes, its title, an optional link, and the property rows to display. - Action **Delete contact** Deletes a contact provided its contact ID. - Action **Delete contact list** Deletes a contact list specified by ID. - Action **Delete contact secondary email** Deletes the specified secondary email for the specified contact. An error will occur if either the contact or secondary email is not found. - Action **Delete deal** Deletes a deal provided its deal ID. - Action **Delete record** Deletes a record of the selected CRM object type by ID. - Action **Delete ticket** Deletes a ticket provided a ticket ID. - Action **Find companies associated to contact** Returns up to 500 company IDs associated with the specified contact - Action **Find company by name** Searches for a company by name (case-insensitive) and emits the company's ID. Zero, one, or multiple ID's may be emitted. - Action **Find company by property** Searches for a company by property (case-insensitive) and emits the company's information. Only the first matching company is emitted. If no matches are found, an error occurs. - Action **Find contact by email** Finds a contact by email. If the contact is not found, no information is emitted and no error occurs. - Action **Find contact by property** Search HubSpot contacts by any property name/value pair (EQ filter). Returns the first matching contact's standard fields. - Action **Find contact list by name** Look up a contact list by its name and return its v3 list id. Use this instead of 'Get all contact lists' whenever the id will be passed to a v3 endpoint such as 'Add contact to list': the v1 lists endpoint returns ids from a different id space, and feeding a v1 id to a v3 endpoint silently targets a different list. - Action **Find contacts by property** Returns contact IDs for all contacts matching the specified property value. - Action **Find custom object records associated to contact** Given a HubSpot contact ID and a custom object type, returns the IDs of all custom object records associated to that contact. Paginated via the v4 associations API. Used by the CRMConnect v3.8 membership reconciliation pass. - Action **Find custom object records by property** Returns record IDs for all records of the specified custom object matching the specified property value. - Action **Find deal by name** Searches for a deal by name (case-insensitive) and emits the company's ID. Zero, one, or multiple ID's may be emitted. - Action **Find deal by property** Searches for a deal by property (case-insensitive) and emits its information. Only the first matching deal is emitted. If no matches are found, an error occurs. - Action **Find deals associated to company** Returns up to 500 deal IDs associated with the specified company - Action **Find deals associated to contact** Returns up to 500 deal IDs associated with the specified contact - Action **Find owner by email** Fetches owner details for an owner with the specified email address. - Action **Find pipeline by name** Finds a pipeline provided its name and its type. - Action **Find recently modified deals** Returns recently modified deals. - Action **Get associated records with labels** List the records associated to a record, including the label and type of each association. - Action **Get association types** Returns all association types between the specified two object types. - Action **Get calls for contact** Returns all calls with the specified contact, optionally within a specified datetime range. - Action **Get calls for deal** Returns all calls with the specified deal, optionally within a specified datetime range. - Action **Get company** Returns company details for the specified ID. - Action **Get contact** Returns contact details for the specified ID. - Action **Get contact list** Read a single contact list by its ID. - Action **Get contact secondary emails** Returns all secondary emails for the specified contact. - Action **Get custom object records batch by IDs** Given a custom object type, a comma-separated list of record IDs, and a comma-separated list of property API names, returns one record per ID with the requested properties, one batch per call. Used by the CRMConnect v3.8 membership reconciliation pass. - Action **Get deal** Returns details for the deal with the specified ID. - Action **Get emails for contact** Returns all emails with the specified contact, optionally within a specified datetime range. - Action **Get emails for deal** Returns all emails with the specified deal, optionally within a specified datetime range. - Action **Get meetings for contact** Returns all meetings with the specified contact, optionally within a specified datetime range. - Action **Get meetings for deal** Returns all meetings with the specified deal, optionally within a specified datetime range. - Action **Get notes for contact** Returns all notes with the specified contact, optionally within a specified datetime range. - Action **Get notes for deal** Returns all notes with the specified deal, optionally within a specified datetime range. - Action **Get Object by Field Value** Looks up a record of the selected HubSpot CRM object type by an exact match on a single property (the Object, Field, and Value settings), returning the first matching record ID. - Action **Get object property info** Returns information for the specified property for the specified company, contact, or deal object type. - Action **Get owner** Returns details for the owner with the specified ID. - Action **Get record** Returns a single record of the selected CRM object type by ID. - Action **Get tasks for contact** Returns all tasks with the specified contact, optionally within a specified datetime range. - Action **Get tasks for deal** Returns all tasks with the specified deal, optionally within a specified datetime range. - Action **Get ticket** Returns details for the ticket with the specified ID. - Action **Get total number of contacts having property** Returns the total number of contacts having the specified property. - Action **Import records from CSV into object** Imports records from a CSV file into a specified object. - Action **List all workflows** Returns the name and id of all workflows visible in the portal. - Action **List contact IDs of a company** Given a company ID, finds all contacts in that company. - Action **List contact list memberships (v3)** Returns the contacts that are currently members of a HubSpot contact list, identified by the list's v3 (ILS) id. - Action **List owners** Returns a list of HubSpot account owners, supporting pagination and optional filtering by email. - Action **List pipelines** Returns the pipelines for deals or tickets, depending on which object type you select. - Action **List pipeline stages** Returns the stages in a specific deal or ticket pipeline. - Action **List records** Lists records of the selected CRM object type. - Action **Log call** Logs a completed call in HubSpot and links it to the given contacts. - Action **Merge contacts** Merge two contact records. The contact ID will be treated as the primary contact, and the contact ID to merge will be treated as the secondary contact. Most recent property values such as email and name will overwrite older values. - Action **Parse property option errors** Emits arrays of property and option names parsed from the input error message. Empty arrays are emitted if the input error message is empty. - Action **Remove contact from list (v3)** Removes a contact from a HubSpot contact list, using the list's v3 (ILS) id. Only MANUAL and SNAPSHOT lists accept membership changes. - Action **Search contact lists (v3)** Returns the contact lists in the connected HubSpot account, optionally narrowed by a name search, processing type, or object type. Each list comes back with its ILS (v3) list id, name and processing type. - Action **Search records** Searches records of the selected CRM object type by filter criteria. - Action **Submit a form** Submits a form to the Forms API - Action **Two-way sync add or update a company** An action for two-way syncing new and updated companies, with enhanced on-the-fly mapping using company names for matching. Can only be used with enhanced two-way sync triggers that support on-the-fly mapping. - Action **Unsubscribe contact from all lists** Unsubscribes a contact from all lists. - Action **Update company** Updates an existing company specified by ID. A field you map but leave EMPTY is IGNORED - the stored value is preserved, not erased. Because of that, this action cannot CLEAR a property: to empty one, edit it in HubSpot directly. - Action **Update company multi-select property - check value** Updates the specified multi-select property for the specified company such that the specified value is checked if not already checked. - Action **Update company multi-select property - uncheck value** Updates the specified multi-select property for the specified company such that the specified value is unchecked (removed). - Action **Update contact** Updates an existing contact specified by ID. A field you map but leave EMPTY is IGNORED - the stored value is preserved, not erased. Because of that, this action cannot CLEAR a property: to empty one, edit it in HubSpot directly. - Action **Update contact multi-select property - check value** Updates the specified multi-select property for the specified contact such that the specified value is checked if not already checked. - Action **Update contact multi-select property - uncheck value** Updates the specified multi-select property for the specified contact such that the specified value is unchecked (removed). - Action **Update contact properties** Updates the values of up to 6 specified properties for the specified contact. A field you map but leave EMPTY is IGNORED - the stored value is preserved, not erased. Because of that, this action cannot CLEAR a property: to empty one, edit it in HubSpot directly. - Action **Update custom object multi-select property - check value** Updates the specified multi-select property for the specified custom object record such that the specified value is checked if not already checked. - Action **Update custom object record** Updates a specified record in the specified custom object. - Action **Update custom object record pipeline and stage** Updates the specified custom object record to place it in the specified pipeline and stage. - Action **Update deal** Updates an existing deal specified by ID. A field you map but leave EMPTY is IGNORED - the stored value is preserved, not erased, and the related calculated amounts (amount in home currency, forecast amount) are left intact. Because of that, this action cannot CLEAR a property: to empty one, edit it in HubSpot directly. - Action **Update deal multi-select property - check value** Updates the specified multi-select property for the specified deal such that the specified value is checked if not already checked. - Action **Update deal multi-select property - uncheck value** Updates the specified multi-select property for the specified deal such that the specified value is unchecked (removed). - Action **Update record** Updates properties on a record of the selected CRM object type by ID. A field you map but leave EMPTY is IGNORED - the stored value is preserved, not erased. Because of that, this action cannot CLEAR a property: to empty one, edit it in HubSpot directly. - Action **Update ticket multi-select property - check value** Updates the specified multi-select property for the specified ticket such that the specified value is checked if not already checked. - Action **Update ticket multi-select property - uncheck value** Updates the specified multi-select property for the specified ticket such that the specified value is unchecked. - Action **Upload Files** Imports a file into the HubSpot File Manager from a public URL (asynchronous import). Set the source URL plus optional name, public/indexable access, and hidden flag; emits the created file reference. - 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 - [ **HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connections/hubspot) - [ **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 HubSpot - [ **HubSpot to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/hubspot-to-salesforce) - [ **HubSpot to Google Sheets** Google Sheets](https://apiant.ai/connect/hubspot-to-google-sheets) - [ **HubSpot to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/hubspot-to-stripe) - [ **HubSpot to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/hubspot-to-shopify) - [ **HubSpot to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/hubspot-to-quickbooks-online) - [ **HubSpot to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/hubspot-to-pipedrive) ## More into Supabase - [ **Airtable to Supabase** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-supabase) - [ **Benetics to Supabase** Benetics is a construction efficiency platform built in the cloud.](https://apiant.ai/connect/benetics-to-supabase) - [ **Erpnext to Supabase** Open-source ERP system for accounting, inventory, manufacturing, sales, projects, and CRM.](https://apiant.ai/connect/erpnext-to-supabase) - [ **Form Io to Supabase** Form-builder platform that auto-generates REST APIs for form submissions, data validation, and workflow...](https://apiant.ai/connect/form-io-to-supabase) - [ **ONLYOFFICE DocSpace to Supabase** ONLYOFFICE DocSpace is a room-based collaboration environment for organizing teamwork on an any content.](https://apiant.ai/connect/onlyoffice-docspace-to-supabase) - [ **Salesforce to Supabase** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-supabase) Questions ## HubSpot and Supabase, answered ### ### What can start an automation from HubSpot? Any of HubSpot's 29 triggers in the catalog, including Deal stage changed, Form submitted, New associated object and New blog post. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Supabase when something happens in HubSpot? 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 HubSpot? Supabase has no triggers in the catalog today, so automations start in HubSpot. 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 HubSpot 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 HubSpot 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.