Have a system that doesn't quite fit?
Tell us what you need it to do. We'll scope it with you.
Zoho Sign in place of DocuSign, inside M-Files
Contracts go out for signature from the M-Files workflow and come back signed, now through Zoho Sign instead of DocuSign.
The challenge
The company signed its contracts through M-Files' DocuSign integration. Moving to Zoho Sign meant rebuilding that integration, converting every contract template, and switching over without losing contracts already out for signature.
What we built
- A custom M-Files vault application that sends a contract to Zoho Sign when it reaches Pending Signature
- Signers taken from the contract's metadata, in three groups that sign in a set order
- DocuSign placeholders converted to Zoho Sign tags across 16 contract templates, so every signature, initial and date lands in place automatically
- The signed PDF and its completion certificate saved back to the contract as a new version
- Declined, expired and voided requests move the contract to the matching workflow state
- A planned switch-over: every contract already out for signature was listed and dealt with before DocuSign was removed
How it works
People work in M-Files exactly as before: moving a contract into Pending Signature sends it. The vault application builds the request from the contract's metadata, sends it through Zoho Sign and checks progress on a schedule. When everyone has signed, the signed contract and certificate come back into the vault and the workflow moves on.
- Contract approved
- Pending Signature
- Zoho Sign
- Signed PDF + certificate
- Signed
By the numbers
- 16 contract templates converted
- Signing status checked every 15 minutes
- Tested in a sandbox and a copy of the live vault, and signed off by the client before go-live
- Live since 28 October 2026