Integration
Connect eSignatures and Kustomer
When Contract Signed fires in eSignatures, your agent runs Add message in Kustomer, or Conversation Created in Kustomer to Add Signer in eSignatures. 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 eSignatures and Kustomer 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 eSignatures and Kustomer can do together
From eSignatures to Kustomer
When Contract Signed in eSignatures
then Add message in Kustomer
From Kustomer to eSignatures
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 Kustomer
Triggers and actions 10 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.
- Conversation Created
Triggers when a new conversation is created in Kustomer.
- Conversation Updated
Triggers when a Kustomer conversation is created or updated.
- Customer Created
Triggers when a new customer is created in Kustomer.
- Customer Updated
Triggers when a Kustomer customer is created or updated.
- Message Created
Triggers when a new message is sent or received in Kustomer.
- Message Updated
Triggers when a Kustomer message is created or updated.
- Add custom object
Creates a new custom object (KObject) of the chosen custom object type in Kustomer.
- Add message
Adds a message to an existing Kustomer conversation; the message belongs to the conversation's customer.
- Create Company
Creates a company in Kustomer that customers can be linked to.
- Create Conversation
Creates a new conversation for a Kustomer customer, with an optional name, status and tags.
- Create Customer
Creates a new customer in Kustomer with a name, email, phone and optional external ID.
- Create Notes
Adds an internal note to a Kustomer conversation. Notes are visible to agents only, not the customer.
- Create User
Invites a new agent user to your Kustomer org by name and email.
- Delete Customer
Deletes a Kustomer customer by ID.
- Find Conversation
Finds a Kustomer conversation by the external ID your own system gave it.
- Find Customer
Finds a Kustomer customer by email address and returns their ID, name and phone.
- Find custom objects by criteria
Returns the custom objects (KObjects) of a chosen Klass, optionally only those after a given date, sorted and limited to selected fields.
- Find User
Finds a Kustomer agent user by email address.
- Get Company
Returns one Kustomer company by ID.
- Get Conversation
Returns one Kustomer conversation by ID, with its subject, status, customer and timestamps.
- Get Customer
Returns one Kustomer customer by ID, with name, emails, phones and timestamps.
- Get message
Returns a single Kustomer message by its ID, including its attributes and related conversation and customer.
- Get user
Returns a Kustomer user (agent) by their ID, including name, email and other profile attributes.
- List teams
Returns the teams in your Kustomer organization, optionally filtered by role group or deleted status.
- Update company
Updates an existing Kustomer company's name, external ID, emails, phones, tags and custom attributes.
- Update Conversation
Updates a Kustomer conversation's subject or status. Only the fields you fill in are changed.
- Update Customer
Updates an existing Kustomer customer's name, email, phone or external ID. Only the fields you fill in are changed.
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 PexafySemantic image search across 9+ free stock photo sources with a unified JSON schema
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
eSignatures to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Kustomer
Gmail to KustomerGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Drive to KustomerGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to KustomerActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
eSignatures and Kustomer, 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 Kustomer when something happens in eSignatures?
Any of Kustomer's 21 actions, including Create Company, Create Conversation, Create Customer and Create Notes. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Kustomer to eSignatures?
Yes. When something happens in Kustomer, your agent can act in eSignatures too. This page covers both directions: Kustomer's triggers and eSignatures's actions are listed here as well.
Do I have to build a connector for eSignatures or Kustomer?
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 Kustomer 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.