# Connect Clerk and Reply

When **New User** fires in [Clerk](https://apiant.ai/connections/clerk), your agent runs **Add contact list** in [Reply](https://apiant.ai/connections/reply), or **New Email Opened** in Reply 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 Reply **7** triggers Reply **16** 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 Reply 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 Clerk and Reply can do together

### From Clerk to Reply

- When **New User** in Clerk then **Add contact list** in Reply
- When **New User** in Clerk then **Add note to contact** in Reply

### From Reply to Clerk

- When **New Email Opened** in Reply then **Create User** in Clerk
- When **New Emails Sent** in Reply 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 Reply

## Triggers and actions 8 triggers · 22 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

**Inbox Category Set for Reply**

Triggers when an email reply in Reply is given an inbox category, automatically or by a user.

- Trigger

**New Email Opened**

Triggers when a contact opens a tracked email sent from Reply.

- Trigger

**New Emails Sent**

Triggers when Reply sends an email from a sequence step.

- Trigger

**New Link Clicked**

Triggers when a recipient clicks a tracked link in an email sent from Reply.

- Trigger

**New Person Bounce**

Triggers when an email sent from Reply bounces or is rejected by the recipient's mail server.

- Trigger

**New Person Opt Out**

Triggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact).

- Trigger

**Prospect Finished**

Triggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually.

- Action

**Add contact list**

Creates a new contact list in Reply, optionally shared with your team.

- Action

**Add note to contact**

Adds a note to a contact's timeline in Reply.

- Action

**Add sequence**

Creates a new sequence in Reply with its steps, schedule, sending accounts and settings.

- Action

**Create\Update Person**

Creates a Reply contact, or updates the existing contact with the same email address.

- Action

**Delete contact**

Deletes a contact from your Reply account.

- Action

**Find contacts by criteria**

Returns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step.

- Action

**Get contact**

Returns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields.

- Action

**Get sequence**

Returns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps.

- Action

**List contact lists**

Returns the contact lists you own plus those shared with your team, optionally filtered by name.

- Action

**List contacts**

Returns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL.

- Action

**List inbox categories**

Returns the inbox categories you can file conversations under.

- Action

**List Sequence Contacts**

Returns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status.

- Action

**List sequences**

Returns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name.

- Action

**Mark as Finished**

Marks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps.

- Action

**Remove Person From Campaign**

Removes a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account.

- Action

**Send Test Webhook Event**

Sends a test event from an existing Reply webhook subscription to its configured URL.

## 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)
- [ **Reply** Reply is a sales automation platform that puts outreach on autopilot, while still making each communication...](https://apiant.ai/connections/reply)

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 Reply

- [ **HubSpot to Reply** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-reply)
- [ **Google Sheets to Reply** Google Sheets](https://apiant.ai/connect/google-sheets-to-reply)
- [ **Gmail to Reply** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-reply)
- [ **Google Calendar to Reply** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-reply)
- [ **Google Drive to Reply** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-reply)
- [ **Mailchimp to Reply** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-reply)

Questions

## Clerk and Reply, 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 Reply when something happens in Clerk?

Any of Reply's 16 actions, including Create\Update Person, Send Test Webhook Event, Add contact list and Add note to contact. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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.
