--- title: "Connect Groove and Metaview - APIANT.ai" description: "When \"Customer Added\" fires in Groove, your agent runs \"Send sourcing message\" in Metaview." canonical: "https://apiant.ai/connect/groove-to-metaview" --- # Connect Groove and Metaview When **Customer Added** fires in [Groove](https://apiant.ai/connections/groove), your agent runs **Send sourcing message** in [Metaview](https://apiant.ai/connections/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. Groove **9** triggers Groove **15** actions Metaview **1** trigger Metaview **31** 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 Metaview 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 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 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. - Trigger **New Conversation** Triggers when a new conversation is available in Metaview. - Action **Build chart** Creates a visual chart from conversation data with optional filtering, grouping, and timezone adjustment. - Action **Check enrichment status** Returns enrichment status and usage metrics for candidate data, with options to scope by person or enrichment type. - Action **Create AI field** Creates a new AI-powered field that analyzes conversations to answer a custom question, with configurable value type. - Action **Create report** Builds a report from conversations with filtering, metrics, grouping, and custom field inclusion. - Action **Fetch candidates** Looks up candidate information by ID, LinkedIn URL, email, or phone number in bulk. - Action **Find candidate's sequences** Finds which outreach sequences a candidate is enrolled in using their ID, LinkedIn URL, email, or phone. - Action **Get note template** Returns a note generation template by ID for use in automating note creation. - Action **Get search details** Retrieves configuration and results for a sourcing search by ID. - Action **Get sourcing analytics** Returns sourcing analytics and metrics grouped by user, search, or date range with filtering options. - Action **Get sourcing messages** Lists outreach messages sent in a sourcing search with pagination support. - Action **Get User Context** Returns information about the connected user account and available features. - Action **Give sourcing feedback** Submits feedback on candidates from a sourcing search, optionally linking to the search that sourced them. - Action **Group conversations** Groups recorded conversations by a field (like recruiter, stage, or outcome) and returns counts and metrics per group. - Action **List application reviews** Returns a list of application reviews, optionally filtering by name or showing only active ones. - Action **List ATS jobs** Returns ATS job postings, optionally filtered by job title. - Action **List ATS stages** Returns hiring pipeline stages for a job, or workspace-level stages if no job is specified. - Action **List available fields** Returns available data fields for reports, optionally filtered by name. - Action **List candidates in sequence** Returns candidates enrolled in a sequence, with optional enrollment status and per-step delivery details. - Action **List field values** Returns distinct values for a field across conversations, useful for building filters or dropdowns. - Action **List mailboxes** Returns email mailboxes available in this Metaview workspace. - Action **List note template folders** Returns folders of note templates organized in the workspace. - Action **List note templates** Returns note templates available in the workspace, optionally filtered by name or with full section details. - Action **List sequences** Returns candidate sequences, optionally filtered by name, creator, or status; includes full configuration if requested. - Action **List sourcing candidates** Returns candidates from a specified sourcing search with optional filtering by pack, feedback status, and detail level. - Action **List sourcing searches** Returns all sourcing searches with optional pagination. - Action **Manage candidate sequence** Adds, pauses, resumes, cancels, removes, or updates candidate enrollments in a recruitment sequence. - Action **Manage note template** Creates, updates, or deletes call note templates with customizable sections for structured note-taking. - Action **Manage sequence** Creates, updates, duplicates, or deletes recruitment sequences. - Action **Search conversations** Searches call conversations with optional filtering, sorting, and field selection. - Action **Search reports** Searches reports by name, category, or ID with optional full configuration details. - Action **Send sourcing message** Starts or continues a sourcing or research search with a message to the AI agent. ## Each app on its own - [ **Groove** The simple helpdesk for SaaS and eCommerce businesses.](https://apiant.ai/connections/groove) - [ **Metaview** Metaview writes your recruiting notes for you so you can save time and focus on high-quality interactions...](https://apiant.ai/connections/metaview) 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 Metaview - [ **HubSpot to Metaview** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-metaview) - [ **Google Sheets to Metaview** Google Sheets](https://apiant.ai/connect/google-sheets-to-metaview) - [ **Gmail to Metaview** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-metaview) - [ **Google Drive to Metaview** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-metaview) - [ **Mailchimp to Metaview** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-metaview) - [ **ActiveCampaign to Metaview** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-metaview) 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.