Friday, July 26, 2019

How to use Microsoft flow to provide Adobe Sign process as http services

We have a external process running on AWS need to integrate with SharePoint document using Adobe Sign. The document will be pushed to SharePoint through Graph API and like to call service to initialize the Adobe Sign process.  There are may different ways to provide this as service but the quickest way might be the Microsoft Flow.

The way I implemented is to start with OoB "Get signatures on a selected file in SharePoint" flow template. Test this manually and then build our own process. The key two actions we need to use are:

  • Adobe "Upload a document and get a document ID"
  • Adobe "Create an agreement from an uploaded document and send for signature"

In order to be easily called, I've created the activity "When a HTTP request is received" as the trigger for the flow. The overall flow is very simple and actions are listed below.


To demonstrate you could receive the parameter, The relativePath Document/{documentName} has been added. The http call will pass the document name as parameter so flow could find the document. This is described as the below screenshot. 



The url to call the flow is like this below. Please note I have updated the real GUID and the way pass the Document as parameter in red.

https://prod-41.westus.logic.azure.com/workflows/9452e067c6b648c3ac4ed60ab1234567/triggers/manual/paths/invoke/Document/myDocument.docx?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=L5LqW-NVBFc6sdxHpthXXXXXXXXXX

The next key is to get the file content and I found the easy way is to use "Get file content using path" action. You could use other actions but may need to get file Id. The rest actions are same as the OoO flow as we mentioned "Get signatures on a selected file in SharePoint" with few parameters modified for file content.


Now, you have a working http service that can be invoked to integrate SharePoint denouement with Adobe Sign. 

Few enhancements in the future.

  1. Pass file ID like DocID only and the flow to retrieve file name, path, and content form the file ID.
  2. Retrieve "Recipient Email" from SharePoint list item.
  3. Retrieve the Signed document and stored to SharePoint some where or update the document item with the Signed Adobe document Url.
This is my first SharePoint Adobe flow, there will be more integration and enhancements we could implement in the future. 




No comments:

Post a Comment