Integration
Connect Clust to Hamsa
When New Application Closed fires in Clust, 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 Clust 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)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 Clust can start in Hamsa
When New Application Closed in Clust
then Add knowledge base item in Hamsa
When New Application Created in Clust
then Add phone number 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 Clust and Hamsa
Triggers and actions 8 triggers · 47 actions
Trigger
New Application ClosedTriggers when an application is closed.
Trigger
New Application CreatedTriggers when a new application is created.
Trigger
New Application LateTriggers when an application passes its deadline.
Trigger
New Application Progress Stage ChangedTriggers when an application moves to a different stage.
Trigger
New Application SubmittedTriggers when an application is submitted.
Trigger
New ContactTriggers when a contact is created.
Trigger
New or Updated ApplicationTriggers when an application is created or changed.
Trigger
New or Updated Application ItemTriggers when an item of the chosen application is added or changes status (submitted, approved, completed).
Action
Approve Application ItemApproves an application item.
Action
Assign a New Stakeholder to RoleAdds a stakeholder to a role on an existing application.
Action
Close ApplicationCloses an application.
Action
Create ApplicationCreates an application from a template and invites the contact to fill it in.
Action
Create CompanyCreates a company.
Action
Create ContactCreates a contact.
Action
Create TagCreates a tag.
Action
Delete ApplicationDeletes an application.
Action
Delete ContactDeletes a contact.
Action
Find ApplicationsReturns applications matching a status, contact email, external ID or keyword.
Action
Find CompaniesReturns companies matching a keyword.
Action
Find ContactsReturns contacts matching an email or keyword.
Action
Get ApplicationReturns one application by ID.
Action
Get Application ItemReturns one application item with its content.
Action
Get CompanyReturns one company by ID.
Action
Get ContactReturns one contact by ID.
Action
Get TemplateReturns one application template by ID.
Action
List Application ItemsReturns the items (documents, forms, tasks) of an application.
Action
List TagsReturns the team's tags.
Action
List Team MembersReturns the team's users.
Action
List TemplatesReturns the application templates.
Action
Reopen ApplicationReopens a closed application.
Action
Submit ApplicationSubmits an application on the client's behalf.
Action
Update ApplicationUpdates an application's title, stage, deadline, external ID or contact details.
Action
Update ContactUpdates a contact.
Action
Update Form FieldSets the answer of one field in a form item of an application.
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 Clust
Clust to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Clust to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Clust to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Clust to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Clust to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Clust to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
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
Clust and Hamsa, answered
What can start an automation from Clust?
Any of Clust's 8 triggers in the catalog, including New Application Closed, New Application Created, New Application Late and New Application Progress Stage Changed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hamsa when something happens in Clust?
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 Clust?
Hamsa has no triggers in the catalog today, so automations start in Clust. 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 Clust 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 Clust 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.