---
title: "Connect Clerk and Groove - APIANT.ai"
description: "When \"New User\" fires in Clerk, your agent runs \"Add label to ticket\" in Groove, or \"Customer Added\" in Groove to \"Create User\" in Clerk."
canonical: "https://apiant.ai/connect/clerk-to-groove"
---

# Connect Clerk and Groove

When **New User** fires in [Clerk](https://apiant.ai/connections/clerk), your agent runs **Add label to ticket** in [Groove](https://apiant.ai/connections/groove), or **Customer Added** in Groove to **Create User** in Clerk. Describe the whole flow and it is built, tested on every scenario and kept running.

Clerk **1** trigger Clerk **6** actions Groove **9** triggers Groove **15** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Clerk and Groove 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 Clerk and Groove can do together

### From Clerk to Groove

- When **New User** in Clerk then **Add label to ticket** in Groove
- When **New User** in Clerk then **Add message** in Groove

### From Groove to Clerk

- When **Customer Added** in Groove then **Create User** in Clerk
- When **Note Added** in Groove then **Update User** in Clerk

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 Clerk and Groove

## Triggers and actions 10 triggers · 21 actions

- Trigger

**New User**

Triggers when a new user is created in Clerk.

- Action

**Ban User**

Ban a user, preventing them from signing in.

- Action

**Create Invitation**

Invite a new user to the Clerk instance by email; they receive a sign-up link.

- Action

**Create User**

Creates a new user in Clerk.

- Action

**Delete User**

Deletes a user from Clerk.

- Action

**Unban User**

Remove a ban on a user, restoring their ability to sign in.

- Action

**Update User**

Updates an existing user in Clerk.

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

## Each app on its own

- [ **Clerk** Clerk is a user authentication and management platform that lets developers add sign-in, profiles, and...](https://apiant.ai/connections/clerk)
- [ **Groove** The simple helpdesk for SaaS and eCommerce businesses.](https://apiant.ai/connections/groove)

Reviews

## What our customers say

## More from Clerk

- [ **Clerk to LinkedIn** LinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...](https://apiant.ai/connect/clerk-to-linkedin)
- [ **Clerk to Facebook** Facebook is a social media and advertising platform used by individuals and businesses to connect, share...](https://apiant.ai/connect/clerk-to-facebook)
- [ **Clerk to Anthropic** Anthropic builds Claude, a family of large language models.](https://apiant.ai/connect/clerk-to-anthropic)
- [ **Clerk to GoHighLevel** All-in-one sales and marketing platform agencies white-label and resell to their clients — contacts...](https://apiant.ai/connect/clerk-to-gohighlevel)
- [ **Clerk to Supabase** Supabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...](https://apiant.ai/connect/clerk-to-supabase)
- [ **Clerk to ElevenLabs** ElevenLabs is an AI audio research and deployment company.](https://apiant.ai/connect/clerk-to-elevenlabs)

## More into Groove

- [ **Google Sheets to Groove** Google Sheets](https://apiant.ai/connect/google-sheets-to-groove)
- [ **Gmail to Groove** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-groove)
- [ **Google Calendar to Groove** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-groove)
- [ **Google Drive to Groove** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-groove)
- [ **ActiveCampaign to Groove** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-groove)
- [ **Airtable to Groove** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-groove)

Questions

## Clerk and Groove, answered

###

### What can start an automation from Clerk?

Any of Clerk's 1 trigger in the catalog, including New User. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Groove when something happens in Clerk?

Any of Groove's 15 actions, including Create New Ticket, Update customer, Add label to ticket and Add message. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Groove to Clerk?

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

###

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

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 Clerk and Groove 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.
