Integration
Connect Clerk and Rossum
When New User fires in Clerk, your agent runs Upload a Document in Rossum, or Document Export in Rossum 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 Rossum 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)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 Rossum can do together
From Clerk to Rossum
When New User in Clerk
then Upload a Document in Rossum
When New User in Clerk
then Get document in Rossum
From Rossum to Clerk
When Document Export in Rossum
then Create User in Clerk
When Document Export in Rossum
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 Rossum
Triggers and actions 2 triggers · 15 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
Document ExportTriggers when a document is exported in Rossum.
Action
Add queueCreate a queue.
Action
Confirm annotationConfirm an annotation.
Action
Delete annotationDelete an annotation.
Action
Get annotationRetrieve one annotation (extracted document data) by id.
Action
Get documentRetrieve document metadata by id.
Action
Get queueRetrieve a queue by id.
Action
Start Annotationmoves an annotation (e.g. to_review) into reviewing status so it can be confirmed; returns the annotation and session timeout.
Action
Update annotationUpdate an annotation (e.g. metadata, status).
Action
Upload a DocumentUploads a document to one of Rossum queues
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 Rossum
HubSpot to RossumHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to RossumGoogle Sheets
Gmail to RossumGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to RossumGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to RossumGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to RossumMailchimp marketing automation and email platform.
Questions
Clerk and Rossum, 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 Rossum when something happens in Clerk?
Any of Rossum's 9 actions, including Update annotation, Upload a Document, Add queue and Confirm annotation. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Rossum to Clerk?
Yes. When something happens in Rossum, your agent can act in Clerk too. This page covers both directions: Rossum's triggers and Clerk's actions are listed here as well.
Do I have to build a connector for Clerk or Rossum?
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 Rossum 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.