This is such a great video, you are an excellent teacher. I always pick up something new! We do something similar for our digital contracts. Docusign is easier to work with IMO, however we use Adobe Sign because of the volume pricing. In our use case, we: Power Apps JSON -> Power Automate -> CraftMyPDF API -> Power Automate -> Adobe Sign API. CraftMyPDF is pretty cool, you can make your docs/contracts extremely customized and flexible (drag and drop UI). Basically, you build a template in it and then map certain sections from the JSON you are sending through the API.
Thank you so much for all your Videos , it helped me learn a lot . Can you please make a video in the future on how to add people into a distribution list using power automate 🙏
Another great video Shane! Always learning something new when a new one is released. In the second workflow, the trigger was looking for a change to a Docusign envelope (assuming ANY envelope). If there were a number of similiar flows that were sending different document types e.g one flow to request a signature for an NDA and another flow to send a document for signature for a sales proposal, is there a way to differentiate which type of document is being responded to? This would be useful if you wanted the responses to NDAs copied to a different library than the sales proposals.
Not sure if there is a better answer but here is my first thought. Create one flow that triggers when anything changes. Then get the envelope. Now check the metadata of your envelope for some metadata that tells you what it is (I am sure this exists, hope) and then have a Switch to build different logic for different types. Hope that helps but that is high level how I would think about it not ever doing it.
Thank you Shane. I have been trying to get the Army to send my "Solutions" Team to your PowerApps University for 1.5 years. The request is still valid in the system, maybe this is the year. :( It looks like DoD is getting pitched by DocuSign. This will be the video I assign to my team to watch if they buy in. LOL You are my go-to when someone in my HQ asks me how to do something, and I don't have time to do it for them.
Hi Shane ! Thank you so much for all the great contents that you have created and helped power platform community. PowerApps is great, unfortunately it is not available for personal projects outside of organization. What would be the closest alternative platform to develop personal webapps with same user experience ? Thanks.
You know I didn't really build that one for download because of all of the new connections I was learning. Is there a part you are looking for? I could probably add the flow to the RUclips library pretty easy. The app would take a bit more though.
Love it! One question, though. If the signed document needs to be stored as an attachment to a list item, how do you determine which list item to attach it to? Is there a parameter that can be attached to the document when you send it to DocuSign (for example, the SP row id) that could be retrieved when the document is completed?
There's a separate "Production" Docusign Connector for Non-Demo Docusign in Power Automate. It has the same exact actions as the demo version. Basically, you would need to use the Production Docusign Connector instead of the demo one. So, it doesn't convert, technically, yes you would need to create the power automate using the prod docusign actions.
The flow steps will not convert automatically. You will need to build a new flow using the Production connector (Docusign not 'Docusign Demo'). Please note: Docusign connectors are standard and you do not need a premium license to use any Docusign actions.
Looking at this in our organisation, what would be useful is to track the all the document progress in a sharepoint site lists. tracking who templated documents are with and thier current status. We were able to achieve this adobe sign but havent been able to since me moved to docusign, im sure it must be possible
Docusign has triggers based on Envelopes so if the envelope is completed for example, Power Automate can create or update an item in SP list. However there isn't a trigger event for Power Automate as of now based on templates or usage of templates.
I have never head of Sign Now, I will look at it. This would work with multi-page you would add more \s1\ tags in the HTML would be the only difference.
The new PDF function is still experimental and really shouldn't be used in Production apps. It has a lot of challenges still so I make them the way I can control.
This is a very Important video Shane. Thank you so much!
You are welcome, happy to help. 😎
Excellent video Shane - I'll start using it straight away
AYYYYYYY! You have no idea how much i LOVE this video!!
As much as the people love you? 🤩
More Awesome Stuff. Just started an new assignment, and guess what I got in charge of the Docusign flows. You're on fire, man!
Congrats on the new assignment. Hope it all goes well and you build something awesome.
This is such a great video, you are an excellent teacher. I always pick up something new! We do something similar for our digital contracts. Docusign is easier to work with IMO, however we use Adobe Sign because of the volume pricing. In our use case, we: Power Apps JSON -> Power Automate -> CraftMyPDF API -> Power Automate -> Adobe Sign API. CraftMyPDF is pretty cool, you can make your docs/contracts extremely customized and flexible (drag and drop UI). Basically, you build a template in it and then map certain sections from the JSON you are sending through the API.
Thank you for the kind words and wow that is quite the process you have there. Glad you got it working. 🤩
A game changer. Thank you Shane
Happy to help
Great video. You make it fun!
Thank you. I do my best to keep tech from being boring. 😎
Thank you so much for all your Videos , it helped me learn a lot . Can you please make a video in the future on how to add people into a distribution list using power automate 🙏
Hmmm. I will think about that one. I assume you will have to use the Graph API but never tried.
@@ShanesCows Thank you so much
Another great video Shane! Always learning something new when a new one is released.
In the second workflow, the trigger was looking for a change to a Docusign envelope (assuming ANY envelope). If there were a number of similiar flows that were sending different document types e.g one flow to request a signature for an NDA and another flow to send a document for signature for a sales proposal, is there a way to differentiate which type of document is being responded to? This would be useful if you wanted the responses to NDAs copied to a different library than the sales proposals.
Not sure if there is a better answer but here is my first thought.
Create one flow that triggers when anything changes. Then get the envelope. Now check the metadata of your envelope for some metadata that tells you what it is (I am sure this exists, hope) and then have a Switch to build different logic for different types. Hope that helps but that is high level how I would think about it not ever doing it.
Thanks Shane!
Thank you Shane. I have been trying to get the Army to send my "Solutions" Team to your PowerApps University for 1.5 years. The request is still valid in the system, maybe this is the year. :( It looks like DoD is getting pitched by DocuSign. This will be the video I assign to my team to watch if they buy in. LOL You are my go-to when someone in my HQ asks me how to do something, and I don't have time to do it for them.
Hi Shane !
Thank you so much for all the great contents that you have created and helped power platform community.
PowerApps is great, unfortunately it is not available for personal projects outside of organization. What would be the closest alternative platform to develop personal webapps with same user experience ? Thanks.
I am not sure. I have never strayed from Power Apps. Maybe ask Copilot or ChatGPT for some suggestions? 🤩
Hello. Is the associated App for the docusign flow available? Thanks.
You know I didn't really build that one for download because of all of the new connections I was learning. Is there a part you are looking for? I could probably add the flow to the RUclips library pretty easy. The app would take a bit more though.
Love it! One question, though. If the signed document needs to be stored as an attachment to a list item, how do you determine which list item to attach it to? Is there a parameter that can be attached to the document when you send it to DocuSign (for example, the SP row id) that could be retrieved when the document is completed?
One way is to use Docusign tabs (text/number etc.) to store the id when document is generated and retrieve tab info when envelope is completed.
Thx for this content. If one converts from free to paid, would the flow steps also convert automatically, or would one need to rebuild each step?
I imagine you would have to change the flow. I will try to get a straight answer though.
There's a separate "Production" Docusign Connector for Non-Demo Docusign in Power Automate. It has the same exact actions as the demo version. Basically, you would need to use the Production Docusign Connector instead of the demo one. So, it doesn't convert, technically, yes you would need to create the power automate using the prod docusign actions.
The flow steps will not convert automatically. You will need to build a new flow using the Production connector (Docusign not 'Docusign Demo'). Please note: Docusign connectors are standard and you do not need a premium license to use any Docusign actions.
Looking at this in our organisation, what would be useful is to track the all the document progress in a sharepoint site lists. tracking who templated documents are with and thier current status. We were able to achieve this adobe sign but havent been able to since me moved to docusign, im sure it must be possible
Hmm. I am not sure. I will try to get someone to look at this for you.
Docusign has triggers based on Envelopes so if the envelope is completed for example, Power Automate can create or update an item in SP list. However there isn't a trigger event for Power Automate as of now based on templates or usage of templates.
If only there was a former Power Platform evangelist working for DocuSign to answer all of our questions (cough**Jon Levesque**cough) 😊
I may or may not have texted him before I made this video. 😉
Hahahaha - oh we talk! :)
@@JonJLevesque great to hear that, Jon, miss your videos on Power Platform!
Salut @AdiCristea . Din RO? In sfarsit si altceva in afara de indeni paici. Faci de mult Power Apps?
Can you do this with sign now? Can you demo this with a multi page document?
I have never head of Sign Now, I will look at it. This would work with multi-page you would add more \s1\ tags in the HTML would be the only difference.
How about making the PDF with the new PDF function in PowerApp? 😅
The new PDF function is still experimental and really shouldn't be used in Production apps. It has a lot of challenges still so I make them the way I can control.