--- title: "Connect Groove to Fatture in Cloud - APIANT.ai" description: "When \"Customer Added\" fires in Groove, your agent runs \"Create Client\" in Fatture in Cloud." canonical: "https://apiant.ai/connect/groove-to-fatture-in-cloud" --- # Connect Groove to Fatture in Cloud When **Customer Added** fires in [Groove](https://apiant.ai/connections/groove), your agent runs **Create Client** in [Fatture in Cloud](https://apiant.ai/connections/fatture-in-cloud). Describe the whole flow and it is built, tested on every scenario and kept running. Groove **9** triggers Groove **15** actions Fatture in Cloud **73** 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 Fatture in Cloud 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 Fatture in Cloud - When **Customer Added** in Groove then **Create Client** in Fatture in Cloud - When **Note Added** in Groove then **Create Issued Document** in Fatture in Cloud 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 Fatture in Cloud ## Triggers and actions 9 triggers · 88 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 **Create Cashbook Entry** Creates a new cashbook entry. - Action **Create Client** Creates a new client in a Fatture in Cloud company. - Action **Create F24** Creates a new F24 tax payment record in a Fatture in Cloud company. - Action **Create Issued Document** Creates a new issued document (invoice, quote, proforma, receipt, delivery note, credit note, order, work report, supplier order or self invoice) in a Fatture in Cloud company. - Action **Create Payment Account** Creates a new payment account. - Action **Create Payment Method** Creates a new payment method. - Action **Create Product** Creates a new product. - Action **Create Receipt** Creates a new receipt. - Action **Create Received Document** Creates a new document. - Action **Create Supplier** Creates a new supplier. - Action **Create Vat Type** Creates a vat type. - Action **Delete Bin Issued Document** Delete Bin Issued Document - Action **Delete Bin Received Document** Delete Bin Received Document - Action **Delete Cashbook Entry** Deletes the specified cashbook entry. - Action **Delete Client** Deletes the specified client. - Action **Delete F24** Removes the specified F24. - Action **Delete F24 Attachment** Removes the attachment of the specified F24. - Action **Delete Issued Document** Deletes the specified document. - Action **Delete Issued Document Attachment** Removes the attachment of the specified document. - Action **Delete Payment Account** Deletes the specified payment account. - Action **Delete Payment Method** Deletes the specified payment method. - Action **Delete Product** Deletes the specified product. - Action **Delete Receipt** Deletes the specified receipt. - Action **Delete Received Document** Deletes the specified document. - Action **Delete Supplier** Deletes the specified supplier. - Action **Delete Vat Type** Deletes the specified vat type. - Action **Get Archive Document** Gets the specified archive document. - Action **Get Bin Issued Documents List** Returns the issued documents currently in the bin. - Action **Get Bin Received Documents List** Get bin issued documents detail - Action **Get Cashbook Entry** Gets the specified cashbook entry. - Action **Get Client** Gets the specified client. - Action **Get F24** Gets the specified F24. - Action **Get Issued Document** Gets the specified document. - Action **Get Payment Account** Gets the specified payment account. - Action **Get Payment Method** Gets the specified payment method. - Action **Get Product** Gets the specified product. - Action **Get Receipt** Gets the specified receipt. - Action **Get Received Document** Gets the specified document. - Action **Get Supplier** Gets the specified supplier. - Action **Get Vat Type** Gets the specified vat type. - Action **Join Issued Documents** Joins issued documents. - Action **List Archive Documents** Lists the archive documents. - Action **List Cashbook Entries** Lists the cashbook entries. - Action **List Clients** Lists the clients. - Action **List F24** Lists the F24s. - Action **List Issued Documents** Lists the issued documents. - Action **List Payment Accounts** Lists the available payment accounts. - Action **List Payment Methods** Lists the available payment methods. - Action **List Pending Received Documents** Lists the pending received documents. - Action **List Products** Lists the products. - Action **List Receipts** Lists the receipts. - Action **List Received Documents** Lists the received documents. - Action **List Suppliers** Lists the suppliers. - Action **List Vat Types** Lists the available vat types. - Action **Modify Archive Document** Modifies the specified archive document. - Action **Modify Cashbook Entry** Modifies the specified cashbook entry. - Action **Modify Client** Modifies the specified client. - Action **Modify F24** Modifies the specified F24. - Action **Modify Issued Document** Modifies the specified document. - Action **Modify Payment Account** Modifies the specified payment account. - Action **Modify Payment Method** Modifies the specified payment method. - Action **Modify Product** Modifies the specified product. - Action **Modify Receipt** Modifies the specified receipt. - Action **Modify Received Document** Modifies the specified document. - Action **Modify Supplier** Modifies the specified supplier. - Action **Modify Vat Type** Modifies the specified vat type. - Action **Recover Issued Document From the Bin** Recover Issued Document From the Bin - Action **Recover Received Document From the Bin** Recover Received Document From the Bin - Action **Schedule Email** Schedules the sending of a document by email. - Action **Upload Archive Document Attachment** Uploads an attachment destined to an archive document. The actual association between the document and the attachment must be implemented separately, using the returned token. - Action **Upload F24 Attachment** Uploads an attachment destined to a F24. The actual association between the document and the attachment must be implemented separately, using the returned token. - Action **Upload Issued Document Attachment** Uploads an attachment destined to an issued document. The actual association between the document and the attachment must be implemented separately, using the returned token. - Action **Upload Received Document Attachment** Uploads an attachment destined to a received document. The actual association between the document and the attachment must be implemented separately, using the returned token. ## Each app on its own - [ **Groove** The simple helpdesk for SaaS and eCommerce businesses.](https://apiant.ai/connections/groove) - [ **Fatture in Cloud** Fatture in Cloud is an italian online invoicing software with all the tools you need keep your business...](https://apiant.ai/connections/fatture-in-cloud) 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 Fatture in Cloud - [ **MINDBODY to Fatture in Cloud** MINDBODY is a powerful business management software that combines your scheduling, task automation...](https://apiant.ai/connect/mindbody-to-fatture-in-cloud) - [ **HubSpot to Fatture in Cloud** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-fatture-in-cloud) - [ **Salesforce to Fatture in Cloud** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-fatture-in-cloud) - [ **Slack to Fatture in Cloud** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-fatture-in-cloud) - [ **Google Sheets to Fatture in Cloud** Google Sheets](https://apiant.ai/connect/google-sheets-to-fatture-in-cloud) - [ **Gmail to Fatture in Cloud** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-fatture-in-cloud) Questions ## Groove and Fatture in Cloud, 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 Fatture in Cloud when something happens in Groove? Any of Fatture in Cloud's 73 actions, including Create Cashbook Entry, Create Client, Create F24 and Create Issued Document. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Fatture in Cloud to Groove? Fatture in Cloud has no triggers in the catalog today, so automations start in Groove. If you need the other direction, ask: your agent reads Fatture in Cloud's API documentation and adds it. ### ### Do I have to build a connector for Groove or Fatture in Cloud? 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 Fatture in Cloud 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.