Automatically Upload Signed Documents to SharePoint from Zoho Sign

In my previous post, Automate Signatures with Zoho Sign and Power Automate, I walked through how you can automate the signing process using Zoho Sign. The workflow triggered whenever a document was sent for signing, making it easy to manage approvals and ensure smooth execution.

This time, we’ll take it a step further. In this continuation, I’ll show how you can automatically upload the signed documents back to SharePoint once the signing process is completed, ensuring they are safely stored and your team stays informed without any manual intervention.

Overview

This flow automates the process of handling completed Zoho Sign documents and saving them to SharePoint. As soon as a document is marked as Completed in Zoho Sign, the Power Automate flow retrieves it, processes it, and uploads it to a designated SharePoint folder.

The overall flow is shown below:

Trigger

The flow starts with Zoho Sign Triggers. This trigger is configured to fire when a Zoho Sign webhook action is marked as Completed. This ensures that the flow only runs after the signing process is finished, preventing partial or unsigned documents from being uploaded.

Step 1 – Compose Request ID

Once triggered, the first step is to extract the request_id from the Zoho Sign payload. This is done using a Compose action, which isolates the request ID for use in subsequent steps. The request ID uniquely identifies the signing session and helps us retrieve the corresponding documents.

Step 2 – For Each Document

After obtaining the request ID, a For each loop is added to iterate through all the document IDs associated with that particular signing request. This is useful when a single signing process contains multiple documents.

Compose Document ID

This extracts the current document ID from the list of documents in the signing request. Each document will pass through the same set of actions individually.

Download File

Using the request ID and document ID, the flow calls Zoho Sign’s API to download the completed PDF document. This ensures that the exact version signed by all parties is retrieved.

Compose 2

This step stores the downloaded file content temporarily, preparing it for upload. It acts as a bridge between downloading from Zoho and uploading to SharePoint.

Create File

Finally, the downloaded file is uploaded to SharePoint using the Create file action. In this example, the target location is the folder:

/Contracts Email Recived Documents

Each file is named dynamically based on its document ID, with the .pdf extension added automatically. You can modify the file naming logic if you prefer to include the signer’s name, date, or any other metadata.

When a Zoho Sign document is marked as Completed, this flow is triggered automatically. It extracts the request ID from the trigger output and loops through all associated document IDs in that request. For each document, the flow retrieves the document ID, downloads the corresponding signed PDF from Zoho Sign, stores it temporarily, and then uploads it to the specified SharePoint folder. This seamless process ensures that every completed signing session is immediately reflected in SharePoint without any manual steps.

Here’s how the complete process comes together:

By automating this process, you not only eliminate manual work but also maintain a consistent and reliable storage structure within SharePoint. Every signed file becomes traceable, version-controlled, and instantly accessible to your team the moment it’s completed. This approach works exceptionally well for teams managing multiple contracts or compliance documents daily, helping them maintain accuracy and save time.

With this automation in place, your Zoho Sign and SharePoint environments now work hand in hand. The moment a document is signed, it’s automatically fetched, stored, and made available in your SharePoint library. There’s no need for manual uploads or constant follow-ups. In the next post, I’ll extend this flow to include team notifications and alerts, so the right people are notified as soon as a signed document lands in SharePoint.