Integration
Connect Clerk and TouchBasePro
When New User fires in Clerk, your agent runs Send Smart Email in TouchBasePro, or New Subscriber in TouchBasePro to Create User in Clerk. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Clerk and TouchBasePro to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Clerk and TouchBasePro can do together
From Clerk to TouchBasePro
When New User in Clerk
then Send Smart Email in TouchBasePro
When New User in Clerk
then Add List in TouchBasePro
From TouchBasePro to Clerk
When New Subscriber in TouchBasePro
then Create User in Clerk
When Updated Subscriber in TouchBasePro
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 TouchBasePro
Triggers and actions 4 triggers · 12 actions
Trigger
New UserTriggers when a new user is created in Clerk.
Action
Ban UserBan a user, preventing them from signing in.
Action
Create InvitationInvite a new user to the Clerk instance by email; they receive a sign-up link.
Action
Create UserCreates a new user in Clerk.
Action
Delete UserDeletes a user from Clerk.
Action
Unban UserRemove a ban on a user, restoring their ability to sign in.
Action
Update UserUpdates an existing user in Clerk.
Trigger
New SubscriberTriggers when a new subscriber is added to a list.
Trigger
Unsubscribed SubscriberTriggers when a subscriber unsubscribes from a list.
Trigger
Updated SubscriberTriggers when an active subscriber on a list is added or has their details changed.
Action
Add ListCreates a new subscriber list in your TouchBasePro account and returns its list id.
Action
Add SubscriberAdds a subscriber to a TouchBasePro email list, or updates their name and custom fields if they are already on it.
Action
Get SubscriberReturns a subscriber's details on a list, including their email address, name, active/inactive state and custom field data.
Action
Send Smart EmailSends a smart transactional email to one or more recipients, filling the email's variables from the data you supply. Returns each recipient with its message ID and status.
Action
Unsubscribe SubscriberUnsubscribes a subscriber from a TouchBasePro list so they no longer receive campaigns sent to it.
Action
Update SubscriberUpdates an existing subscriber on a list, including their email address, name, custom field values and tracking consent.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Clerk
Clerk to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Clerk to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Clerk to AnthropicAnthropic builds Claude, a family of large language models.
Clerk to GoHighLevelAll-in-one sales and marketing platform agencies white-label and resell to their clients — contacts...
Clerk to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
Clerk to ElevenLabsElevenLabs is an AI audio research and deployment company.
More into TouchBasePro
HubSpot to TouchBaseProHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TouchBaseProSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TouchBaseProSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to TouchBaseProGoogle Sheets
Gmail to TouchBaseProGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TouchBaseProGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Clerk and TouchBasePro, 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 TouchBasePro when something happens in Clerk?
Any of TouchBasePro's 6 actions, including Send Smart Email, Update Subscriber, Add List and Add Subscriber. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from TouchBasePro to Clerk?
Yes. When something happens in TouchBasePro, your agent can act in Clerk too. This page covers both directions: TouchBasePro's triggers and Clerk's actions are listed here as well.
Do I have to build a connector for Clerk or TouchBasePro?
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.