Integration
Connect eSignatures and Saasu
When Contract Signed fires in eSignatures, your agent runs Create Contact in Saasu, or New Contact in Saasu 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 Saasu 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)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 Saasu can do together
From eSignatures to Saasu
When Contract Signed in eSignatures
then Create Contact in Saasu
When Contract Withdrawn in eSignatures
then Create Item Invoice in Saasu
From Saasu to eSignatures
When New Contact in Saasu
then Add Signer in eSignatures
When New Contact in Saasu
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 Saasu
Triggers and actions 5 triggers · 32 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 ContactTriggers when a new contact is added to your Saasu file.
Action
Add activityCreates an activity (task, call, meeting, note) in your Saasu file, optionally attached to a contact or transaction.
Action
Add companyCreates a company record in Saasu.
Action
Add itemCreates an inventory or combo item in Saasu.
Action
Add journalCreates a manual journal entry with debit and credit lines in a Saasu file.
Action
Create ContactCreates a new contact (person) in your Saasu file and returns its id.
Action
Create Item InvoiceCreates an item-layout invoice, quote or order in Saasu with inventory item line items.
Action
Create Service InvoiceCreates a service-layout sale or purchase invoice in Saasu, with line items described by account and amount.
Action
Delete contactDeletes a contact from your Saasu file.
Action
Delete invoiceDeletes a sale or purchase invoice from the Saasu file.
Action
Delete itemDeletes an inventory item from the Saasu file.
Action
Email invoiceEmails a Saasu invoice to the email address you specify.
Action
Find accountsReturns the accounts in your Saasu chart of accounts, filtered by type, status, bank-account flag or header account.
Action
Find companiesReturns the companies in your Saasu file whose name matches, optionally limited to a last-modified date range.
Action
Find ContactFinds Saasu contacts matching an email, name, company or other criteria and returns the matching contacts.
Action
Find itemsReturns the inventory and combo items whose code or description matches the search text.
Action
Get contactReturns a single Saasu contact by its ID.
Action
Get invoiceReturns a single Saasu invoice (sale or purchase) by its ID, including line items and totals.
Action
Get journalReturns a single journal transaction, including its date, reference, summary and journal line items.
Action
Update contactUpdates an existing contact in Saasu, such as their name, email, phone numbers, addresses and customer/supplier flags.
Action
Update invoiceUpdates an existing Saasu sale or purchase invoice, replacing its details and line items.
Action
Update itemUpdates an existing inventory or combo item in Saasu, such as its code, description, prices, accounts and tax codes.
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
eSignatures to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Saasu
HubSpot to SaasuHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to SaasuGoogle Sheets
Gmail to SaasuGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SaasuGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SaasuGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to SaasuMailchimp marketing automation and email platform.
Questions
eSignatures and Saasu, 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 Saasu when something happens in eSignatures?
Any of Saasu's 21 actions, including Create Contact, Create Item Invoice, Create Service Invoice and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Saasu to eSignatures?
Yes. When something happens in Saasu, your agent can act in eSignatures too. This page covers both directions: Saasu's triggers and eSignatures's actions are listed here as well.
Do I have to build a connector for eSignatures or Saasu?
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 Saasu 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.