Is HttpClient Step in CLM Workflow capable of uploading a file to an endpoint

Hi Ashish,
You can write a json body for the storage website and pass the document url contained in a variable in that json body and update the attachment field where you want to upload the document. Use PUT Method for this if you are updating already created record in storage website for that particular document . and if its a first time trigger then first create the record using POST Method then use PUT method to update the attachment field with docusign document url. You will need 2 httpclient steps for that to work.
In Headers use: Authorization and pass the Bearer Token that you receive from the OAuth Access Token
2nd Header use: Content-Type and pass value “text/plain”
3rd header use: Accept and pass value “application/xml”

capture the repsonse status code and response variable under the output also as a best practice.

 

Hello ​@ashishkeshari06 

Welcome to DocuSign Community!

​@Sudhanshu Vijay has got the method using HTTP Client step which looks interesting, though I can share about the “Agreement Action” through the eSignature.

You can utilize Agreement Actions in DocuSign eSignature to automatically save a signed contract to SharePoint. Check out DocuSign Support article for more details.

Connect an Application
Automate Common Post-Signature Tasks With Agreement Actions

Hope it helps,

Thanks!

Thanks ​@Pawan Gangwani - for your inputs. I have explored that option and since it’s pushes the document to storage - then destination application will have to pull the files/documents which adds additional hops as well as dependency on the destination application. My goal is push to the destination through their API which is well supported for a file/document upload - just that the HttpClient - Content(Text Field) - seems to be not supportive of the file attachments. 

​@Sudhanshu Vijay - Your suggestion looks interesting. I have already tried few other variations. Let me try your suggested way - thanks for the inputs.