---
title: "Connect eSignatures and Trengo - APIANT.ai"
description: "When \"Contract Signed\" fires in eSignatures, your agent runs \"Add internal note to ticket\" in Trengo."
canonical: "https://apiant.ai/connect/esignatures-to-trengo"
---

# Connect eSignatures and Trengo

When **Contract Signed** fires in [eSignatures](https://apiant.ai/connections/esignatures), your agent runs **Add internal note to ticket** in [Trengo](https://apiant.ai/connections/trengo), or **New Internal Note** in Trengo 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 Trengo **3** triggers Trengo **15** 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 Trengo 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 Trengo can do together

### From eSignatures to Trengo

- When **Contract Signed** in eSignatures then **Add internal note to ticket** in Trengo
- When **Contract Withdrawn** in eSignatures then **Add ticket** in Trengo

### From Trengo to eSignatures

- When **New Internal Note** in Trengo then **Add Signer** in eSignatures
- When **New Outbound Message** in Trengo 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 Trengo

## Triggers and actions 7 triggers · 26 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 Internal Note**

Fires when an internal note is added to a Trengo ticket.

- Trigger

**New Outbound Message**

Triggers when an outbound message is created.

- Trigger

**Ticket Label Added**

Triggers when a label is added to a conversation.

- Action

**Add internal note to ticket**

Adds an internal note (visible only to agents) to a Trengo ticket.

- Action

**Add ticket**

Create a new support ticket.

- Action

**Add ticket label**

Attaches an existing label to a Trengo ticket.

- Action

**Create a Contact**

Creates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.

- Action

**Create webhook**

Subscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.

- Action

**Delete contact**

Delete a contact by id.

- Action

**Delete ticket**

Delete a ticket by id.

- Action

**Find a Contact**

Returns the Trengo contacts that match the search term.

- Action

**Get contact**

Retrieve a single Trengo contact by its id.

- Action

**Get webhook**

Fetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.

- Action

**List contacts**

List all contacts.

- Action

**List labels**

Lists the ticket labels defined in the Trengo account (first page).

- Action

**List tickets**

Returns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.

- Action

**Send a Message**

Sends a reply message on an existing Trengo ticket, over the ticket's own channel.

- Action

**Update contact**

Update an existing contact by id.

## 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)
- [ **Trengo** Trengo is a team collaboration tool to manage conversations from channels such as web chat, email and...](https://apiant.ai/connections/trengo)

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 Trengo

- [ **OpenAI to Trengo** OpenAI's platform for text generation (Responses + Chat Completions), image generation (gpt-image-1 /...](https://apiant.ai/connect/openai-to-trengo)
- [ **CloudConvert to Trengo** CloudConvert converts files between more than 200 supported formats: documents, image, spreadsheet...](https://apiant.ai/connect/cloudconvert-to-trengo)
- [ **elmah.io to Trengo** Cloud logging for.NET web applications using ELMAH.](https://apiant.ai/connect/elmah-io-to-trengo)
- [ **Postman to Trengo** Postman is a platform for building and testing APIs.](https://apiant.ai/connect/postman-to-trengo)
- [ **HubSpot to Trengo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-trengo)
- [ **Salesforce to Trengo** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-trengo)

Questions

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

Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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