[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Chase unsigned Yousign requests with reminders

> Find Yousign requests that are still waiting for a signature, see who has not signed and send each of those signers a reminder.

Source: https://cotlet.dev/integrations/yousign-api-mcp-server/chase-unsigned-signature-requests

A contract sent on Monday is still unsigned on Friday, and nobody knows whose turn it is until someone opens each request in Yousign.

Cotlet does it in your own Yousign account with list\_signature\_requests, get\_signature\_request and send\_reminder, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=yousign) [All Yousign tools](https://cotlet.dev/integrations/yousign-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Yousign do this on its own?

Yousign sends automatic reminders at the frequency and count set on each request, and you can send one by hand from the request page (checked 20 Oct 2026). The API has a send\_reminder call on paid API plans and a webhook when a reminder goes out. Nothing in the app sums up across requests who is still silent.

## How you do it in Yousign today

1. The user opens the Signatures page and filters for requests still In progress.
2. For each request, the user opens the details page to see which signer has not signed.
3. A reminder to everyone goes out with "Send reminder" on the details page. For one person, the user clicks the "..." to the right of the signer and chooses "Send reminder".
4. Automatic reminders are set per request in the settings step, with a frequency and a number of reminders, and the default sits under your initials > Signature settings.
5. The list has no view of who ignored the last reminder, so chasing means checking request after request.

## How to chase unsigned Yousign requests with reminders

Prompt

```
List my signature requests still In progress, tell me who has not signed, and send a reminder to those signers.
```

1. 01  
### List what is still open  
list\_signature\_requests runs with the In progress status. The agent leaves out Draft, Completed and cancelled requests, so no one is chased for a request that is not waiting on them.
2. 02  
### Find the signers who are pending  
get\_signature\_request returns each signer with a status. The agent keeps signers who were notified and have not signed. With a signing order set, only the signer whose turn it is counts.
3. 03  
### Skip recent sends  
The agent compares the creation date with your rule, for example "older than 3 days", and skips newer requests. Requests close to their expiration date go to the top of the list.
4. 04  
### Send the reminders  
send\_reminder goes out once per signer, or once per request when you leave signer\_id out. Yousign allows a reminder only while the request is In progress and the signer has been notified, so other signers are skipped and listed. Each reminder waits for your OK by default.
5. 05  
### Report who is left  
The agent returns who was reminded and who was skipped with the reason, so you know whom to call yourself.

### What you get back

Example data

```
Requests In progress: 5
Reminded 4 signers on 3 requests, e.g. Tom Becker (Service agreement)
Skipped 2: Lease renewal (created today), NDA with Acme (signer not notified yet, waits for the previous signer)
Expires first: Lease renewal
```

### Other ways to ask

- Every morning, remind signers of requests older than 3 days, once, and list who stays silent.
- Remind only the signer of the Service agreement, not the other recipients.
- List what is waiting on me as a signer or approver and do not send anything.

## What Yousign allows, and what to know first

- A manual reminder from the request page goes to all recipients, or only to the one whose signature is pending when a signing order is set.
- Yousign allows a reminder through the API only when the request is ongoing and the signer is notified.
- Automatic reminders use the frequency and number set on each request, and the account default is under Signature settings.
- A request expires 6 months after creation by default and can be set up to one year.

send\_reminder asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Yousign Help: Send reminders to recipients](https://help.youtrust.com/en/articles/72882-send-reminders-to-recipients) · [Yousign Help: Create a signature request](https://help.youtrust.com/en/articles/71619-create-a-signature-request) · [Yousign developers: Send manual reminder to a Signer](https://developers.youtrust.com/reference/post-signature%5Frequests-signaturerequestid-signers-signerid-send%5Freminder-1) · [Yousign developers: Webhooks](https://developers.youtrust.com/docs/webhooks)

## Call send\_reminder from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/yousign/signature-requests/8c1d4e7a-52b9-4f03-a6d8-91e0b3c5f274/reminders \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"signer_id":"b7e2a9d4-1c63-4a58-8f0e-d35c6a41b2f9"}'
```

Example response

```
{
"signature_request_id": "8c1d4e7a-52b9-4f03-a6d8-91e0b3c5f274",
"reminded": [
{
"name": "Tom Becker",
"email": "tom@example.com"
}
],
"skipped": []
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is yousign\_write → send\_reminder. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/yousign-api-mcp-server.md#automations)

## Yousign tools this automation uses

__Cotlet Yousign tools used to chase unsigned Yousign requests with reminders__
| Tool | Parameters |
| ------------------------- | ---------------------------------- |
| list\_signature\_requests | status |
| get\_signature\_request | signature\_request\_id |
| send\_reminder | signature\_request\_id, signer\_id |

[All 11 Yousign tools with descriptions](https://cotlet.dev/integrations/yousign-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Yousign to Cotlet?

Yes. You sign in to Yousign yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Yousign once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Yousign automations

- [Send Yousign contracts from a template with AI](https://cotlet.dev/integrations/yousign-api-mcp-server/send-contracts-from-template.md)
- [Download signed Yousign documents and audit trails](https://cotlet.dev/integrations/yousign-api-mcp-server/archive-signed-documents.md)
- [Yousign API and MCP server: every tool](https://cotlet.dev/integrations/yousign-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Yousign.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Yousign.

[Sign up free](https://cotlet.dev/app/signup?app=yousign)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.