Skip to main content

RSign - Microsoft Power Automate: User guide

Updated

The certified RSign® connector brings secure, legally binding e-signatures to the Microsoft Power Automate. By natively integrating RSign® with Power Automate, users can build document workflows without writing code. From automating complex signature cycles to managing real-time request statuses, RSign® streamlines digital processes directly within the Microsoft ecosystem.

This article covers the following topics:

 

Pre-requisites

To use RSign® in the Power Platform apps, you will need the following.

On the RSign side

- Active RSign® login credentials and an appropriate RSign® user plan.

- Access to the RSign® APIs and your company’s unique Reference Key. (If you don’t have your Reference Key, please contact your RPost® representative)

On the Microsoft side

- An active Premium account with proper access to the apps and capabilities required by your integration (the plan should include access to custom connectors).

Note: Microsoft Power Platform users are responsible for their own Microsoft plans and billing.

 

Actions supported in the RSign® certified connector

The certified RSign® connector allows you to set up various actions to send e-signature requests and manage them in your own automated workflows/apps, among other actions. Here are the currently available actions you can set up with RSign in Microsoft Power Automate:

- Get AuthToken: Authenticates the user based on their RSign® credentials and retrieves a necessary token (AuthToken) required for all subsequent actions.

- Send Envelope Using a Template: Sends an eSignature request to the selected recipients using a pre-configured RSign® template. Check this article to learn how to use RSign® Templates.

- Send Envelope Using a Rule: Sends an eSignature request to selected recipients using a pre-configured RSign® rule. Check this article to learn how to use RSign® Rules.

- Retrieve Template Information: Retrieves the information about a Template or Rule based on its Code. Among the information returned is the Template name, documents and roles defined when creating that template on RSign® Web.

- Retrieve Envelope Status: Retrieves the status of an Envelope based on its Envelope Code.

- Retrieve Envelope Documents: Retrieves the documents part of an Envelope based on its Envelope Code. It retrieves the original and/or the Final Signed Documents.

 

How to create Flows with RSign® in Power Automate

To start creating Flows with RSign® in Power Automate, follow these steps:

1. In the Power Automate home page, click on Create:

1.png

2. Then, select any of the three possible ways to create a flow (the one you use will depend on the type of flow you need or your current workflow). In this guide we will use the Instant cloud flow option:

2.png

3. Choose the name and the trigger for your flow, and click on Create:

3.png

4. In the editor interface, click on the + icon to add a new action to the flow. On the Add an action window, type RSign and you’ll see all the RSign supported actions:

4.png

5. Select the action you want to use for the flow from the list of available actions. In this guide, we’ll use the Send Envelope using a Template:

5.png

6. Customize your action settings as needed and add as many actions as you need to achieve your required workflow.

Note: For all flows using the RSign connector, you will always need to add the Get AuthToken action first, to get a token that will be used in all subsequent RSign actions.

6.png

7. Once you have finished setting up your flow, save it and test it. After a successful test, your flow will be turned on and will run according to your configuration.

7.png

 

How to use RSign® webhooks in Power Automate

To use RSign® webhooks in Power Automate as a trigger for your Flows, follow these steps:

1. Create a Flow in Power Automate and click on the Add a trigger button. Then, search for the Request trigger in the Built-in tools group:

8.png

2. Then, click on the Request trigger and select the When an HTTP request is received. This will make it so that the flow will trigger each time an HTTP request (webhook notification) is sent from RSign to your flow.

9.png

3. On Who can trigger the flow?, select Anyone and on the Request Body JSON Schema paste the following JSON schema.

{
    "type": "object",
    "properties": {
        "EnvelopeId": {
            "type": "string"
        },
        "EnvelopeCode": {
            "type": "string"
        },
        "SenderEmail": {
            "type": "string"
        },
        "EnvelopeStatus": {
            "type": "string"
        },
        "EnvelopeStatusOld": {
            "type": "string"
        },
        "Timestamp": {
            "type": "string"
        },
        "SignerEmail": {
            "type": "string"
        },
        "SignerStatus": {
            "type": "string"
        },
        "ReferenceCode": {
            "type": "integer"
        },
        "ReferenceEmail": {
            "type": "string"
        }
    }
}
10.png

4. Continue setting up your Flow as needed, adding all the actions you need. Once finished, click on Save. Power Automate will generate a unique URL for your Flow. Copy the generated URL.

11.png

5. Go to RSign® and enter the URL in the URL field of your RSign® webhook settings.

12.png

Visit this article to learn more about how to configure RSign® webhooks for your account.