Integration
Connect Groove to Hunter
When Customer Added fires in Groove, your agent runs Create email opened webhook in Hunter. 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 Hunter 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 Hunter
When Customer Added in Groove
then Create email opened webhook in Hunter
When Note Added in Groove
then Create Lead in Hunter
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 Hunter
Triggers and actions 9 triggers · 28 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
Count EmailReturns how many email addresses Hunter knows for a domain or company, broken down by personal vs generic, department and seniority, without revealing the addresses. Free — uses no credits.
Action
Create email opened webhookSubscribes a URL to Hunter's email opened event for Sequences. Hunter POSTs to the URL each time a sequence email is opened.
Action
Create LeadCreates a lead in Hunter, or adds an existing lead with the same email to the requested lists.
Action
Delete LeadDeletes a lead from your Hunter account.
Action
Enrich companyLook up a company by its website domain and return Hunter's enriched company profile.
Action
Enrich personReturns all the information Hunter has about a person given an email address (name, position, social profiles, company).
Action
Find EmailFinds the most likely professional email address for a person, from their name plus a company domain or name, or from their LinkedIn handle.
Action
Find Emails by DomainReturns the email addresses Hunter has found for a company's domain (or company name), with names, positions and sources for each.
Action
Get LeadRetrieve a single lead from Hunter by its id.
Action
Get WebhookFetches a webhook by ID, with the event it listens for and the URL it posts to. An error occurs if the webhook is not found.
Action
List LeadsLists the leads saved in your Hunter account, most recent first, optionally filtered by list, lead attributes, statuses, dates and location.
Action
Update LeadUpdates an existing Hunter lead. Only the fields you fill in are changed; everything else on the lead is left as it is.
Action
Verify EmailChecks whether an email address is deliverable and returns Hunter's verification status, score and individual checks.
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 Hunter
HubSpot to HunterHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to HunterSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to HunterSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HunterGoogle Sheets
Gmail to HunterGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to HunterGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Groove and Hunter, 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 Hunter when something happens in Groove?
Any of Hunter's 13 actions, including Create email opened webhook, Create Lead, Update Lead and Count Email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hunter to Groove?
Hunter has no triggers in the catalog today, so automations start in Groove. If you need the other direction, ask: your agent reads Hunter's API documentation and adds it.
Do I have to build a connector for Groove or Hunter?
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.