Integration
Connect JOIN to Hamsa
When Application Created fires in JOIN, your agent runs Add knowledge base item in Hamsa. 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 JOIN and Hamsa 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 JOIN can start in Hamsa
When Application Created in JOIN
then Add knowledge base item in Hamsa
When Job Published in JOIN
then Add transcription job in Hamsa
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 JOIN and Hamsa
Triggers and actions 3 triggers · 37 actions
Trigger
Application CreatedTriggers when a new job application is received in JOIN.
Trigger
Job PublishedTriggers when a job is published (goes online) in JOIN.
Trigger
Job UnpublishedTriggers when a job is taken offline or archived in JOIN.
Action
Add candidate noteAdds a note to a candidate in JOIN.
Action
Add jobCreates a job in JOIN. New jobs are activated and multiposted to job boards automatically.
Action
Add locationCreates a new office location in JOIN that job ads can be assigned to.
Action
Create ApplicationCreates an application for a candidate on a JOIN job, optionally attaching documents such as a CV.
Action
Get applicationReturns one job application, including its candidate, job, attachments, screening answers and pipeline stage.
Action
Get candidateReturns a single JOIN candidate by id, including contact details, tags, consent status and their applications, with notes optionally embedded.
Action
Get jobReturns a single JOIN job by its ID, including its title, status, office and optionally its full content.
Action
Get JobsReturns jobs in your JOIN account, optionally filtered by status, title, country, external id, or creation/update dates.
Action
Get Online JobsReturns the jobs currently published (online) in your JOIN account, optionally filtered by title, country, dates or external id.
Action
List applicationsReturns the applications in your JOIN account, optionally filtered by job, dates, country, hiring state or pipeline stage.
Action
List candidate notesReturns all notes recorded on a candidate in JOIN, including replies.
Action
List candidatesReturns the candidates in your JOIN company, optionally filtered by a name/email search or creation date.
Action
List candidate scorecardsReturns the scorecards submitted for a candidate's job application, including each interviewer's overall recommendation, attribute ratings and question answers.
Action
List locationsReturns the office locations in your JOIN account, optionally filtered by country or city.
Action
Update jobUpdates an existing job's details, such as title, description, office, salary, and application requirements. Fields you leave blank stay unchanged.
Action
Update Job StatusChanges a JOIN job's status to online, offline or archived, and returns the job's ID.
Action
Add knowledge base itemCreate a new knowledge base item for a voice agent.
Action
Add phone numberAdd a phone number for a user.
Action
Add transcription jobCreate a new asynchronous job (e.g. transcription).
Action
Add TTS voiceCreate a new text-to-speech voice.
Action
Add voice agentCreate a new AI voice agent.
Action
Assign phone numberAssign a phone number to a voice agent.
Action
Delete knowledge base itemDelete a knowledge base item by ID.
Action
Delete phone numberDelete a phone number.
Action
Delete TTS voiceDelete a text-to-speech voice by ID.
Action
Get campaignGet a campaign by ID.
Action
Get conversationGet a call conversation record by ID.
Action
Get jobGet a single job's details by ID.
Action
Get voice agentRetrieve a specific voice agent by ID.
Action
Initiate voice agent callInitiate an outbound call with a voice agent via Twilio.
Action
List jobsList jobs.
Action
List knowledge base itemsReturn a list of knowledge base items.
Action
List phone numbersReturn a list of phone numbers for a user.
Action
List TTS voicesRetrieve the list of available TTS voices.
Action
List voice agentsRetrieve a list of the account's voice agents.
Action
Transcribe audioGenerate a speech-to-text transcription from audio (not streamed).
Action
Update voice agentUpdate an existing voice agent's configuration.
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 JOIN
JOIN to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
JOIN to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
JOIN to MailchimpMailchimp marketing automation and email platform.
JOIN to StripeStripe is a payment processing platform for online businesses.
JOIN to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
JOIN to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Hamsa
MySQL to HamsaConnect directly to a MySQL database and run SQL statements from your automations.
TimelinesAI to HamsaTimelinesAI allows you to share access to your personal or business Whatsapp account, integrate it with...
HubSpot to HamsaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to HamsaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to HamsaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to HamsaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Questions
JOIN and Hamsa, answered
What can start an automation from JOIN?
Any of JOIN's 3 triggers in the catalog, including Application Created, Job Published and Job Unpublished. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hamsa when something happens in JOIN?
Any of Hamsa's 21 actions, including Update voice agent, Add knowledge base item, Add phone number and Add transcription job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Hamsa to JOIN?
Hamsa has no triggers in the catalog today, so automations start in JOIN. If you need the other direction, ask: your agent reads Hamsa's API documentation and adds it.
Do I have to build a connector for JOIN or Hamsa?
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 JOIN and Hamsa 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.