Integration
Connect eSignatures and Peach
When Contract Signed fires in eSignatures, your agent runs Add order in Peach, or New or Updated Broadcast in Peach 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 Peach 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 Peach can do together
From eSignatures to Peach
When Contract Signed in eSignatures
then Add order in Peach
When Contract Withdrawn in eSignatures
then Create Contact in Peach
From Peach to eSignatures
When New or Updated Broadcast in Peach
then Add Signer in eSignatures
When New or Updated Broadcast in Peach
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 Peach
Triggers and actions 5 triggers · 26 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 or Updated BroadcastTriggers when a broadcast is created or updated.
Action
Add orderCreates a WhatsApp payment order for a contact, with line items, totals and an optional expiry.
Action
Add WhatsApp templateCreates a new WhatsApp message template in Peach with its header, body, footer and button components.
Action
Create ContactCreates a contact in Peach from a phone number, with optional name, email, language and custom metadata.
Action
Get BroadcastReturns a broadcast's details, including its template, launch settings and delivery stats.
Action
Get OrderReturns an order by its ID, with its amounts, status and line items.
Action
Get WhatsApp TemplateReturns a WhatsApp message template, including its category, language and approval status.
Action
Launch broadcastCreates and launches a WhatsApp broadcast of an approved template to a list of contacts or a saved audience.
Action
List BroadcastsReturns a page of broadcasts, optionally filtered by status or by last-updated time.
Action
List conversationsReturns the account's conversations, optionally filtered by status, escalation, activity type, or recent activity/update time.
Action
List messagesReturns the messages on your Peach account, optionally filtered by direction, date range, conversation, contact phone number or business phone number.
Action
List WhatsApp templatesReturns all WhatsApp message templates in the Peach account, with their status, category, language and components.
Action
Send Template MessageSends an approved WhatsApp template message to a contact, filling the template's variables.
Action
Update ContactUpdates a Peach contact's name, email, language or metadata, found by phone number.
Action
Update conversation statusChanges a conversation's status to open, closed, pending or awaiting customer response, and returns the updated conversation.
Action
Update WhatsApp templateUpdates an existing WhatsApp template's name, language, category, purpose or components.
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 Peach
HubSpot to PeachHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PeachGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PeachGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PeachGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PeachGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PeachMailchimp marketing automation and email platform.
Questions
eSignatures and Peach, 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 Peach when something happens in eSignatures?
Any of Peach's 15 actions, including Create Contact, Send Template Message, Update Contact and Update conversation status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Peach to eSignatures?
Yes. When something happens in Peach, your agent can act in eSignatures too. This page covers both directions: Peach's triggers and eSignatures's actions are listed here as well.
Do I have to build a connector for eSignatures or Peach?
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 Peach 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.