Integration
Connect eSignatures to Hamsa
When something happens in eSignatures, your agent does the next thing in Hamsa. Describe it 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 eSignatures 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 eSignatures can start in Hamsa
When Contract Signed in eSignatures
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 eSignatures and Hamsa
Triggers and actions 4 triggers ยท 32 actions
- Contract Signed
Triggers when a contract is signed by all signers.
- Contract Withdrawn
Fires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn".
- Signer Declined Signature
Fires when a signer declines to sign the contract. Webhook event "Signer declined the signature".
- Signer Viewed Contract
Fires when a signer opens/views the contract. Webhook event "Signer viewed the contract".
- Add Signer
Add a new signer to an existing contract.
- Add Template
Create a new reusable contract template.
- Create Contract
Creates a new contract.
- Delete Signer
Remove a signer from a contract that has not yet signed.
- Delete Template
Delete a contract template.
- Get Contract
Retrieve a contract's current status, signer states, and metadata.
- Get Template
Retrieve a contract template's details.
- List Templates
List all contract templates in the account.
- Send Contract Draft
Send a previously created draft contract to its signers.
- Update Template
Update an existing contract template's title or settings.
- Withdraw Contract
Withdraw (cancel) a contract that has been sent but not fully signed.
- Add knowledge base item
Create a new knowledge base item for a voice agent.
- Add phone number
Add a phone number for a user.
- Add transcription job
Create a new asynchronous job (e.g. transcription).
- Add TTS voice
Create a new text-to-speech voice.
- Add voice agent
Create a new AI voice agent.
- Assign phone number
Assign a phone number to a voice agent.
- Delete knowledge base item
Delete a knowledge base item by ID.
- Delete phone number
Delete a phone number.
- Delete TTS voice
Delete a text-to-speech voice by ID.
- Get campaign
Get a campaign by ID.
- Get conversation
Get a call conversation record by ID.
- Get job
Get a single job's details by ID.
- Get voice agent
Retrieve a specific voice agent by ID.
- Initiate voice agent call
Initiate an outbound call with a voice agent via Twilio.
- List jobs
List jobs.
- List knowledge base items
Return a list of knowledge base items.
- List phone numbers
Return a list of phone numbers for a user.
- List TTS voices
Retrieve the list of available TTS voices.
- List voice agents
Retrieve a list of the account's voice agents.
- Transcribe audio
Generate a speech-to-text transcription from audio (not streamed).
- Update voice agent
Update 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 eSignatures
eSignatures to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
eSignatures to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
eSignatures to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
eSignatures to Google SheetsGoogle Sheets
eSignatures to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
eSignatures to MailchimpMailchimp marketing automation and email platform.
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...
Questions
eSignatures and Hamsa, answered
What can start an automation from eSignatures?
Any of eSignatures's 4 triggers in the catalog, including Contract Signed, Contract Withdrawn, Signer Declined Signature and Signer Viewed Contract. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Hamsa when something happens in eSignatures?
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 eSignatures?
Hamsa has no triggers in the catalog today, so automations start in eSignatures. 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 eSignatures 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.