Integration
Connect Jodoo to Hamsa
When New Record or Workflow fires in Jodoo, 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 Jodoo 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 Jodoo can start in Hamsa
When New Record or Workflow in Jodoo
then Add knowledge base item in Hamsa
When New Record or Workflow in Jodoo
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 Jodoo and Hamsa
Triggers and actions 1 trigger · 26 actions
Trigger
New Record or WorkflowFires when a new record (including a workflow record) is submitted to the chosen Jodoo form.
Action
Delete RecordDeletes a record by specifying the Data ID. The Instance ID equals the Data ID when the record is in a workflow form.
Action
Find RecordFinds a record in the form with the Data ID. The Instance ID equals the Data ID when the record is in a workflow form.
Action
List appsList Jodoo apps accessible to the API key.
Action
List formsList forms in a Jodoo app.
Action
Update RecordUpdates the values of specific fields in a record.
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 Jodoo
Jodoo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Jodoo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Jodoo to MailchimpMailchimp marketing automation and email platform.
Jodoo to StripeStripe is a payment processing platform for online businesses.
Jodoo to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Jodoo 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
Questions
Jodoo and Hamsa, answered
What can start an automation from Jodoo?
Any of Jodoo's 1 trigger in the catalog, including New Record or Workflow. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hamsa when something happens in Jodoo?
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 Jodoo?
Hamsa has no triggers in the catalog today, so automations start in Jodoo. 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 Jodoo 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 Jodoo 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.