Basic – DocuSign for Power Automate
Contents
DocuSign is a cloud-based electronic signature platform that lets individuals and businesses sign, send, and manage documents digitally. In the Power Platform, specifically Power Automate itself, DocuSign publishes 2 connectors: the DocuSign connector and the DocuSign Demo connector.
Here is the list of the differences between them:
| Type | Sign Up URL | Description |
|---|---|---|
| Production | Docusign Login – Enter email to start sign in | – Production purposes – Only letting you send 3 envelopes. – The account given will not allow you to explore the full capabilities. |
| Sandbox | Docusign Login – Enter email to start sign in | – Development purposes – Unlimited testing – Full features capabilities, including letting you try Signing Groups |
Please note, you need to use the correct connector based on your account type. For example, in this blog post, I’m using all the actions under the DocuSign Demo connector.
How it works
To understand how it works, we need to know the journey of eSignature from the DocuSign perspective:

DocuSign Envelope creation
Envelope
As you can see in the above diagram, the Envelope is the first thing that we need to create. In the Envelope, we need to set the Email subject (100 chars at max), Account, and the Email body (optional – 10000 chars at max):

Create envelope action
Recipient(s)
Next, we need to define who the stakeholders are for the envelope. We can define the Recipient type, such as:
-
- Allow to Edit
- In-Person Signer
- Needs to Sign
- Needs to View
- Receives a Copy
- Signs with Witness
- Specify Recipient
- Update Recipients
For this blog post, we focus on the Needs to Sign only, as I have not yet been exposed to the other selections. I think Allow to Edit, Needs to View, and Receives a Copy are more into the behavior of how the recipient responds to the envelope in the system. But for In-Person Signer, Signs with Witness, I need to dig deeper into how it works. If you know how it works, please feel free to let me know.
By defining the recipient, we can also define if the Envelope needs to be signed by multiple people:

Add recipient action
Document(s)
To add document(s), we need to supply the Account, Envelope Id, and also the document information(s) such as documentBase64, fileExtensions, name (of the file), transformPdfField (if you want to automatically upload the document as pdf), and assignTabsToRecipientId (If there are multiple recipient, you need to set the correct recipientId here):

Add documents to an envelope action
Define Dynamics Field Values, Signature, and Date Signed
If you have a requirement to populate dynamics content into the document, then you can define the tag with the format of “/custom-tag/” and set it to white font color. For example, this is the document that I set for this blog post:

Sample document with several fields
There are several “Tab types” that DocuSign supports (tab, basically, kinda like a dynamic component). For the above, you can see we will implement the Text, Signature, and Date Signed tab.
As you can see in the above, you can see \Party_A\, \Party_B\, etc. Those texts need to be set to white font color, and the document will end up like this:

After setting the Font Color to white
Populate Dynamic Text Fields
Again, in the above screenshot, you will notice that I set several custom text fields that need to be populated in the system, such as \Party_A\, \Party_B\, \FullName1\, and \FullName2\. To achieve those, we need to use “Add tabs for a recipient on an envelope“:

Populate Text fields
First, we need to set the Account, Envelope, and the Recipient ID of the action. Then, for the tabs, you can set:
| Property | Description |
|---|---|
| Anchor String | The tag that you want to replace. Eg: \Party_A\ |
| Value | Replace the Anchor String with the value that you want to submit. |
| Required | true/false. Whether the value is mandatory/non-mandatory. |
| Validation Pattern | Regex based |
| Validation Message | Shows when the value is invalid |
| Label | Label |
| Anchor X | Change the X position of the Value in the document |
| Anchor Y | Change the Y position of the Value in the document |
| Font | Font to be applied to the value. E.g.: Arial, Calibri. |
| Font Color | Font Color. E.g.: Black, Red, Blue |
| Font Size | Font Size. E.g.: Size10, Size11 |
| Bold | true/false |
| Italic | true/false |
Here is the peek code that I applied for the tab:
[
{
"anchorString": "\\Party_A\\",
"value": "Insurgo Blog",
"anchorYOffset": "-6",
"font": "Calibri",
"fontColor": "Black",
"fontSize": "Size12",
"bold": "true"
},
{
"anchorString": "\\Party_B\\",
"value": "Clarisse Sdn Bhd",
"anchorYOffset": "-6",
"font": "Calibri",
"fontColor": "Black",
"fontSize": "Size12",
"bold": "true"
},
{
"anchorString": "\\FullName1\\",
"value": "Temmy Wahyu Raharjo",
"anchorYOffset": "-6",
"font": "Calibri",
"fontColor": "Black",
"fontSize": "Size12",
"bold": "true"
},
{
"anchorString": "\\FullName2\\",
"value": "Jeanetta Clarisse Raharjo",
"anchorYOffset": "-6",
"font": "Calibri",
"fontColor": "Black",
"fontSize": "Size12",
"bold": "true"
}
]
Populate Date Signed
Similar to the Text tab, here are the settings that we need to apply to set the Date Signed tab (simpler than the Text tab):

Date Signed tab
Set Signature tab
Here are the settings for the Signature tab:

Signature tab
For the Signature tab, the most important thing is to set the correct recipient Anchor String and the Recipient if you define multiple recipients.
Send
Last part, after we defined everything, we just need to use the “Send envelope” action. The settings are also very simple:

Send envelope action
Result
If I invoke the Flow, I will get an email:

Email notification
Then, when the first person opens the Envelope, it will show this:

First signature
Once the first person signs, it will route the Envelope to the second person to sign:

Second Signature
Happy CRM-ing, and hopefully you learn something!
About the author

Dynamics CRM CE Technical Consultant | Power Platform | Dataverse | Blogger | MVP Business Applications | Loves the concept of Test Driven Development | Certified MCP | Certified Scrum Master
Raharjo, T (04/02/2026) Basic – DocuSign for Power Automate. Basic – DocuSign for Power Automate – Temmy Wahyu Raharjo