eSignatures via Power Automate with DocuSign and Adobe Acrobat Sign 

Thanks for the nice words!

I actually cover that part within this video. Go to around the 14 minute mark for DocuSign and the 41 minute mark for Adobe Sign. Both are similar in that you create a flow for listening for the signing and other events. You then grab the ID and use that to look up the correct SharePoint list row. Then update it with the signed form, status, etc. Hope this helps.

Thanks for the kind words. I haven't done this but it looks quite possible in both DocuSign and Adobe. This link for DocuSign might be helpful: support.docusign.com/s/document-item?language=en_US&rsc_301=&bundleId=ulp1643236876813&topicId=kcb1578456479440.html&_LANG=enus. For Adobe, I think you would do this right within Adobe Acrobat Pro and select as a Signature 2 field. This link about the Adobe Portal might be usefu: helpx.adobe.com/sign/using/send-document-for-signature.html#:~:text=Adobe%20Acrobat%20Sign%20makes%20it,to%20multiple%20people%20to%20sign.

I had not heard that. Thanks for letting everyone know.

Appreciate the nice feedback!

Here is how my samples look in the Word documents. DocuSign: Name: /n1/ Address: /a1/ Signed: /s1/ Date Signed: /ds1/ Adobe: Name: {{Name 1_es_:signer1:fullname:font(size=Auto)}} Address: {{ Address}} Signed: {{ *Signature 1_es_:signer1:signature}} Date Signed: {{Date 1_es_:signer1:date:format(mm/dd/yyyy):font(size=Auto)}} Hope this helps.

My Adobe demo account expired. Perhaps yours did as well? If not, you might go to Connections within Power Automate to see if any issues are showing there with Adobe Sign.

I can't do that unfortunately. But I have found that using Adobe Acrobat Pro if you have it makes the process much easier. You can use it to mark up your PDF file and even put in logic. Then use that as a template instead of the Word document like I used in my video. I couldn't find a good reference for that, but that is likely due to my search not being specific enough. This link for the Power Platform side looks pretty helpful: helpx.adobe.com/sign/integrations/microsoft-powerapps-flow.html#sign-to-power-automate.

​@@jeffrhodes Fun fact: If you make your email address in the flow the same as your Adobe email address, it DOES NOT SEND. When I used one of my other email addresses, it worked fine. Sheesh. That would have been a handy piece of information. I"m still workingon figuring out how to put the data from the sharepoint list into my Adobe Sign agreement so it's all nice and pre-filled. :) Edit: GOT IT!!!! See, what you have to do is pull up the Advanced Parameters drop down in the Create Agreement and Send for Signature action, and pick the "Form Field" option. Then you can just keep "Add Item"'ing for each field that you need, making sure (I think) to match the name of the field in the flow to the tags on the Word document beint used as a template, and populate the default values of same with the values from the Sharepoint List. Hoky smokes. This was tricky but is super useful once you figure it out. DId you ever make a followup video tothis that shows how to use Templates that live in Adobe Sign? I need to see about adding the extra logic for tracking the Agreement status etc now within the Sharepoint List. :) :) :)

@@goodluckfox Good stuff! Thanks for sharing your lessons learned. I haven't made any follow-up videos unfortunately as I don't have Adobe Pro or Acrobat Sign on my personal machine. One nice DocuSign feature is the demo connector that doesn't require a license.

This needs to be the original name of the column in SharePoint. I had named it Certificate and then renamed it to AgreementID. But the OData query wants the original name. The easiest way to find the correct name to use is to edit the column in SharePoint and then look at the URL: plattecanyon.sharepoint.com/samples/_layouts/15/FldEdit.aspx?List=%7BCAFDE37E%2D8780%2D4F96%2DB99E%2DF683F228C904%7D&Field=Certificate. The "Field=Certificate" part at the end is what you are looking for. If you are following my example and named it AgreementID initially, then use that instead. Hope this helps.

All I can think of is some sort of client-side setting. Have you tested by sending to yourself like I did in the video. Downloading and signing it pretty much defeats the purpose of course:).

I don't share the SharePoint list unfortunately, but here is a link to a screen capture that shows the SharePoint list settings: plattecanyon-my.sharepoint.com/:i:/g/personal/jeffrey_plattecanyon_onmicrosoft_com/EUIOox2bPnxLmPno1Ru7lC4B4GbA7ItaUVHs2VabkesAQQ?e=9H03e2. Hope this helps.

Hard to say I would debug the flow and look closely at the address to make sure there are no stray characters. Either of these should send to any email address.

There are two Case 5's in the Adobe Acrobat Status flow. The first is "AGREEMENT_ACTION_COMPLETED". It then has a case for SIGNER, APPROVER, ACCEPTOR, FORM_FILLER, and CERTIFIED_RECIPIENT. For all of these, I just update the Message variable to log the agreement name and participant. For example, here is the value for CERTIFIED_RECIPIENT (case 5): Notification from Microsoft Power Automate The receipt of the Adobe Sign agreement @{triggerBody()?['agreement']?['name']} has been acknowledged by @{triggerBody()?['participantUserEmail']}. Hope this helps.

Thank you @@jeffrhodes 👍

You can do it via the tags like I did in the video, but better looks to be to use Adobe Acrobat DC to configure the form template itself (and use a PDF rather than a Word document).

@@jeffrhodes thank you for your help

Did you change the type from docx to PDF? I have used PDF successfully but find that it makes the rest of the PDF "unfillable" (other than the tags that you put in via Power Automate).

@@jeffrhodes Yes, I changed the type to PDF and used the base64 expression to embed the dynamic content from my MS Form where the document was uploaded. The flow runs successfully, but the document is not added and when I check the output I see the above errors.

@@melindagildart7342 only other suggestion would be to try without the base64() part as that seems to vary based on each cloud. I would check that the error is on the creating the document action as getting the tags into the PDF file can be challenging (and cause errors). Hope this helps a bit.

@@jeffrhodes This is what I get when I don't include the base64() expression. "The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters."

​@@melindagildart7342 And you changed your "Get file content via path" action to ensure it is pointing to the PDF file? Sorry - not many more ideas.