--- title: "Connect Groove to Apify - APIANT.ai" description: "When \"Customer Added\" fires in Groove, your agent runs \"Run Task\" in Apify. Describe the whole flow and it is built, tested on every scenario and kept running." canonical: "https://apiant.ai/connect/groove-to-apify" --- # Connect Groove to Apify When **Customer Added** fires in [Groove](https://apiant.ai/connections/groove), your agent runs **Run Task** in [Apify](https://apiant.ai/connections/apify). Describe the whole flow and it is built, tested on every scenario and kept running. Groove **9** triggers Groove **15** actions Apify **18** 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 Apify 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 Apify - When **Customer Added** in Groove then **Run Task** in Apify - When **Note Added** in Groove then **Set Key-Value Store Record** in Apify 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 Apify ## Triggers and actions 9 triggers · 33 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 **Abort Actor build** Aborts an Actor build that is starting or running and returns the build's details. Builds that already finished, failed, timed out or are aborting are left unchanged. - Action **Abort Actor run** Aborts a running or starting Apify Actor run and returns the run's details, including its updated status. Runs that already finished, failed or timed out are left unchanged. - Action **Add dataset items** Appends one or more items to the end of an Apify dataset. - Action **Delete key-value store record** Deletes a record, identified by its key, from an Apify key-value store. - Action **Fetch Dataset Items** Returns all items stored in an Apify dataset, such as the results scraped by an Actor run, with optional field selection and cleanup. - Action **Find Last Actor Run** Returns the most recent run of an Actor, optionally limited to runs with a given status or started a given way, including its status, timing and the ids of its default dataset and key-value store. - Action **Find Last Task Run** Returns the most recent run of an Apify Actor task, optionally limited to runs with a given status or origin. - Action **Get Actor** Returns all the details of an Apify Actor, including its versions, default run options, statistics and pricing. - Action **Get Actor run** Returns the details of one Actor run, including its status, timing, statistics, costs and the IDs of its default dataset, key-value store and request queue. Can optionally wait up to 60 seconds for the run to finish. - Action **Get Key-Value Store Record** Returns the value stored under a key in an Apify key-value store, such as an Actor run's output or input record. - Action **Get task** Returns the details of an Apify Actor task, including its saved input, run options, and run statistics. - Action **List Actor runs** Returns the runs of one of your Apify Actors, with each run's status, start and finish times, cost and the IDs of its default dataset and key-value store. Can be filtered by status and start date. - Action **List Actors** Returns the Actors you created or have used in your Apify account, with each Actor's ID, name, owner username, title and usage stats. - Action **List datasets** Returns the datasets in your Apify account, with each dataset's id, name, item count and timestamps. - Action **List tasks** Returns the Actor tasks you have created or used, with each task's id, name, Actor and run stats. - Action **Run Actor** Starts a run of an Apify Actor with the input you provide and returns the new run, including its status and the IDs of its default dataset and key-value store. - Action **Run Task** Starts a run of one of your saved Apify Actor tasks, optionally overriding parts of its input, and returns the new run with its status and storage IDs. - Action **Set Key-Value Store Record** Saves a value under a key in an Apify key-value store, replacing any existing record with the same key. ## Each app on its own - [ **Groove** The simple helpdesk for SaaS and eCommerce businesses.](https://apiant.ai/connections/groove) - [ **Apify** Apify is a full-stack platform where developers build, deploy, and monitor web scraping tools.](https://apiant.ai/connections/apify) 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 Apify - [ **HubSpot to Apify** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-apify) - [ **Salesforce to Apify** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-apify) - [ **Slack to Apify** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-apify) - [ **Google Sheets to Apify** Google Sheets](https://apiant.ai/connect/google-sheets-to-apify) - [ **Gmail to Apify** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-apify) - [ **Google Calendar to Apify** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-apify) Questions ## Groove and Apify, 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 Apify when something happens in Groove? Any of Apify's 18 actions, including Abort Actor build, Abort Actor run, Add dataset items and Fetch Dataset Items. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Apify to Groove? Apify has no triggers in the catalog today, so automations start in Groove. If you need the other direction, ask: your agent reads Apify's API documentation and adds it. ### ### Do I have to build a connector for Groove or Apify? 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 Apify 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.