> ## Documentation Index
> Fetch the complete documentation index at: https://alpha.developer.tomorro.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Non-Technical scoping

> Connect your own signature tool: what the integration covers, in five flows

**Scope:** this guide only covers the exchanges between **Tomorro and the integration** (the middleware built by the customer). What the integration does with the third-party signature tool (Yousign, Universign, Adobe Sign, LuxTrust, Oodrive...) is out of scope and entirely on the customer's side.

**TL;DR**

Five flows, all between Tomorro and your middleware:

* **Flow 1: Signature is requested.** A user sends for signature in Tomorro. Tomorro fires `signature.requested`, you fetch the document, fields and signatories, then run the signature in your own tool. **Tomorro sends nothing to the signatories at any point**: your tool owns the whole signer experience, so no double notification.
* **Flow 2: Signature is completed.** Once everyone has signed in your tool, you push the signed PDF back. Tomorro moves the contract to `signed` and runs its post-signature automations.

***

* **Flow 3: Signature canceled in Tomorro.** A user cancels from Tomorro, Tomorro fires `signature.canceled`, you kill the envelope on your side. Nothing to call back.
* **Flow 4: Signature canceled in your tool.** Refused, expired or canceled there: you call `cancel-signatures` and the contract goes back to `draft` or `negotiating`.

***

* **Flow 5: Attachments (optional).** Push the signature certificate, or any supporting document produced by your tool (PDF, Word, Excel...), onto the contract, one file per call.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.