Integration
Connect Groove to Hyperbrowser
When Customer Added fires in Groove, your agent runs Extract Data from Web Page in Hyperbrowser. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Groove and Hyperbrowser to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Groove can start in Hyperbrowser
When Customer Added in Groove
then Extract Data from Web Page in Hyperbrowser
When Note Added in Groove
then Scrape web page in Hyperbrowser
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 Hyperbrowser
Triggers and actions 9 triggers · 29 actions
Trigger
Agent RepliedTriggers when an agent replies to a ticket.
Trigger
Customer AddedTriggers when a customer is created.
Trigger
Customer RepliedTriggers when a customer replies to a ticket.
Trigger
Note AddedTriggers when a note is added to a ticket.
Trigger
Ticket AssignedTriggers when a ticket is assigned.
Trigger
Ticket ClosedTriggers when a ticket is closed.
Trigger
Ticket OpenedTriggers when a ticket is opened.
Trigger
Ticket StartedTriggers when a new ticket is created.
Trigger
Ticket TaggedTriggers when a ticket is tagged.
Action
Add label to ticketAdds one or more labels to a Groove ticket, keeping its existing labels, and returns the updated ticket.
Action
Add messageAdds a new message (reply or private note) to an existing Groove ticket.
Action
Add NoteAdds a private note to a Groove ticket, visible only to agents.
Action
Change Assigned AgentAssigns a Groove ticket to a different agent, identified by the agent's email address.
Action
Change Ticket MailboxMoves a ticket into a different mailbox.
Action
Change Ticket StateChanges the state of a Groove ticket (unread, opened, pending, closed or spam).
Action
Close TicketCloses a Groove ticket by setting its state to closed.
Action
Create New TicketCreates a new ticket in Groove from a customer or agent, with its first message.
Action
Get customerReturns one Groove customer, looked up by email address, including their contact details and custom attributes.
Action
Get ticketReturns a single Groove ticket by its ticket number.
Action
List agentsReturns the agents on your Groove account, optionally limited to one group.
Action
List mailboxesReturns all mailboxes in the Groove account, with each mailbox's name and email address.
Action
List messagesReturns the messages and notes on a Groove ticket.
Action
Reopen TicketReopens a Groove ticket by setting its state to opened.
Action
Update customerUpdates a customer's profile details, such as name, company, title and contact info, identified by their email address.
Action
Add profileCreates a new Hyperbrowser browser profile that sessions can reuse to keep cookies and browser state.
Action
Add sessionCreates (launches) a new Hyperbrowser cloud browser session and returns its id, status and connection endpoints.
Action
Crawl WebsiteStarts a Hyperbrowser crawl job that visits pages of a website starting from a URL and returns the job id. Use the crawl job status/results operations to read the crawled pages.
Action
Delete profileDelete a browser profile by ID.
Action
Extract Data from Web PageExtracts data from a web page and returns the extracted content.
Action
Extract Structured DataStarts a Hyperbrowser extract job on one or more URLs and waits for it to finish, returning the structured data the AI extracted.
Action
Fetch web pageFetches a web page and returns its content as Markdown, HTML, links, a screenshot, extracted JSON or a branding profile.
Action
Get profileRetrieves a Hyperbrowser browser profile by its ID.
Action
Get sessionRetrieves a Hyperbrowser browser session by its ID, including its status, timing, launch settings, credits used and connection endpoints.
Action
List profilesList all browser profiles.
Action
List sessionsReturns all browser sessions, optionally only those with a given status.
Action
Scrape web pageScrapes a web page in a cloud browser and returns its content as markdown, HTML, links and/or a screenshot, plus the page metadata.
Action
Search webSearch the web and return results (RPC-style).
Action
Stop sessionStops a running Hyperbrowser browser session.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Groove
Groove to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Groove to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Groove to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Groove to MailchimpMailchimp marketing automation and email platform.
Groove to StripeStripe is a payment processing platform for online businesses.
Groove to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Hyperbrowser
HubSpot to HyperbrowserHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to HyperbrowserSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to HyperbrowserSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HyperbrowserGoogle Sheets
Gmail to HyperbrowserGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HyperbrowserGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Groove and Hyperbrowser, 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 Hyperbrowser when something happens in Groove?
Any of Hyperbrowser's 14 actions, including Add profile, Add session, Crawl Website and Extract Data from Web Page. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hyperbrowser to Groove?
Hyperbrowser has no triggers in the catalog today, so automations start in Groove. If you need the other direction, ask: your agent reads Hyperbrowser's API documentation and adds it.
Do I have to build a connector for Groove or Hyperbrowser?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.