Zoho Sign Make integrationAutomate Zoho Sign with Make.
What happens after a contract gets signed, and who has to do it by hand? The Zoho Sign Make integration gives you 13 modules: 8 instant triggers and 5 actions. This page is for ops and sales teams, and it walks you from the connection to a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Zoho Sign Make integration do for you?
The Zoho Sign Make integration links your Zoho Sign account to Make, a no-code tool where you build a scenario, meaning an automation made of small bricks called modules. Zoho Sign tells Make the moment a document is sent, viewed, signed, declined or completed, and Make can send documents, fetch their details and download the signed file.
A deal closes, the contract leaves by itself. A module from your CRM or file storage opens the scenario, and Send a Document sends the file out for signature. The file has to carry its signature fields as text tags, so prepare the template once in your word processor.
Signed files land where your team works. Watch Document Completed fires once every recipient has signed, then Download Document fetches the final file so the next module can store or share it.
A refusal never goes unnoticed. Watch Document Declined and Watch Document Expired can alert the account owner, while Get Document Field Data pulls what signers typed into the form fields for your records.
What the app does not offer: no scheduled trigger and no search module. Every trigger here is instant, and anything outside the 5 actions goes through Make an API Call. If you are also weighing n8n, the n8n vs Make comparison lays out the criteria. New to the editor? Make training covers the basics, and Make troubleshooting helps when a run fails.
How do you connect Zoho Sign to Make?
- 01
Register an app in Zoho
Open the Zoho developer console, click Add Client ID and fill in your application details. Paste
https://www.integromat.com/oauth/cb/zoho-signas the callback URI, register, then copy the Client ID and the Client secret. - 02
Add a Zoho Sign module
In your scenario, add any Zoho Sign module and click Create a connection. A connection is your Zoho Sign account linked to Make once, then reused by every Zoho Sign module. The Connection name field is optional.
- 03
Paste the credentials
Enter the Client ID and Client secret you copied, or follow the instructions Make shows on screen. Your account stays linked, so the next module you add simply picks it from the list.
Your first scenario: send a contract for signature
GoalWhen a contract file is ready in another app, Make sends it to your signers through Zoho Sign.
- 01
Create the scenario
On the Scenarios page, create a new scenario and click the big +. The first module will be the app that holds your contract file, such as your CRM or cloud storage.
- 02
Pick the starting event
Search that app by name, choose the module that hands over the file, connect the account and fill its fields. Make lists the folders or records it can read once the connection works.
- 03
Add Send a Document
Click the + on the right, search Zoho Sign and pick Send a Document. Map the file from the first module and enter the recipients. The file needs its fields written as text tags.
- 04
Test with Run once
Click Run once. Each module shows the bundles it received, a bundle being one item passed along, here the file. Check that the request reached your Zoho Sign account.
- 05
Schedule and switch on
Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Save, then flip the switch to turn the scenario on.
Which Zoho Sign events can start a scenario?
8 modules start a scenario when something happens in Zoho Sign. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Zoho Sign as soon as it happens.
Watch Document Assigned to Somebody Else
Instant triggerIn Make“Triggers when a document has been assigned to someone else by a recipient.”
You learn right away when a recipient hands the document over to another person, so the signer on your file is no longer the one you picked. Use it to keep your records honest about who actually signs.
Watch Document Completed
Instant triggerIn Make“Triggers when a document has been completed by all recipients.”
This is the finish line: the scenario starts only once every recipient has completed the document. It is the natural place to hang anything that needs the fully signed file, from archiving to kicking off onboarding.
Watch Document Declined
Instant triggerIn Make“Triggers when a document has been declined by a recipient.”
A refusal reaches your team instead of sitting quietly in Zoho Sign. The scenario starts when any recipient declines the document, which gives the account owner a chance to call before the deal cools down.
Watch Document Expired
Instant triggerIn Make“Triggers when a document sent to a recipient has expired.”
Forgotten requests stop dying in silence. Make hears about it when a document sent to a recipient reaches its expiry, so someone can resend it or close the opportunity on purpose.
Watch Document Recalled
Instant triggerIn Make“Triggers when a document sent using Zoho Sign has been recalled.”
Someone on your side pulled a request back, and your other tools find out without anyone updating them by hand. The scenario starts when a document sent through Zoho Sign gets recalled.
Watch Document Sent
Instant triggerIn Make“Triggers when a new document has been sent in Zoho Sign”
Every new signature request becomes a line in your tracking, whoever sent it and from wherever. The scenario starts when a new document goes out in Zoho Sign, which gives you one place to see what went out.
Watch Document Signed
Instant triggerIn Make“Triggers when a document has been signed by a recipient.”
Progress shows up signature by signature. The scenario starts each time a recipient signs, which suits documents with several signers where you want to see who is done and who is still pending.
Watch Document Viewed
Instant triggerIn Make“Triggers when document has been viewed by recipient.”
You know the recipient actually opened the document, which is the right moment to follow up while it is on their screen. The scenario starts when a recipient views what you sent.
What can Make do in Zoho Sign?
Zoho Sign gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Download Document
ActionIn Make“Downloads a Zoho Sign document”
You get the actual Zoho Sign file inside your scenario, ready to be stored, attached or shared by the next module. Without it, the triggers only tell you something happened.
Get Document Details
ActionIn Make“Gets the details of a document”
This action gives you the full picture of one document, so a message or a record can mention more than an ID. Reach for it when a trigger fires and the next module needs details the trigger did not bring.
Get Document Field Data
ActionIn Make“Gets the details of the document filled by signers.”
Whatever signers typed into the document comes back to Make as data you can map, ready for the next module. It saves someone from retyping answers from a PDF into another tool.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
When none of the ready-made modules covers your need, this one calls any endpoint of the Zoho Sign API with the connection you already set up. No second login, no extra tool.
Send a Document
ActionIn Make“Sends out a document for signature from recipients as specified. Uploaded file must contain fields specified as text tags.”
Contracts go out for signature from any event in your scenario, with the recipients you set, so nobody downloads and re-uploads files by hand. This is the module that turns a closed deal into a signature request.
Need help automating Zoho Sign with Make?
A person reads every message.
