# Connect Groove and SQL Server

When **Customer Added** fires in [Groove](https://apiant.ai/connections/groove), your agent runs **Add Row** in [SQL Server](https://apiant.ai/connections/sql-server), or **New or Updated Row** in SQL Server 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 SQL Server **4** triggers SQL Server **7** 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 SQL Server to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

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 SQL Server can do together

### From Groove to SQL Server

- When **Customer Added** in Groove then **Add Row** in SQL Server
- When **Note Added** in Groove then **Update Row** in SQL Server

### From SQL Server to Groove

- When **New or Updated Row** in SQL Server then **Add label to ticket** in Groove
- When **New Row** in SQL Server 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 SQL Server

## Triggers and actions 13 triggers · 22 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 or Updated Row**

Triggers when a new row is added or modified.

- Trigger

**New or Updated Row (Custom Query)**

Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database.

- Trigger

**New Row**

Triggers when you add a new row.

- Trigger

**New Table**

Fires when a new table appears in the connected SQL Server database.

- Action

**Add Row**

Add one row to a table on the connected SQL Server database.

- Action

**Delete Row**

Delete the rows in a table whose chosen column equals a value.

- Action

**Find Row**

Find the first row in a table whose chosen column matches a value.

- Action

**Find Rows via Custom Query**

Runs a SELECT statement you write against the connected SQL Server database and returns every row it matches.

- Action

**Find Row via Custom Query**

Runs a SELECT statement you write against the connected SQL Server database and returns the first row it matches.

- Action

**Run Custom Statement**

Runs a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.

- Action

**Update Row**

Change column values on every row of a table whose chosen column matches a value.

## Each app on its own

- [ **Groove** The simple helpdesk for SaaS and eCommerce businesses.](https://apiant.ai/connections/groove)
- [ **SQL Server** Connect directly to a Microsoft SQL Server database and run SQL statements from your automations.](https://apiant.ai/connections/sql-server)

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 SQL Server

- [ **HubSpot to SQL Server** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sql-server)
- [ **Slack to SQL Server** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sql-server)
- [ **Mailchimp to SQL Server** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-sql-server)
- [ **Shopify to SQL Server** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/shopify-to-sql-server)
- [ **QuickBooks Online to SQL Server** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/quickbooks-online-to-sql-server)
- [ **Pipedrive to SQL Server** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-sql-server)

Questions

## Groove and SQL Server, 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 SQL Server when something happens in Groove?

Any of SQL Server's 7 actions, including Update Row, Add Row, Find Row and Find Rows via Custom Query. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from SQL Server to Groove?

Yes. When something happens in SQL Server, your agent can act in Groove too. This page covers both directions: SQL Server's triggers and Groove's actions are listed here as well.

###

### Do I have to build a connector for Groove or SQL Server?

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.

###

### 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.
