--- title: "Connect Groove to Brex - APIANT.ai" description: "When \"Customer Added\" fires in Groove, your agent runs \"Update a Budget - “Brex Empower” Customers Only\" in Brex." canonical: "https://apiant.ai/connect/groove-to-brex" --- # Connect Groove to Brex When **Customer Added** fires in [Groove](https://apiant.ai/connections/groove), your agent runs **Update a Budget - “Brex Empower” Customers Only** in [Brex](https://apiant.ai/connections/brex). Describe the whole flow and it is built, tested on every scenario and kept running. Groove **9** triggers Groove **15** actions Brex **27** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Groove and Brex 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 Groove can start in Brex - When **Customer Added** in Groove then **Update a Budget - “Brex Empower” Customers Only** in Brex - When **Note Added** in Groove then **Create User** in Brex 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 Groove and Brex ## Triggers and actions 9 triggers · 42 actions - Trigger **Agent Replied** Triggers when an agent replies to a ticket. - Trigger **Customer Added** Triggers when a customer is created. - Trigger **Customer Replied** Triggers when a customer replies to a ticket. - Trigger **Note Added** Triggers when a note is added to a ticket. - Trigger **Ticket Assigned** Triggers when a ticket is assigned. - Trigger **Ticket Closed** Triggers when a ticket is closed. - Trigger **Ticket Opened** Triggers when a ticket is opened. - Trigger **Ticket Started** Triggers when a new ticket is created. - Trigger **Ticket Tagged** Triggers when a ticket is tagged. - Action **Add label to ticket** Adds one or more labels to a Groove ticket, keeping its existing labels, and returns the updated ticket. - Action **Add message** Adds a new message (reply or private note) to an existing Groove ticket. - Action **Add Note** Adds a private note to a Groove ticket, visible only to agents. - Action **Change Assigned Agent** Assigns a Groove ticket to a different agent, identified by the agent's email address. - Action **Change Ticket Mailbox** Moves a ticket into a different mailbox. - Action **Change Ticket State** Changes the state of a Groove ticket (unread, opened, pending, closed or spam). - Action **Close Ticket** Closes a Groove ticket by setting its state to closed. - Action **Create New Ticket** Creates a new ticket in Groove from a customer or agent, with its first message. - Action **Get customer** Returns one Groove customer, looked up by email address, including their contact details and custom attributes. - Action **Get ticket** Returns a single Groove ticket by its ticket number. - Action **List agents** Returns the agents on your Groove account, optionally limited to one group. - Action **List mailboxes** Returns all mailboxes in the Groove account, with each mailbox's name and email address. - Action **List messages** Returns the messages and notes on a Groove ticket. - Action **Reopen Ticket** Reopens a Groove ticket by setting its state to opened. - Action **Update customer** Updates a customer's profile details, such as name, company, title and contact info, identified by their email address. - Action **Create Department** Creates a new department in your Brex account and returns its ID, name and description. - Action **Create Location** Creates a new location in your Brex account and returns its ID, name and description. - Action **Create User** Creates a new Brex employee user without sending an invitation, leaving the user inactive until they are invited later. Returns the id of the new user. - Action **Create Vendor** Creates a new vendor in Brex, with optional contact details and payment accounts, and returns the created vendor. - Action **Disable User** Disables (suspends) an active Brex user and returns the updated user. Optionally changes the user's manager, department, location, title, cost center, legal entity or metadata at the same time. - Action **Email Card Details** Sends a secure email containing a card's number, CVV, and expiration date to the recipient you specify. - Action **Find a Card by ID** Returns a single Brex card by its ID, including its owner, status, type, spend controls, addresses and expiration date. - Action **Find a User** Returns the Brex users that match a name, email address or identity-provider ID, optionally narrowed by status, manager, department, location, title, cost center, legal entity or custom field value. - Action **Find Department by Name** Returns the Brex departments that match the specified department name. - Action **Find Location by Name** Returns the Brex locations that match the specified name. - Action **Find User by Email** Returns the Brex user whose email address exactly matches the one you specify, or reports that no user was found. - Action **Find Vendor by Name** Returns the vendors whose name matches the name you supply. - Action **Get Card Number** Returns the full card number, CVV, expiration date and cardholder name for a Brex card. - Action **Get Card Transactions** Returns settled card transactions across all of the company's Brex card accounts, optionally narrowed by user or posted date. - Action **Get Cash Transactions** Returns the transactions for a Brex cash account, optionally only those posted on or after a given date. - Action **List cards** Returns the company's Brex cards, optionally only those belonging to one user. - Action **List Cash Accounts** Returns all of the company's Brex cash accounts with their status, balances, account and routing numbers, and which one is primary. - Action **List departments** Returns the departments in your Brex account, optionally filtered by name. - Action **List Expenses** Returns the expenses on the Brex account, optionally narrowed by user, budget, type, status or date range. Admins and bookkeepers see every expense; other users see only their own. - Action **List locations** Returns the locations in your Brex account, optionally filtered by name. - Action **List users** Returns the users in your Brex account, optionally narrowed by name, email, status, manager, department, location, title, cost center, legal entity or custom field value. - Action **List vendors** Returns the vendors in the Brex account, optionally only those matching a vendor name. - Action **Terminate card** Permanently terminates a Brex card and returns the updated card. The card owner is notified. - Action **Update a Budget - “Brex Empower” Customers Only** Updates an existing Brex budget's name, description, parent, owners, period, amount or dates. Available to Brex Empower customers only. - Action **Update card** Updates an existing Brex vendor card's spend controls and metadata, and returns the updated card. - Action **Update User** Updates a Brex user's status, manager, department, location, title, cost center, legal entity or metadata. Anything left blank is unchanged. - Action **Update Vendor by Name** Finds a Brex vendor by its company name and updates that vendor's name, email, phone, beneficiary name or payment accounts. ## Each app on its own - [ **Groove** The simple helpdesk for SaaS and eCommerce businesses.](https://apiant.ai/connections/groove) - [ **Brex** Handle your company’s deposits, payments, credit cards, spend management, and accounting in one place.](https://apiant.ai/connections/brex) Reviews ## What our customers say ## More from Groove - [ **Groove to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/groove-to-hubspot) - [ **Groove to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/groove-to-salesforce) - [ **Groove to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/groove-to-slack) - [ **Groove to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/groove-to-mailchimp) - [ **Groove to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/groove-to-stripe) - [ **Groove to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/groove-to-shopify) ## More into Brex - [ **HubSpot to Brex** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-brex) - [ **Salesforce to Brex** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-brex) - [ **Slack to Brex** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-brex) - [ **Google Sheets to Brex** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-brex) - [ **Gmail to Brex** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-brex) - [ **Google Calendar to Brex** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-brex) Questions ## Groove and Brex, answered ### ### What can start an automation from Groove? Any of Groove's 9 triggers in the catalog, including Customer Added, Note Added, Agent Replied and Customer Replied. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Brex when something happens in Groove? Any of Brex's 27 actions, including Create Department, Create Location, Create User and Create Vendor. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Brex to Groove? Brex has no triggers in the catalog today, so automations start in Groove. If you need the other direction, ask: your agent reads Brex's API documentation and adds it. ### ### Do I have to build a connector for Groove or Brex? 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 Groove and Brex 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.