--- title: "Connect eSignatures to Hamsa - APIANT.ai" description: "When \"Contract Signed\" fires in eSignatures, your agent runs \"Add knowledge base item\" in Hamsa." canonical: "https://apiant.ai/connect/esignatures-to-hamsa" --- # Connect eSignatures to Hamsa When **Contract Signed** fires in [eSignatures](https://apiant.ai/connections/esignatures), your agent runs **Add knowledge base item** in [Hamsa](https://apiant.ai/connections/hamsa). Describe the whole flow and it is built, tested on every scenario and kept running. eSignatures **4** triggers eSignatures **11** actions Hamsa **21** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want eSignatures and Hamsa to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What eSignatures can start in Hamsa - When **Contract Signed** in eSignatures then **Add knowledge base item** in Hamsa - When **Contract Withdrawn** in eSignatures 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 eSignatures and Hamsa ## Triggers and actions 4 triggers ยท 32 actions - Trigger **Contract Signed** Triggers when a contract is signed by all signers. - Trigger **Contract Withdrawn** Fires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn". - Trigger **Signer Declined Signature** Fires when a signer declines to sign the contract. Webhook event "Signer declined the signature". - Trigger **Signer Viewed Contract** Fires when a signer opens/views the contract. Webhook event "Signer viewed the contract". - Action **Add Signer** Add a new signer to an existing contract. - Action **Add Template** Create a new reusable contract template. - Action **Create Contract** Creates a new contract. - Action **Delete Signer** Remove a signer from a contract that has not yet signed. - Action **Delete Template** Delete a contract template. - Action **Get Contract** Retrieve a contract's current status, signer states, and metadata. - Action **Get Template** Retrieve a contract template's details. - Action **List Templates** List all contract templates in the account. - Action **Send Contract Draft** Send a previously created draft contract to its signers. - Action **Update Template** Update an existing contract template's title or settings. - Action **Withdraw Contract** Withdraw (cancel) a contract that has been sent but not fully signed. - Action **Add knowledge base item** Create a new knowledge base item for a voice agent. - Action **Add phone number** Add a phone number for a user. - Action **Add transcription job** Create a new asynchronous job (e.g. transcription). - Action **Add TTS voice** Create a new text-to-speech voice. - Action **Add voice agent** Create a new AI voice agent. - Action **Assign phone number** Assign a phone number to a voice agent. - Action **Delete knowledge base item** Delete a knowledge base item by ID. - Action **Delete phone number** Delete a phone number. - Action **Delete TTS voice** Delete a text-to-speech voice by ID. - Action **Get campaign** Get a campaign by ID. - Action **Get conversation** Get a call conversation record by ID. - Action **Get job** Get a single job's details by ID. - Action **Get voice agent** Retrieve a specific voice agent by ID. - Action **Initiate voice agent call** Initiate an outbound call with a voice agent via Twilio. - Action **List jobs** List jobs. - Action **List knowledge base items** Return a list of knowledge base items. - Action **List phone numbers** Return a list of phone numbers for a user. - Action **List TTS voices** Retrieve the list of available TTS voices. - Action **List voice agents** Retrieve a list of the account's voice agents. - Action **Transcribe audio** Generate a speech-to-text transcription from audio (not streamed). - Action **Update voice agent** Update an existing voice agent's configuration. ## Each app on its own - [ **eSignatures** ESignatures.io is a tool used for signing mobile friendly contracts over the web.](https://apiant.ai/connections/esignatures) - [ **Hamsa** AI voice agent platform with lifelike avatars, RAG-powered conversations, and API/SDK for calls, CRM, and...](https://apiant.ai/connections/hamsa) Reviews ## What our customers say ## More from eSignatures - [ **eSignatures to Pexafy** Semantic image search across 9+ free stock photo sources with a unified JSON schema](https://apiant.ai/connect/esignatures-to-pexafy) - [ **eSignatures to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/esignatures-to-hubspot) - [ **eSignatures to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/esignatures-to-salesforce) - [ **eSignatures to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/esignatures-to-slack) - [ **eSignatures to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/esignatures-to-google-sheets) - [ **eSignatures to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/esignatures-to-google-calendar) ## More into Hamsa - [ **MySQL to Hamsa** Connect directly to a MySQL database and run SQL statements from your automations.](https://apiant.ai/connect/mysql-to-hamsa) - [ **TimelinesAI to Hamsa** TimelinesAI allows you to share access to your personal or business Whatsapp account, integrate it with...](https://apiant.ai/connect/timelinesai-to-hamsa) - [ **HubSpot to Hamsa** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-hamsa) - [ **Salesforce to Hamsa** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-hamsa) - [ **Slack to Hamsa** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-hamsa) - [ **Google Sheets to Hamsa** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-hamsa) 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. ### ### Can my AI client use eSignatures 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.