Build solutions, not workarounds.
What do you want Rendobar and Hamsa to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Rendobar can start in Hamsa
When Job completed in Rendobar
then Add transcription job in Hamsa
When Job completed in Rendobar
then Add knowledge base item 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 Rendobar and Hamsa
Triggers and actions 1 trigger ยท 33 actions
Trigger
Job completedFires when a job finishes (success/failure). Backed by the vendor's webhook endpoint delivery mechanism, filtered to job-completion events.
Action
Add assetInitialize an asset (media file) upload.
Action
Add jobCreate a media processing job (transcode, caption, watermark, etc).
Action
Cancel jobCancel a running job.
Action
Delete assetDelete an asset by id.
Action
Get assetGet details of an asset by id.
Action
Get jobGet details of a job by id.
Action
Get job logsGet execution logs for a job.
Action
Get job outputGet the download URL/content for a completed job's output.
Action
List assetsList uploaded assets.
Action
List jobsList jobs for the account.
Action
List job typesList available job types (transcode, caption, watermark, etc).
Action
List modelsList available generation/processing models.
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 Rendobar
Rendobar to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Rendobar to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Rendobar to StripeStripe is a payment processing platform for online businesses.
Rendobar to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Rendobar to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Rendobar to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
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
Questions
Rendobar and Hamsa, answered
What can start an automation from Rendobar?
Any of Rendobar's 1 trigger in the catalog, including Job completed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hamsa when something happens in Rendobar?
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 Rendobar?
Hamsa has no triggers in the catalog today, so automations start in Rendobar. 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 Rendobar 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.
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.