--- title: "Connect Groove to DocsBot AI - APIANT.ai" description: "When \"Customer Added\" fires in Groove, your agent runs \"Add lead\" in DocsBot AI." canonical: "https://apiant.ai/connect/groove-to-docsbot-ai" --- # Connect Groove to DocsBot AI When **Customer Added** fires in [Groove](https://apiant.ai/connections/groove), your agent runs **Add lead** in [DocsBot AI](https://apiant.ai/connections/docsbot-ai). Describe the whole flow and it is built, tested on every scenario and kept running. Groove **9** triggers Groove **15** actions DocsBot AI **13** 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 DocsBot AI 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 DocsBot AI - When **Customer Added** in Groove then **Add lead** in DocsBot AI - When **Note Added** in Groove then **Chat Agent Message (Recommended)** in DocsBot AI 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 DocsBot AI ## Triggers and actions 9 triggers · 28 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 **Add bot** Creates a new DocsBot bot in a team, optionally copying sources from an existing bot. - Action **Add lead** Captures or updates a lead for a DocsBot conversation, merging the supplied contact details (email, name, company and so on) into the lead record. - Action **Add source** Creates a new training source (URL, sitemap, document, Q&A and more) on a DocsBot bot. - Action **Ask Question (Legacy)** Asks a DocsBot bot a question using the legacy Chat API and returns the answer, its sources and the updated chat history. - Action **Chat Agent Message (Recommended)** Sends a message to a DocsBot bot in a stateful conversation and returns the agent's answer, sources and conversation history. - Action **Create Web Source** Adds a web-based training source (a page URL, sitemap, RSS feed or YouTube video) to a DocsBot bot and returns the created source. - Action **Delete bot** Permanently deletes a bot from a DocsBot team. - Action **Delete lead** Deletes one captured lead record from a DocsBot bot. - Action **Delete source** Deletes a training source from a DocsBot bot. The source may still appear in chat answers for a few minutes afterwards. - Action **Get bot** Returns one DocsBot bot with its settings, model, status and source counts. - Action **List bots** Returns the bots in a DocsBot team, optionally filtered by text or privacy and sorted. - Action **Semantic Search** Searches a bot's trained content and returns the most relevant source chunks for a natural-language query. - Action **Update bot** Updates the settings of an existing DocsBot bot, such as its name, description, prompt, model, privacy and widget appearance. Only the fields you fill in are changed. ## Each app on its own - [ **Groove** The simple helpdesk for SaaS and eCommerce businesses.](https://apiant.ai/connections/groove) - [ **DocsBot AI** DocsBot AI provides instant & accurate answers for you, your customers, or your team with AI powered...](https://apiant.ai/connections/docsbot-ai) 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 DocsBot AI - [ **HubSpot to DocsBot AI** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-docsbot-ai) - [ **Salesforce to DocsBot AI** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-docsbot-ai) - [ **Slack to DocsBot AI** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-docsbot-ai) - [ **Google Sheets to DocsBot AI** Google Sheets](https://apiant.ai/connect/google-sheets-to-docsbot-ai) - [ **Gmail to DocsBot AI** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-docsbot-ai) - [ **Google Calendar to DocsBot AI** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-docsbot-ai) Questions ## Groove and DocsBot AI, 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 DocsBot AI when something happens in Groove? Any of DocsBot AI's 13 actions, including Create Web Source, Update bot, Add bot and Add lead. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from DocsBot AI to Groove? DocsBot AI has no triggers in the catalog today, so automations start in Groove. If you need the other direction, ask: your agent reads DocsBot AI's API documentation and adds it. ### ### Do I have to build a connector for Groove or DocsBot AI? 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 DocsBot AI 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.