--- title: "Connect Himalayas and Clerk - APIANT.ai" description: "When \"New job posted\" fires in Himalayas, your agent runs \"Create User\" in Clerk, or \"New User\" in Clerk to \"Find Jobs by Criteria\" in Himalayas." canonical: "https://apiant.ai/connect/himalayas-to-clerk" --- # Connect Himalayas and Clerk When **New job posted** fires in [Himalayas](https://apiant.ai/connections/himalayas), your agent runs **Create User** in [Clerk](https://apiant.ai/connections/clerk), or **New User** in Clerk to **Find Jobs by Criteria** in Himalayas. Describe the whole flow and it is built, tested on every scenario and kept running. Himalayas **1** trigger Himalayas **2** actions Clerk **1** trigger Clerk **6** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Himalayas and Clerk to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.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 Himalayas and Clerk can do together ### From Himalayas to Clerk - When **New job posted** in Himalayas then **Create User** in Clerk - When **New job posted** in Himalayas then **Update User** in Clerk ### From Clerk to Himalayas - When **New User** in Clerk then **Find Jobs by Criteria** in Himalayas - When **New User** in Clerk then **List Jobs** in Himalayas 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 Himalayas and Clerk ## Triggers and actions 2 triggers ยท 8 actions - Trigger **New job posted** Fires when a new remote job is posted to Himalayas. - Action **Find Jobs by Criteria** Search Himalayas remote jobs with filters (e.g. keyword, category, location). - Action **List Jobs** Browse the full Himalayas remote jobs feed. - 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. ## Each app on its own - [ **Himalayas** Remote job board and search engine](https://apiant.ai/connections/himalayas) - [ **Clerk** Clerk is a user authentication and management platform that lets developers add sign-in, profiles, and...](https://apiant.ai/connections/clerk) Reviews ## What our customers say ## More from Himalayas - [ **Himalayas to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/himalayas-to-google-calendar) - [ **Himalayas to Sent** Sent is a multichannel messaging platform for sending SMS, WhatsApp, and RCS messages from templates, with...](https://apiant.ai/connect/himalayas-to-sent) - [ **Himalayas to timeBuzzer** timeBuzzer is a simple time tracker and timesheet app to track hours worked across projects in real time.](https://apiant.ai/connect/himalayas-to-timebuzzer) - [ **Himalayas to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/himalayas-to-hubspot) - [ **Himalayas to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/himalayas-to-salesforce) - [ **Himalayas to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/himalayas-to-slack) ## More into Clerk - [ **Brevo to Clerk** Brevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...](https://apiant.ai/connect/brevo-to-clerk) - [ **Instagram to Clerk** Instagram is a social media platform for sharing photos, videos, and stories.](https://apiant.ai/connect/instagram-to-clerk) - [ **Kit to Clerk** Kit is an email marketing platform for professional bloggers.](https://apiant.ai/connect/kit-to-clerk) - [ **Postman to Clerk** Postman is a platform for building and testing APIs.](https://apiant.ai/connect/postman-to-clerk) - [ **Telegram to Clerk** Telegram is a cloud-based instant messaging and voice over IP service developed by Telegram Messenger LLP.](https://apiant.ai/connect/telegram-to-clerk) - [ **HubSpot to Clerk** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-clerk) Questions ## Himalayas and Clerk, answered ### ### What can start an automation from Himalayas? Any of Himalayas's 1 trigger in the catalog, including New job posted. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Clerk when something happens in Himalayas? Any of Clerk's 6 actions, including Create Invitation, Create User, Update User and Ban User. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Clerk to Himalayas? Yes. When something happens in Clerk, your agent can act in Himalayas too. This page covers both directions: Clerk's triggers and Himalayas's actions are listed here as well. ### ### Do I have to build a connector for Himalayas or Clerk? 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 Himalayas and Clerk 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.