Integration
Connect Clerk and Leiga
When New User fires in Clerk, your agent runs Create Issue in Leiga, or Updated Issue in Leiga 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 Leiga 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 Leiga can do together
From Clerk to Leiga
When New User in Clerk
then Create Issue in Leiga
From Leiga to 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 Leiga
Triggers and actions 2 triggers · 21 actions
- New User
Triggers when a new user is created in Clerk.
- Ban User
Ban a user, preventing them from signing in.
- Create Invitation
Invite a new user to the Clerk instance by email; they receive a sign-up link.
- Create User
Creates a new user in Clerk.
- Delete User
Deletes a user from Clerk.
- Unban User
Remove a ban on a user, restoring their ability to sign in.
- Update User
Updates an existing user in Clerk.
- Updated Issue
Triggers when an issue is updated in Leiga.
- Add comment
Adds a comment to a Leiga issue or other record, optionally as a reply to an existing comment.
- Add epic
Creates a new epic in a Leiga project.
- Add project
Creates a new project in Leiga from a project template, with a name, leader and optional description.
- Add version
Creates a new version (release) in Leiga with a name, owner, and optional description, start date and estimated release date.
- Create Issue
Creates a new issue in a Leiga project with the issue type and field values you provide.
- Delete issue
Deletes an issue from a Leiga project.
- Find issues by criteria
Searches the issues in a Leiga project matching a summary keyword, status types, field values or date ranges, and returns the matching issues.
- Get issue
Returns the full details of a Leiga issue, including its custom field values, by issue ID.
- Get project
Returns the details of a Leiga project by its ID.
- Get version
Returns the details of a Leiga version, including its name, status and release dates.
- List comments
Returns the comments on a Leiga issue or other item, including replies and attachments.
- List Issue Types
Returns the issue types (such as bug or task) available in a Leiga project.
- List projects
Returns all projects in your Leiga organization with their id, name, key and archived status.
- Update issue
Updates an existing Leiga issue's field values, such as its summary, description, status, priority, assignee or labels.
- Update project
Updates a Leiga project's overview fields, such as its name or start time.
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 Leiga
HubSpot to LeigaHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to LeigaGoogle Sheets
Gmail to LeigaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to LeigaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to LeigaGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to LeigaActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Clerk and Leiga, 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 Leiga when something happens in Clerk?
Any of Leiga's 15 actions, including Create Issue, Update issue, Update project and Add comment. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Leiga to Clerk?
Yes. When something happens in Leiga, your agent can act in Clerk too. This page covers both directions: Leiga's triggers and Clerk's actions are listed here as well.
Do I have to build a connector for Clerk or Leiga?
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 Leiga 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.