Integration
Connect Groove and Metaview
When Customer Added fires in Groove, your agent runs Send sourcing message in Metaview, or New Conversation in Metaview to Add label to ticket in Groove. 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 Metaview to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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 and Metaview can do together
From Groove to Metaview
When Customer Added in Groove
then Send sourcing message in Metaview
When Note Added in Groove
then Create AI field in Metaview
From Metaview to Groove
When New Conversation in Metaview
then Add label to ticket in Groove
When New Conversation in Metaview
then Add message in Groove
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 Metaview
Triggers and actions 10 triggers · 46 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.
Trigger
New ConversationTriggers when a new conversation is available in Metaview.
Action
Build chartCreates a visual chart from conversation data with optional filtering, grouping, and timezone adjustment.
Action
Check enrichment statusReturns enrichment status and usage metrics for candidate data, with options to scope by person or enrichment type.
Action
Create AI fieldCreates a new AI-powered field that analyzes conversations to answer a custom question, with configurable value type.
Action
Create reportBuilds a report from conversations with filtering, metrics, grouping, and custom field inclusion.
Action
Fetch candidatesLooks up candidate information by ID, LinkedIn URL, email, or phone number in bulk.
Action
Find candidate's sequencesFinds which outreach sequences a candidate is enrolled in using their ID, LinkedIn URL, email, or phone.
Action
Get note templateReturns a note generation template by ID for use in automating note creation.
Action
Get search detailsRetrieves configuration and results for a sourcing search by ID.
Action
Get sourcing analyticsReturns sourcing analytics and metrics grouped by user, search, or date range with filtering options.
Action
Get sourcing messagesLists outreach messages sent in a sourcing search with pagination support.
Action
Get User ContextReturns information about the connected user account and available features.
Action
Give sourcing feedbackSubmits feedback on candidates from a sourcing search, optionally linking to the search that sourced them.
Action
Group conversationsGroups recorded conversations by a field (like recruiter, stage, or outcome) and returns counts and metrics per group.
Action
List application reviewsReturns a list of application reviews, optionally filtering by name or showing only active ones.
Action
List ATS jobsReturns ATS job postings, optionally filtered by job title.
Action
List ATS stagesReturns hiring pipeline stages for a job, or workspace-level stages if no job is specified.
Action
List available fieldsReturns available data fields for reports, optionally filtered by name.
Action
List candidates in sequenceReturns candidates enrolled in a sequence, with optional enrollment status and per-step delivery details.
Action
List field valuesReturns distinct values for a field across conversations, useful for building filters or dropdowns.
Action
List mailboxesReturns email mailboxes available in this Metaview workspace.
Action
List note template foldersReturns folders of note templates organized in the workspace.
Action
List note templatesReturns note templates available in the workspace, optionally filtered by name or with full section details.
Action
List sequencesReturns candidate sequences, optionally filtered by name, creator, or status; includes full configuration if requested.
Action
List sourcing candidatesReturns candidates from a specified sourcing search with optional filtering by pack, feedback status, and detail level.
Action
List sourcing searchesReturns all sourcing searches with optional pagination.
Action
Manage candidate sequenceAdds, pauses, resumes, cancels, removes, or updates candidate enrollments in a recruitment sequence.
Action
Manage note templateCreates, updates, or deletes call note templates with customizable sections for structured note-taking.
Action
Manage sequenceCreates, updates, duplicates, or deletes recruitment sequences.
Action
Search conversationsSearches call conversations with optional filtering, sorting, and field selection.
Action
Search reportsSearches reports by name, category, or ID with optional full configuration details.
Action
Send sourcing messageStarts or continues a sourcing or research search with a message to the AI agent.
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 Metaview
HubSpot to MetaviewHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to MetaviewGoogle Sheets
Gmail to MetaviewGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Drive to MetaviewGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to MetaviewMailchimp marketing automation and email platform.
ActiveCampaign to MetaviewActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Groove and Metaview, 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 Metaview when something happens in Groove?
Any of Metaview's 31 actions, including Create AI field, Create report, Send sourcing message and Build chart. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Metaview to Groove?
Yes. When something happens in Metaview, your agent can act in Groove too. This page covers both directions: Metaview's triggers and Groove's actions are listed here as well.
Do I have to build a connector for Groove or Metaview?
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 Metaview 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.