Integration
Connect Clerk and Consent Kit
When New User fires in Clerk, your agent runs Get Project in Consent Kit, or Consent Updated in Consent Kit 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 Consent Kit to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Consent Kit can do together
From Clerk to Consent Kit
When New User in Clerk
then Get Project in Consent Kit
When New User in Clerk
then Create Data Link in Consent Kit
From Consent Kit to Clerk
When Consent Updated in Consent Kit
then Create User in Clerk
When New Consent in Consent Kit
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 Consent Kit
Triggers and actions 7 triggers · 24 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
Consent AgreedTriggers when a participant agrees to a consent in Consent Kit.
Trigger
Consent DeclinedTriggers when a participant refuses a consent in Consent Kit.
Trigger
Consent UpdatedTriggers when a Consent Kit consent is created or updated.
Trigger
Data LinkedTriggers when new data is linked to a Consent Kit participant.
Trigger
New ConsentTriggers when a participant agrees to or refuses a consent in Consent Kit.
Trigger
Participant CreatedTriggers when a participant is added to a Consent Kit study, with their email and first name.
Action
Create Data LinkLinks data stored at a URL (a recording, notes, a file) to a Consent Kit participant.
Action
Create ParticipantAdds a participant to a Consent Kit study; Consent Kit uses the email to send them the consent form.
Action
Create StudyCreates a new study inside a Consent Kit project.
Action
Delete Data LinkDeletes (unlinks) a data link from its Consent Kit participant.
Action
Delete StudyDeletes a Consent Kit study.
Action
Get ConsentReturns one Consent Kit consent by ID: whether it was agreed or refused, the permissions given, and the participant.
Action
Get PanelReturns one Consent Kit panel by its ID, including how many panellists it has.
Action
Get ParticipantReturns one Consent Kit participant by ID, optionally with their email and first name.
Action
Get ProjectReturns one Consent Kit project by its ID.
Action
Get StudyReturns one Consent Kit study by its ID.
Action
List ConsentsReturns a page of consents in your Consent Kit organisation, optionally only agreed or only refused ones.
Action
List Data LinksReturns a page of the data links in your Consent Kit organisation.
Action
List FieldsReturns the custom field definitions configured for your Consent Kit organisation, used to read panellist properties.
Action
List Panel PanellistsReturns the opted-in panellists of a Consent Kit panel, optionally with their email, name and custom field values.
Action
List PanelsReturns a page of your organisation's Consent Kit panels.
Action
List ParticipantsReturns a page of your organisation's Consent Kit participants, optionally with their email and first name.
Action
List ProjectsReturns a page of your organisation's Consent Kit projects, newest first.
Action
List StudiesReturns a page of your organisation's Consent Kit studies.
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 Consent Kit
ActiveCampaign to Consent KitActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to Consent KitOrganize anything with Airtable, a modern database created for everyone.
Asana to Consent KitAsana is a collaborative information manager for workspace.
ClickUp to Consent KitClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to Consent KitBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to Consent KitCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
Clerk and Consent Kit, 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 Consent Kit when something happens in Clerk?
Any of Consent Kit's 18 actions, including Create Data Link, Create Participant, Create Study and Get Consent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Consent Kit to Clerk?
Yes. When something happens in Consent Kit, your agent can act in Clerk too. This page covers both directions: Consent Kit's triggers and Clerk's actions are listed here as well.
Do I have to build a connector for Clerk or Consent Kit?
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 Consent Kit 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.