Integration
Connect eSignatures and Keplars
When Contract Signed fires in eSignatures, your agent runs Add Contact to Audience in Keplars, or New Audience in Keplars 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 Keplars 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 Keplars can do together
From eSignatures to Keplars
When Contract Signed in eSignatures
then Add Contact to Audience in Keplars
When Contract Withdrawn in eSignatures
then Send Email in Keplars
From Keplars to eSignatures
When New Audience in Keplars
then Add Signer in eSignatures
When New Contact in Audience in Keplars
then Add Template in 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 Keplars
Triggers and actions 6 triggers · 31 actions
Trigger
Contract SignedTriggers when a contract is signed by all signers.
Trigger
Contract WithdrawnFires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn".
Trigger
Signer Declined SignatureFires when a signer declines to sign the contract. Webhook event "Signer declined the signature".
Trigger
Signer Viewed ContractFires when a signer opens/views the contract. Webhook event "Signer viewed the contract".
Action
Add SignerAdd a new signer to an existing contract.
Action
Add TemplateCreate a new reusable contract template.
Action
Create ContractCreates a new contract.
Action
Delete SignerRemove a signer from a contract that has not yet signed.
Action
Delete TemplateDelete a contract template.
Action
Get ContractRetrieve a contract's current status, signer states, and metadata.
Action
Get TemplateRetrieve a contract template's details.
Action
List TemplatesList all contract templates in the account.
Action
Send Contract DraftSend a previously created draft contract to its signers.
Action
Update TemplateUpdate an existing contract template's title or settings.
Action
Withdraw ContractWithdraw (cancel) a contract that has been sent but not fully signed.
Trigger
New AudienceTriggers when a new audience is created.
Trigger
New Contact in AudienceTriggers when a contact is added to an audience.
Action
Add Contact to AudienceAdds a contact to an audience, reusing an existing contact with the same email.
Action
Add DomainAdds a sending domain and returns the DNS records to publish.
Action
Create AudienceCreates a new audience (contact list).
Action
Delete AudienceDeletes an audience.
Action
Delete ContactDeletes a contact.
Action
Delete DomainDeletes a sending domain.
Action
Enroll Contact in AutomationEnrolls a contact, by email, in a Keplars automation.
Action
Get AudienceReturns one audience by its ID.
Action
Get AutomationReturns one automation by its ID.
Action
Get ContactReturns one contact, looked up by ID or email.
Action
List AudiencesReturns the workspace's audiences.
Action
List AutomationsReturns the workspace's automations.
Action
List Contacts in AudienceReturns the contacts in an audience.
Action
List DomainsReturns the workspace's sending domains.
Action
Remove Contact from AutomationRemoves a contact, by email, from a Keplars automation.
Action
Schedule EmailSchedules a transactional email to be sent at a future date and time.
Action
Send EmailQueues a transactional email for delivery through Keplars.
Action
Track EventRecords a custom event for a contact, which can start event-triggered Keplars automations.
Action
Update ContactUpdates a contact's details.
Action
Verify DomainChecks a sending domain's DNS records and returns its verification result.
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 Keplars
HubSpot to KeplarsHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to KeplarsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to KeplarsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to KeplarsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to KeplarsGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to KeplarsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
eSignatures and Keplars, 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 Keplars when something happens in eSignatures?
Any of Keplars's 20 actions, including Create Audience, Send Email, Update Contact and Add Contact to Audience. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Keplars to eSignatures?
Yes. When something happens in Keplars, your agent can act in eSignatures too. This page covers both directions: Keplars's triggers and eSignatures's actions are listed here as well.
Do I have to build a connector for eSignatures or Keplars?
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 Keplars 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.