Integration
Connect Cartes.io and eSignatures
When New map fires in Cartes.io, your agent runs Add Signer in eSignatures, or Contract Signed in eSignatures to Add map in Cartes.io. 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 Cartes.io and eSignatures 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 Cartes.io and eSignatures can do together
From Cartes.io to eSignatures
When New map in Cartes.io
then Add Signer in eSignatures
From eSignatures to Cartes.io
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 Cartes.io and eSignatures
Triggers and actions 6 triggers · 21 actions
- New map
Fires when a new map is created.
- New marker
Fires when a new marker is added to a map.
- Add map
Create a new map.
- Find categories
Search for categories matching a query.
- Find maps
Search for maps matching a query.
- Get map
Retrieve a single map by ID.
- Get map static image
Generate a static image snapshot of a map.
- Get marker
Retrieve a single marker by ID.
- List categories
List all available map/marker categories.
- List maps
List all maps.
- List marker locations
List the recorded location history for a marker.
- List markers
List all markers on a map.
- 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 Cartes.io
Cartes.io to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cartes.io to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cartes.io to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cartes.io to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Cartes.io to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cartes.io 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
Cartes.io and eSignatures, answered
What can start an automation from Cartes.io?
Any of Cartes.io's 2 triggers in the catalog, including New map and New marker. Describe the moment in plain language and your agent picks the right one.
What can your agent do in eSignatures when something happens in Cartes.io?
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 Cartes.io?
Yes. When something happens in eSignatures, your agent can act in Cartes.io too. This page covers both directions: eSignatures's triggers and Cartes.io's actions are listed here as well.
Do I have to build a connector for Cartes.io 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.
Can my AI client use Cartes.io and eSignatures 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.