---
title: "Connect eSignatures and SQL Server - APIANT.ai"
description: "When \"Contract Signed\" fires in eSignatures, your agent runs \"Add Row\" in SQL Server, or \"New or Updated Row\" in SQL Server to \"Add Signer\" in eSignatures."
canonical: "https://apiant.ai/connect/esignatures-to-sql-server"
---

# Connect eSignatures and SQL Server

When **Contract Signed** fires in [eSignatures](https://apiant.ai/connections/esignatures), your agent runs **Add Row** in [SQL Server](https://apiant.ai/connections/sql-server), or **New or Updated Row** in SQL Server to **Add Signer** in eSignatures. Describe the whole flow and it is built, tested on every scenario and kept running.

eSignatures **4** triggers eSignatures **11** actions SQL Server **4** triggers SQL Server **7** 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 SQL Server 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 and SQL Server can do together

### From eSignatures to SQL Server

- When **Contract Signed** in eSignatures then **Add Row** in SQL Server
- When **Contract Withdrawn** in eSignatures then **Update Row** in SQL Server

### From SQL Server to eSignatures

- When **New or Updated Row** in SQL Server then **Add Signer** in eSignatures
- When **New Row** in SQL Server 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 SQL Server

## Triggers and actions 8 triggers · 18 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.

- Trigger

**New or Updated Row**

Triggers when a new row is added or modified.

- Trigger

**New or Updated Row (Custom Query)**

Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database.

- Trigger

**New Row**

Triggers when you add a new row.

- Trigger

**New Table**

Fires when a new table appears in the connected SQL Server database.

- Action

**Add Row**

Add one row to a table on the connected SQL Server database.

- Action

**Delete Row**

Delete the rows in a table whose chosen column equals a value.

- Action

**Find Row**

Find the first row in a table whose chosen column matches a value.

- Action

**Find Rows via Custom Query**

Runs a SELECT statement you write against the connected SQL Server database and returns every row it matches.

- Action

**Find Row via Custom Query**

Runs a SELECT statement you write against the connected SQL Server database and returns the first row it matches.

- Action

**Run Custom Statement**

Runs a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.

- Action

**Update Row**

Change column values on every row of a table whose chosen column matches a value.

## 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)
- [ **SQL Server** Connect directly to a Microsoft SQL Server database and run SQL statements from your automations.](https://apiant.ai/connections/sql-server)

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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](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 SQL Server

- [ **HubSpot to SQL Server** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sql-server)
- [ **Slack to SQL Server** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sql-server)
- [ **Mailchimp to SQL Server** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-sql-server)
- [ **Shopify to SQL Server** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/shopify-to-sql-server)
- [ **QuickBooks Online to SQL Server** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/quickbooks-online-to-sql-server)
- [ **Pipedrive to SQL Server** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/pipedrive-to-sql-server)

Questions

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

Any of SQL Server's 7 actions, including Update Row, Add Row, Find Row and Find Rows via Custom Query. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from SQL Server to eSignatures?

Yes. When something happens in SQL Server, your agent can act in eSignatures too. This page covers both directions: SQL Server's triggers and eSignatures's actions are listed here as well.

###

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

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 SQL Server 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.
