# Connect eSignatures.io to your AI employee

Connect to eSignatures.io: create, sign, convert, and manage documents and pdfs. Hire an AI employee, connect eSignatures.io in one click, and it takes real actions in eSignatures.io for you: reading, writing, and following up while you get on with something else. Works over OAuth or any MCP server, and no workflow builder is involved.

## Things people ask their AI employee to do in eSignatures.io

- Send the contract for signature in eSignatures.io and chase whoever has not signed.
- Tell me which documents in eSignatures.io are still waiting on someone.
- File every signed agreement from eSignatures.io where the team can find it.

## How connecting eSignatures.io works

- Hire an AI employee from the marketplace. It arrives knowing the job.
- Connect eSignatures.io in one click through its standard OAuth screen. No API keys.
- Ask for what you want in plain language. It does the work and reports back.

## Why connect eSignatures.io to an AI agent?

Your AI employee handles the repetitive eSignatures.io work, on a schedule or on request, and tells you what it did. eSignatures.io is one of thousands of connections, plus any MCP server you already run, so a single request can cross all of them. Category: Documents & Signatures.

## People who connect eSignatures.io also connect

- [Connect API2PDF to your AI agent](/en/integrations/api2pdf)
- [Connect Carbone to your AI agent](/en/integrations/carbone)
- [Connect CloudConvert to your AI agent](/en/integrations/cloudconvert)
- [Connect Conversion Tools to your AI agent](/en/integrations/conversion_tools)
- [Connect Convertapi to your AI agent](/en/integrations/convertapi)
- [Connect DocRaptor to your AI agent](/en/integrations/docraptor)

## Explore

- [Every integration](/en/integrations)
- [Hire an AI employee](/en/market)
- [Pricing](/en/pricing)

## FAQ

### How do I connect eSignatures.io to an AI agent?

Hire an AI employee, open its Tools tab, find eSignatures.io, and click Connect. You authorise access through the standard eSignatures.io OAuth screen and the connection is live the moment you approve it. There are no API keys to paste and nothing to deploy.

### Do I have to build a workflow or write code?

No. This is not a workflow builder with triggers and branches. You tell your AI employee what you want in plain language, and it decides which eSignatures.io actions to run. If you want it to happen every week, say that too.

### What can an AI agent actually do inside eSignatures.io?

Everything eSignatures.io exposes to us: the full action list is on this page, read and write both. Anything eSignatures.io itself does not allow is listed as a limit, so you find out here rather than by failing later.

### Is there an MCP server for eSignatures.io?

You do not need one, the eSignatures.io connection is built in. If you already run your own MCP server, your AI employee can use that too, alongside the built-in connection.

### Will it work with my other tools at the same time?

Yes, and that is the point. eSignatures.io is one of thousands of connections, so a single request can read from one tool, act in eSignatures.io, and report back in your chat.

### Is it safe to give an AI agent access to eSignatures.io?

You connect eSignatures.io once at the company level and choose which employees may use it. Sensitive actions can require your approval before they run, and every action the employee takes is logged.