Integration
Connect Amo Crm and eSignatures
When something happens in Amo Crm or eSignatures, your agent does the next thing in the other. Describe it 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 Amo Crm and eSignatures to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Amo Crm and eSignatures can do together
From Amo Crm to eSignatures
When New contact in Amo Crm
then Add Signer in eSignatures
From eSignatures to Amo Crm
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 Amo Crm and eSignatures
Triggers and actions 6 triggers · 27 actions
- New contact
Polling trigger for new contacts.
- New lead
Polling trigger for new leads.
- Add company
Create a company.
- Add contact
Create a contact.
- Add lead
Create a lead.
- Add note
Add a note to a lead/contact/company.
- Add task
Create a task.
- Get company
Get a company by ID.
- Get contact
Get a contact by ID.
- Get lead
Get a lead by ID.
- Get note
Returns one note (type, params/text, entity_id) attached to a lead, contact or company, by entity type and note id.
- List contacts
List contacts.
- List leads
List leads.
- List pipelines
List lead pipelines.
- List tasks
List tasks.
- Update company
Update a company.
- Update contact
Update a contact.
- Update lead
Update a lead.
- 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.
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 Amo Crm
Amo Crm to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Amo Crm to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Amo Crm to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Amo Crm to Google SheetsGoogle Sheets
Amo Crm to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Amo Crm to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into eSignatures
Google Drive to eSignaturesGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to eSignaturesActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to eSignaturesOrganize anything with Airtable, a modern database created for everyone.
Asana to eSignaturesAsana is a collaborative information manager for workspace.
ClickUp to eSignaturesClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Questions
Amo Crm and eSignatures, answered
What can start an automation from Amo Crm?
Any of Amo Crm's 2 triggers in the catalog, including New contact and New lead. Describe the moment in plain language and your agent picks the right one.
What can your agent do in eSignatures when something happens in Amo Crm?
Any of eSignatures's 11 actions, including Create Contract, Send Contract Draft, Update Template and Add Signer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from eSignatures to Amo Crm?
Yes. When something happens in eSignatures, your agent can act in Amo Crm too. This page covers both directions: eSignatures's triggers and Amo Crm's actions are listed here as well.
Do I have to build a connector for Amo Crm or eSignatures?
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.
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.