---
title: "Connect eSignatures to CARTO - APIANT.ai"
description: "When \"Contract Signed\" fires in eSignatures, your agent runs \"Add SQL job\" in CARTO."
canonical: "https://apiant.ai/connect/esignatures-to-carto"
---

# Connect eSignatures to CARTO

When **Contract Signed** fires in [eSignatures](https://apiant.ai/connections/esignatures), your agent runs **Add SQL job** in [CARTO](https://apiant.ai/connections/carto). Describe the whole flow and it is built, tested on every scenario and kept running.

eSignatures **4** triggers eSignatures **11** actions CARTO **8** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want eSignatures and CARTO to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What eSignatures can start in CARTO

- When **Contract Signed** in eSignatures then **Add SQL job** in CARTO
- When **Contract Withdrawn** in eSignatures then **Calculate isoline** in CARTO

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 CARTO

## Triggers and actions 4 triggers · 19 actions

- Trigger

**Contract Signed**

Triggers when a contract is signed by all signers.

- Trigger

**Contract Withdrawn**

Fires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn".

- Trigger

**Signer Declined Signature**

Fires when a signer declines to sign the contract. Webhook event "Signer declined the signature".

- Trigger

**Signer Viewed Contract**

Fires when a signer opens/views the contract. Webhook event "Signer viewed the contract".

- Action

**Add Signer**

Add a new signer to an existing contract.

- Action

**Add Template**

Create a new reusable contract template.

- Action

**Create Contract**

Creates a new contract.

- Action

**Delete Signer**

Remove a signer from a contract that has not yet signed.

- Action

**Delete Template**

Delete a contract template.

- Action

**Get Contract**

Retrieve a contract's current status, signer states, and metadata.

- Action

**Get Template**

Retrieve a contract template's details.

- Action

**List Templates**

List all contract templates in the account.

- Action

**Send Contract Draft**

Send a previously created draft contract to its signers.

- Action

**Update Template**

Update an existing contract template's title or settings.

- Action

**Withdraw Contract**

Withdraw (cancel) a contract that has been sent but not fully signed.

- Action

**Add SQL job**

Starts an asynchronous SQL job in your data warehouse through a CARTO connection, for queries that take longer than a minute. Returns the job id to check its progress.

- Action

**Calculate isoline**

Returns the area reachable from a point within a travel time or distance, as a GeoJSON polygon collection.

- Action

**Calculate route**

Calculates a route between an origin and a destination, optionally through intermediate waypoints, using your organization's location data provider.

- Action

**Delete SQL job**

Cancels a running SQL job on one of your CARTO data warehouse connections.

- Action

**Geocode address**

Returns coordinates and address details for a street address, using your organization's configured geocoding provider.

- Action

**Get SQL job**

Returns a SQL job's current status and details, so you can check whether a long-running query has finished.

- Action

**Reverse geocode**

Returns the street address closest to a latitude/longitude pair.

- Action

**Run SQL query**

Runs a SQL query in your data warehouse through a CARTO connection and returns the resulting rows and column schema.

## Each app on its own

- [ **eSignatures** ESignatures.io is a tool used for signing mobile friendly contracts over the web.](https://apiant.ai/connections/esignatures)
- [ **CARTO** Location Information Prediction](https://apiant.ai/connections/carto)

Reviews

## What our customers say

## More from eSignatures

- [ **eSignatures to Pexafy** Semantic image search across 9+ free stock photo sources with a unified JSON schema](https://apiant.ai/connect/esignatures-to-pexafy)
- [ **eSignatures to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/esignatures-to-hubspot)
- [ **eSignatures to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/esignatures-to-salesforce)
- [ **eSignatures to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/esignatures-to-slack)
- [ **eSignatures to Google Sheets** Google Sheets](https://apiant.ai/connect/esignatures-to-google-sheets)
- [ **eSignatures to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/esignatures-to-google-calendar)

## More into CARTO

- [ **HubSpot to CARTO** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-carto)
- [ **Salesforce to CARTO** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-carto)
- [ **Slack to CARTO** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-carto)
- [ **Google Sheets to CARTO** Google Sheets](https://apiant.ai/connect/google-sheets-to-carto)
- [ **Gmail to CARTO** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-carto)
- [ **Google Calendar to CARTO** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-carto)

Questions

## eSignatures and CARTO, 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 CARTO when something happens in eSignatures?

Any of CARTO's 8 actions, including Add SQL job, Calculate isoline, Calculate route and Geocode address. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from CARTO to eSignatures?

CARTO has no triggers in the catalog today, so automations start in eSignatures. If you need the other direction, ask: your agent reads CARTO's API documentation and adds it.

###

### Do I have to build a connector for eSignatures or CARTO?

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 CARTO 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.
