Connect the e-signature tool your company already uses: Yousign, Universign, Adobe Sign and others, via API.
Tomorro calls your endpoint when a signature is requested or canceled, and your own integration drives the signing ceremony in your tool. The signed document then comes back to Tomorro through the API.
This integration is set up by an admin from Settings → Integrations and applies to the whole workspace.
This integration is not enabled by default: it is enabled on request from your account manager.
The setup is done by your technical team. The full documentation (prerequisites, webhook setup, API calls, cancellation cases, attachments) is available here: Technical documentation.
Possible flows :
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 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.