Overview

Microsoft Flow is a tool that connects different apps and services into coordinated multi-step workflows so that repetitive tasks can be automated without the need for complex API coding. 

There are three Flow concepts that drive all workflows. The first is that all services can expose their API through a Connector to the service.  Connectors may have Triggers that start flows.  Connectors must have Actions that drive what happens within the Flow.  There are common logical connectors between actions that control the workflow based on parameters generated by previous actions.

Adobe Sign is a natural participant in this ecosystem because the nature of signature processes usually involves preparation and review of the agreement prior to signature and notification and archival of the document after the agreement is signed.

Flow creates an environment where any supported service can be connected to another.  Use cases for the Adobe Sign connector include:

  • Starting a signature process from a service trigger
  • Getting the status of a Sign process
  • Moving documents from the Sign service to other repositories.

Prerequisites

Adobe Sign for Microsoft Flow requires an active enterprise service plan with Adobe Sign.

Supported platforms:

  • Office 365 – Using:
    • Chrome v59+
    • Firefox v53+
    • Safari 9+
    • Edge 38+
    • IE 11+


IE/Edge browsers

For Flow to work seamlessly in Internet Explorer and Edge browsers, you must trust the below sites in your browser security configuration:

  • https://*.echocdn.com
  • https://*.echosign.com
  • https://*.microsoftonline.com
  • https://*.office.com
  • https://*.office365.com
  • https://*.live.com (If using a Live account)
  • https://*.sharepoint.com
  • If using a third-party identity management system, that URL needs to be added as well

Accessing the Flow interface

To access the Flow interface, you only need to log into your Microsoft 365 organization, click the applications icon at the top-left of the window, and select Flow.

  • If the Flow option is not available to you, contact your Microsoft 365 administrator

Upon clicking the Flow icon, you are redirected to the Flow home page: flow.microsoft.com

access_flow

On the Flow homepage:

  • Click the Connectors link at the top of the page
  • Type Adobe Sign into the Search field
  • Select the Adobe Sign connector
find_the_adobe_signconnector2

Adobe Sign Triggers

Triggers

A trigger is an event or change that is used to start a flow.

Adobe Sign triggers are predicated on changing values within the Adobe Sign application, which means that a Webhook must be established to trap and pass meaningful changes.

  • Every trigger requires a Name value which is any identifiable string the user wants to use
  • Every trigger requires a Scope. This limits the number of agreements that are included in the webhook, and as a direct result, the number of times the flow is triggered
    • Scope is important when a flow is designed that encompasses more than the indivudual user
    • Only Adobe Sign Account admins can create a flow with an Account level scope, which would trigger for every agreement created in the account, regardless as to the user that originally created it
    • Adobe Sign Group admins can only create Scopes for their group in Adobe Sign. This type of flow would trigger for every agreement created by users within the admins group
    • Flows created by Adobe Sign users that are not privileged as admins, but define a scope at the Account or Group level, will never trigger
  • By configuring your trigger, MS Flow generates a unique HTTPS URL unique to that flow and automatically registers that with Adobe Sign

Note:

It's worth noting that Adobe Sign actions do not require an Adobe Sign trigger to be used. 

If you have another source for your triggers, then the Adobe Sign actions are still viable in your Flows.

List of Adobe Sign Triggers

Trigger Summary Description

When a new agreement is created

Trigger a flow whenever an agreement is created in your account/group/user (depending upon the scope defined in the webhook). 

When an agreement is sent to a participant

Trigger a flow whenever an agreement related to your account/group/user/on a specific agreement  (depending upon the scope defined in the webhook) is sent to a recipient. 

When an agreement workflow is completed successfully

Trigger a flow whenever an agreement workflow is completed successfully in your account/group/user/on a specific agreement (depending upon the scope defined in the webhook). 

When the state of an agreement changes

Trigger a flow whenever the state of an agreement gets changed in your account/group/user/on a specific agreement (depending upon the scope defined in the webhook). 

When an event occurs

Trigger a flow whenever the event occurs in your account/group/user/on a specific resource (depending upon the scope defined in the webhook). 

When a new agreement is created

Trigger a Flow whenever an agreement is created in your account/group/user (depending upon the scope defined in the trigger). 

This is restricted to Account/Group/User Scopes for an Agreement resource only.

Input Parameter Required? Description

Name

Yes The Name of the trigger

Scope (account/group/user)

Yes The Scope of the trigger

Agreement Conditional Params

1) Include Agreement Info ?

2) Include Agreement Participants Info ?

3) Include Agreement Document Info ?

Optional Conditionals Params that define the data in the payload
1_when_a_new_agreementiscreated

When an agreement is sent to a participant

Trigger a Flow whenever an agreement created in your account/group/user (depending upon the scope defined in the trigger) is sent to a recipient. 

Applicable for the Agreement resource only.

Input Parameter Required? Description

Name

Yes The Name of the trigger

Scope (account/group/user/on a specific agreement)

Yes The Scope of the trigger
Agreement Name/ID

Optional

Specify only when scope is limited to a specific agreement

Agreement Conditional Params

1) Include Agreement Info ?

2) Include Agreement Participants Info ?

3) Include Agreement Document Info ?

4) Include Agreement Signed Document Info ?

 

Optional Conditionals Params that define the data in the payload
2_when_an_agreementissenttoaparticipant

Note:

The signature requested event gets broadcasted for both when you are the sender, and when your signature is requested. This means:

Case 1: Sender will receive notifications, whenever a signature request is made by me.

Whenever the sender has asked for signatures, the sender will be notified on the webhook URL she provided while creating the webhook.

Case 2: Signer will receive notifications, whenever a signature request is made for them.

Whenever the agreement arrives asking for my signatures, the signer will be notified on the webhook URL they provided while creating the webhook.

 

Differentiating the two cases:

The webhook payload data specifies the participant email on triggers created for "Any of my agreements". 

For the Sender side, the participant email will not be equal to the user’s email who created the webhook.

For the Signer side, the participant email will be equal to user’s email who created the webhook.

When an agreement workflow is completed successfully

Trigger a Flow whenever an Agreement workflow is completed successfully in your account/group/user/on a specific agreement (depending upon the scope defined in the trigger). 

Applicable for the Agreement resource only.

Input Parameter Required? Description

Name

Yes The Name of the trigger

Scope (account/group/user/on a specific agreement)

Yes The Scope of the trigger
Agreement Name/ID

Optional

Specify only when scope is limited to a specific agreement

Agreement Conditional Params

1) Include Agreement Info ?

2) Include Agreement Participants Info ?

3) Include Agreement Document Info ?

4) Include Agreement Signed Document Info ?

 

Optional Conditionals Params that define the data in the payload
3_when_an_agreementiscompletedsuccessfully

When the state of an agreement changes

Trigger a Flow whenever the state of an agreement gets changed in your account/group/user/on a specific agreement (depending upon the scope defined in the trigger). 

Applicable for the Agreement resource only.

Input Parameter Required? Description

Name

Yes The Name of the trigger

Scope (account/group/user/on a specific agreement)

Yes The Scope of the trigger
Events Yes

Event Set to choose from

"When an agreement is created",
"When a participant completes their action",
"When an agreement workflow is completed successfully",
"When an agreement is cancelled",
"When an agreement is rejected by a participant",
"When an agreement expires"

Agreement Name/ID

Optional

Specify only when scope is limited to a specific agreement

Agreement Conditional Params

1) Include Agreement Info ?

2) Include Agreement Participants Info ?

3) Include Agreement Document Info ?

4) Include Agreement Signed Document Info ?

Optional Conditionals Params that define the data in the payload
4_when_the_stateofanagreementchanges

When an event occurs

Trigger a Flow whenever the event occurs in your account/group/user/on a specific resource (depending upon the scope defined in the trigger). 

Applicable for Agreement, Megasign, and Widget resources.

Input Parameter Required? Description

Name

Yes The Name of the trigger

Scope (account/group/user/on a specific resource)

Yes The Scope of the trigger
Events Yes

Event Set to choose from

"When any agreement event occurs", 
"When an agreement is created",
"When an agreement is sent",
"When a participant completes their action",
"When an agreement workflow is completed successfully",
"When an agreement expires", 
"When an agreement is deleted",
"When an agreement is cancelled",
"When an agreement is rejected by a participant",
"When an agreement is shared",
"When an agreement is delegated",
"When an agreement participant is replaced",
"When an agreement is modified",
"When an agreement modification is acknowledged",
"When an agreement email is viewed by a participant",
"When an agreement email gets bounced",
"When an agreement creation fails",
"When an offline agreement is synced",
"When an agreement is uploaded by sender",
"When an agreement is vaulted",
"When an agreement participant is authenticated through social identity",
"When an agreement participant is authenticated through KBA", 
"When any mega sign event occurs",
"When a mega sign is created",
"When a mega sign is shared", 
"When a mega sign is recalled",
"When any widget event occurs"
"When a widget is created", 
"When a widget is enabled",
"When a widget is disabled",
"When a widget is modified",
"When a widget is shared",
"When a widget creation fails"

Resource Type Optional

Specify only when scope is limited to a specific resource

Resource ID

Optional

Specify only when scope is limited to a specific resource

Agreement Conditional Params

1) Include Agreement Info ?

2) Include Agreement Participants Info ?

3) Include Agreement Document Info ?

4) Include Agreement Signed Document Info ?

Mega Sign Conditional Params

1) Include Mega Sign Info ?

Widget Conditional Params

1) Include Widget Info ?

2) Include Widget Participants Info ?

3) Include Widget Document Info ?

Optional Conditionals Params that define the data in the payload
5_when_an_event_occurs

Adobe Sign Actions

Actions 

An action represents what you want to happen after the flow is triggered. Actions allow users to perform operations that can create, send, or evaluate agreements associated to the users of an Adobe Sign account.

Each action has one or more required (and/or optional) inputs that are needed for the action to be implemented correctly. These inputs come from triggers or other actions earlier in the flow.

The action produces an output that is either a desired asset (a downloaded agreement in the form of a file stream) or values to be used in subsequent actions.

List of Adobe Sign Actions

Action Summary Description

Upload a document and get a document ID

Uploads a file stream to Adobe Sign and produces a document ID for subsequent actions
Create an agreement from an uploaded document and send for signature Uses a document ID to create and send an agreement
Create a library template from an uploaded document Uses a document ID to create a new library template in Adobe Sign
Create an agreement from a document URL and send for signature

Uses a supplied URL to retrieve a file, create, and then send a new agreement

Create a library template from a document URL Uses a supplied URL to retrieve a file and then create a new library template in Adobe Sign
Create an agreement from a library template and send for signature Uses an Adobe Sign library template to create and send a new agreement

Get a list of all agreements

Returns a list of all agreements for the user
Get a list of all library templates Return a list of all Adobe Sign library templates on your account
Get the status of an agreement

Returns all of the data associated with an agreement

Get a list of all the document IDs from an agreement

Returns a list of all documentIDs associated with the agreement, including any uploaded during signing
Get a PDF of a signed agreement Returns the signed PDF from an agreement

Get a document from an agreement

Returns one specific document from an agreement

Upload a document and get a document ID

This action is designed to accept a file from the trigger, or previous action, to produce a unique document ID that subsequent actions can utilize for processing the file into an agreement or template.

Required Input Parameters  Description Default Value
File-Name The name of the document being uploaded. None
File Content The file to be uploaded. None
action_-_upload_adocumentandgetadocumentid

 

The only output of this function is the unique document ID

Output Parameters Description
Document ID The unique Id of the uploaded document

Create an agreement from an uploaded document and send for signature

This action is designed to create and send a document for signature, based on the document ID provided by the Upload a document and get a document ID action.

 

Advanced options

  • Can be configured to include up to seven recipients
    • Individual roles can be set for each recipient
  • Up to eight files can be attached from the Adobe Sign library
  • A custom message can be applied
  • The agreement can be set to expire after a set number of days
  • Reminders can be configured: Daily, Weekly or defined by a custom dynamic value
  • A password to secure the final PDF after all signatures are obtained.
  • Up to ten (text tagged) fields within the attached files can be pre populated with static or dynamic values derived from previous trigger/actions in the flow
Required Input Parameters  Description

Default Value

Agreement Name The name of the agreement. None
Document ID The document ID received by uploading a document None
Signature Type The type of signature: E-signature or Written E-Signature
Recipient Email Email of the recipient None
Recipient Signing Order Signing index, starting with 1, that governs the signing order when there are multiple recipients 1
Recipient Role The role of recipient SIGNER
Create an agreement from an uploaded document and send for signature - Rebranded

 

The output of this action

Output Parameters Description
Agreement Id The unique agreement identifier that can be used to query status and download signed documents

Create a library template from an uploaded document

This action is designed to create a new Adobe Sign library template using an uploaded file document ID (via the Upload a document and get a document ID action).

Up to eight document IDs can be included to create the library template.

Required Input Parameters  Description Default Value
Template Name The name of the library template as it will be shown in the Adobe Sign library. None
Template Type The type of library template: Reusable Document, Reusable form field layer, or Both

 

Reusable Document
Share with Specifies who, within your Adobe Sign account, should have access to this library document: Only me, Any user in my group, or Any user in my organization Only me
Document ID The document ID received from the Upload a document and get a document ID action None
Create a library template from an uploaded document - Rebranded

 

The output of this action

Output Parameters Description
Library Template Id The unique identifier that can be used to refer to the library template

Create an agreement from a document URL and send for signature

This action is designed to create and send a document for signature, based on a file accessed through a public URL.

 

Advanced options

  • Can be configured to include up to seven recipients
    • Individual roles can be set for each recipient
  • Up to eight files can be attached from the Adobe Sign library
  • A custom message can be applied
  • The agreement can be set to expire after a set number of days
  • Reminders can be configured: Daily, Weekly or defined by a custom dynamic value
  • A password to secure the final PDF after all signatures are obtained.
  • Up to ten (text tagged) fields within the attached files can be pre populated with static or dynamic values derived from previous trigger/actions in the flow
Required Input Parameters  Description Default Value
Agreement Name The name of the agreement None
Document URL A publicly accessible URL for retrieving the document None
Document Name  The name of the referenced document, with extension None
Signature Type The type of signature: E-signature or Written E-Signature
Recipient Email Email address of the recipient None
Recipient Signing Order Signing index, starting with 1, that governs the signing order when there are multiple recipients
1
Recipient Role The role of recipient SIGNER
Create an agreement from a document URL and send for signature - Rebranded

 

The output of this action

Output Parameters Description
Agreement Id The unique agreement identifier that can be used to query status and download signed documents

Create a library template from a document URL

This action is designed to create an Adobe Sign library template from a publicly accessible URL, and return a library template ID that can be used to send a new agreement.

Up to eight files can be attached to make the library template.

Required Input Parameters  Description Default Value
Template Name The name of the library template as it will be shown in the Adobe Sign library. None
Template Type The type of library template: Reusable DocumentReusable form field layer, or Both

 

Reusable Document
Share with Specifies who, within your Adobe Sign account, should have access to this library document: Only meAny user in my group, or Any user in my organization Only me
Document URL A publicly accessible URL for retrieving the document None
Document Name  The name of the referenced document, with extension None
Create a library template from a document URL - Rebranded

 

The output of this action

Output Parameters Description
Library Template Id The unique identifier that can be used to refer to the library template

Create an agreement from a library template and send for signature

This action is designed to accept a trigger action, and send a predetermined file from the Adobe Sign library to a configured recipient.

 

Advanced options

  • Can be configured to include up to seven recipients
    • Individual roles can be set for each recipient
  • Up to eight files can be attached from the Adobe Sign library
  • A custom message can be applied
  • The agreement can be set to expire after a set number of days
  • Reminders can be configured: Daily, Weekly or defined by a custom dynamic value
  • A password to secure the final PDF after all signatures are obtained.
  • Up to ten (text tagged) fields within the attached files can be pre populated with static or dynamic values derived from previous trigger/actions in the flow
Required Input Parameters  Description Default Value
Agreement Name The name of the agreement None
Document Library Template The Adobe Sign library template which will be used as the Document source when creating the agreement None
Signature Type The type of signature to be applied: E-signature or Written E-Signature
Recipient Email Email address of the recipient None
Recipient Signing Order Signing index, starting with 1, that governs the signing order when there are multiple recipients 1
Recipient Role The role of recipient SIGNER
Create an agreement from a library template and send for signature - Rebranded

 

The output of this action

Output Parameters Description
Agreement Id The unique identifier that can be used to query status and download signed documents

Get a list of all agreements

This action is used to return all the agreements in a user's account.

The returned agreement list can further be manipulated and operated for different use cases.

Get a list of all agreements - Rebreanded

 

The output of this action produces an array of agreements. Each agreement in the array contains:

Output Parameters Description
Agreement ID A unique ID that can be used to uniquely identify the agreement
Display Date The display date for the agreement
Esign True if the agreement is using an E-signature workflow; False if the agreement is using a Written signature workflow
Latest Version ID A version ID which uniquely identifies the current version of the agreement
Name Name of the Agreement

Follow-up actions to this action could be:

  • Get the status of an agreement
  • Get a list of all the document IDs from an agreement
  • Get a PDF of a signed agreement
  • Get a document from an agreement

Get a list of all library templates

This action is used to retrieve the list of the Adobe Sign library templates available to the user.

get_a_list_of_alllibrarytemplates

 

The output of this action is an array of library templates. Each template record includes:

Output Parameters Description
Library Template Id The unique ID of the library document used when sending the document to be signed
Library Template Name The name of the library template
Modified Date The day on which the library template was last modified
Template Sharing Mode The scope of visibility of the library template: Only me, Any user in my group, or Any user in my organization

Get the status of an agreement

This action is designed to return all the current information regarding one agreement, as identified by the agreement ID.

Required Input Parameters  Description Default Value
Agreement ID The agreement ID of the agreement whose information is needed None
action_-_get_thestatusofanagreement

 

The output of this action includes the agreement level data:

Output Parameters Description
Agreement ID  A unique ID that can be used to uniquely identify the agreement
Agreement Name The name of the agreement
CCs Email Email addresses of the CC'd parties
Created Date The date the agreement was created
Expiration Date The date after which the agreement can no longer be signed
Locale The language (locale) used for the agreement
Message The message associated with the agreement that the sender has provided
Document Protection Indicates whether or not a password is required to view the signed PDF
Signature Type Indicates the Signature workflow that was requested: E-signature or Written
Status The current status of the agreement
Workflow ID The ID of a custom workflow which defines the routing path of an agreement

 

An array of recipients for the agreement. Each recipient contains:

Output Parameters Description
Participant Email Email address of the participant that initiated the event
Participant Set ID The unique ID of the participant set
Private Message Private message for the participant
Signing Order Index starting with 1, that tells the order in which this recipient signs
Status The participant set status with respect to the document

Get a list of all the document IDs from an agreement

This action is designed to list all of the document IDs that are connected to one agreement.

Supporting documents (files uploaded during the signature process) can also be listed in either the original format or as a PDF.

Required Input Parameters  Description Default Value
Agreement Id The agreement identifier, as returned by the agreement creation API or retrieved from the API to fetch agreements. None
Get a list of all the document IDs from an agreement - Rebranded

 

The output of this action is the meta data of the original file that was uploaded:

Output Parameters Description
Document ID Unique ID of the document
Mime Type The Mime type of the document
Name The name of the document
Num Pages Number of pages in the document

 

Supporting documents are presented in an array, with each document containing:

Output Parameters Description
Supporting Document Name Display name of the supporting document
Supporting Document Field Name The name of the field that the supporting document was uploaded to
Supporting Document Mime Type The Mime type of the supporting document
Supporting Document Pages Number of pages in the supporting document
Supporting Document ID Unique Id representing the supporting document

Get a PDF of a signed agreement

This action is designed to download the signed PDF from the identified agreement.

 

Additional Options

  • Include supporting documents added to the agreement during the signature process
  • Include the Audit Report for the agreement
Required Input Parameters  Description Default Value
Agreement ID The agreement ID as provided by the action that creates the agreement None
Get a PDF of a signed agreement - Rebranded

 

The output of this action for each downloaded file:

Output Parameters Description
File Content The file stream of the document
File Content Size The content type of the response
File Content Type The content size of the response

Get a document from an agreement

This action is designed to download a specific document ID from an agreement.

Required Input Parameters  Description Default Value
Agreement ID The agreement ID of the agreement whose document is needed None
Document ID The document ID of the specific document of the agreement None 
Get a document from an agreement - Rebranded

 

The output of this action is:

Output Parameters  Description
File Content  The file stream of the document
File Content Size  The content type of the response
File Content Type The content size of the response

Templates

Adobe Sign provides a number of pre-made templates for common document connectors, such as Creative Cloud and Microsoft SharePoint.

To access the templates:

  • Go to the Flow Home page
  • Click on Templates in the top row of options
  • Type Adobe Sign in the Search field
select_a_template

Examples

Get signatures on a new asset in Creative Cloud

Description of the Flow

When a new asset is added in Adobe Creative Cloud, trigger the Flow to get the Asset ID of the newly added file.

Upload the file (identified by the Asset ID) to Adobe Sign using the Upload a document and get a document ID action.

The Create agreement and send for signature action uses the DocumentId to create and send an agreement based on the uploaded file.

Once the agreement is sent, a notification is sent to the user on the Microsoft flow mobile application using the Send me a mobile notification action.

Prerequisites

Users need to establish a connection with Adobe Creative Cloud and Adobe Sign.

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name
1 Trigger Adobe Creative Cloud When an asset is added
2 Action Adobe Creative Cloud Get asset contents using asset id
3 Action Adobe Sign Upload a document and get a document ID
4 Action Adobe Sign Create agreement and send for signature
5 Action Adobe Sign Send me a mobile notification
  1. Step 1 - Trigger: When an asset is added to Creative Cloud

    When a new item is created under a user specified list, in a particular site, this trigger initiates the Flow.

    1_1
  2. Step 2 - Action: Get asset contents using asset id

    Capture the Asset ID that relates to the asset contents, including the asset name and the file stream.

    1_2

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Asset Name Yes Auto-filled through the output response of the trigger event The name of the asset being added Basic
  3. Step 3 - Action: Upload a document and get a document ID

    Creates a document ID from the uploaded file.

    Automatically populated values pulled from the previous action:

    • File Name : The name of the document that has been uploaded
    • File Content : The file stream of the uploaded document
    1_3

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Asset Name Yes Auto-filled by the output response from the "When an asset is added" trigger  The name of the asset being added Basic

    Asset

    Contents

    Yes Auto-filled by the output response from the "Get asset contents using asset id" action The Asset content of the document to be added in Adobe Creative Cloud. Basic
  4. Step 4 - Action: Create an agreement from an uploaded document and send for signature

    Using the document ID as the file, an agreement is configured to include a list of recipients, a signing order, and a signature type.

    The following output values from the previous action are auto-populated :

    • Document Id - The unique ID received by uploading the document
    • Asset Name - The name of asset that was uploaded; to be used as name of the agreement
    1_4

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Agreement Name Yes Auto-filled by the output response from the "When an asset is added" trigger This value is auto-filled in the template Basic
    Document Id Yes Auto-filled by the output response from the "Upload a document and get a document ID" action This value is auto-filled in the template Basic
    Signature Type Yes E-Signature Specifies the Signature Type Basic
    Recipient Email No To be specified by the user The recipient email to which the agreement is being sent for signature Basic
    Recipient Signing Order Yes
    1 Start from 1 Basic
    Recipient Role Yes SIGNER The role of the recipient Basic
    Message Yes

    Please review and complete this document

    An optional message to the recipients requesting their action

    Basic
  5. Step 5 - Action: Send me a mobile notification

    After the agreement is configured and sent, notification about the successful creation of the agreement is sent to the user

    The following output values from the previous action are auto-populated :

    • Asset Name
    1_5

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Text Yes

    Your agreement <FILE_NAME> has been successfully sent for signature using Adobe Sign.

    The <FILE_NAME> value is auto-filled in the template Basic

Get signatures on a new file in Box

Description of the Flow

Creating a new file in a designated Box folder triggers the Flow.

The new file is uploaded to AdobeSign and a document ID is created.

The file, as identified by the document ID, is used as the base for a new agreement, and that agreement is sent for signature.

After the successful creation of the agreement, a notification is sent to the user on the Microsoft Flow mobile application.

Prerequisites

Users need to establish a connection with Adobe Sign and Box

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name
1. Trigger Box When a file is created
2. Action Adobe Sign Upload a document and get a document ID
3. Action Adobe Sign Create agreement and send for signature
4. Action Adobe Sign Send me a mobile notification
  1. Step 1 - Trigger: When a file is created in Box

    A specific folder ID must be configured in the Trigger by the user. This folder is monitored for any new files.

    Upon detection of a new file, the trigger starts the flow.

     

    2_1
    Field Name Default Value Value Comments Visibility
    Folder No To be specified by the user The folder that the trigger is monitoring Basic
  2. Step 2 - Action: Upload a document and get a document ID

    Creates a document ID from the uploaded file.

    Automatically populated values pulled from the previous action:

    • File Name : The name of the document that has been uploaded
    • File Content : The file stream of the uploaded document
    2_2

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    File Name Yes Auto-filled by the output response from the "When a file is created" trigger The name of the document to be uploaded Basic
    File Content Yes Auto-filled by the output response from the "When a file is created" trigger The File stream of the document to be uploaded Basic
  3. Step 3 - Action: Create an agreement from an uploaded document and send for signature

    Using the document ID as the file, an agreement is configured to include a list of recipients, a signing order, and a signature type.

    The following output values from the previous action are auto-populated :

    • Document Id - The unique ID received by uploading the document
    • File Name - The name of file that was created; to be used as name of the agreement
    2_3

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Agreement Name Yes Auto-filled by the output response from the "When an asset is added" trigger This value is auto-filled in the template Basic
    Document Id Yes Auto-filled by the output response from the "Upload a document and get a document ID" action This value is auto-filled in the template Basic
    Signature Type Yes E-Signature Specifies the Signature Type Basic
    Recipient Email No To be specified by the user The recipient email to which the agreement is being sent for signature Basic
    Recipient Signing Order Yes
    1 Start from 1 Basic
    Recipient Role Yes SIGNER The role of the recipient Basic
    Message Yes

    Please review and complete this document

    An optional message to the recipients requesting their action

    Advanced
  4. Step 4 - Action: Send me a mobile notification

    After the agreement is configured and sent, notification about the successful creation of the agreement is sent to the user

    The following output values from the previous action are auto-populated :

    • File Name
    2_4

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Text Yes

    Your agreement <FILE_NAME> has been successfully sent for signature using Adobe Sign.

    The <FILE_NAME> value is auto-filled in the template Basic

Get signatures on a new file in Dropbox

Description of the Flow

Creating a new file in a designated Dropbox folder triggers the Flow.

The new file is uploaded to AdobeSign and a document ID is created.

The file, as identified by the document ID, is used as the base for a new agreement, and that agreement is sent for signature.

After the successful creation of the agreement, a notification is sent to the user on the Microsoft Flow mobile application.

Prerequisites

Users need to establish a connection with Adobe Sign and Dropbox

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name
1. Trigger DropBox When a file is created
2. Action Adobe Sign Upload a document and get a document ID
3. Action Adobe Sign Create agreement and send for signature
4. Action Adobe Sign Send me a mobile notification
  1. Step 1 - Trigger: When a file is created in Dropbox

    A specific folder must be configured in the trigger by the user. This folder is monitored for any new files.

    Upon detection of a new file, the trigger starts the flow.

     

    3_1
    Field Name Default Value Value Comments Visibility
    Folder No To be specified by the user The folder that the trigger is monitoring Basic
  2. Step 2 - Action: Upload a document and get a document ID

    Creates a document ID from the uploaded file.

    Automatically populated values pulled from the previous action:

    • File Name : The name of the document that has been uploaded
    • File Content : The file stream of the uploaded document
    3_2

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    File Name Yes Auto-filled by the output response from the "When a file is created" trigger The name of the document to be uploaded Basic
    File Content Yes Auto-filled by the output response from the "When a file is created" trigger The File stream of the document to be uploaded Basic
  3. Step 3 - Action: Create an agreement from an uploaded document and send for signature

    Using the document ID as the file, an agreement is configured to include a list of recipients, a signing order, and a signature type.

    The following output values from the previous action are auto-populated :

    • Document Id 
    3_3

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Agreement Name Yes Auto-filled by the output response from the "When an asset is added" trigger This value is auto-filled in the template Basic
    Document Id Yes Auto-filled by the output response from the "Upload a document and get a document ID" action This value is auto-filled in the template Basic
    Signature Type Yes E-Signature Specifies the Signature Type Basic
    Recipient Email No To be specified by the user The recipient email to which the agreement is being sent for signature Basic
    Recipient Signing Order Yes
    1 Start from 1 Basic
    Recipient Role Yes SIGNER The role of the recipient Basic
    Message Yes

    Please review and complete this document

    An optional message to the recipients requesting their action

    Advanced
  4. Step 4 - Action: Send me a mobile notification

    After the agreement is configured and sent, notification about the successfully creation of the agreement is sent to the user

    The following output values from the previous action are auto-populated :

    • File Name
    3_4

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Text Yes

    Your agreement <FILE_NAME> has been successfully sent for signature using Adobe Sign.

    The <FILE_NAME> value is auto-filled in the template Basic

Get signatures on a new file in OneDrive

Description of the Flow

Creating a new file in a designated OneDrive folder triggers the Flow.

The new file is uploaded to AdobeSign and a document ID is created.

The file, as identified by document ID, is used as the base for a new agreement, and that agreement is sent for signature.

After the successful creation of the agreement, a notification is sent to the user on the Microsoft Flow mobile application.

Prerequisites

Users need to establish a connection with Adobe Sign and OneDrive

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name
1. Trigger OneDrive When a file is created
2. Action Adobe Sign Upload a document and get a document ID
3. Action Adobe Sign Create agreement and send for signature
4. Action Adobe Sign Send me a mobile notification
  1. Step 1 - Trigger: When a file is created in OneDrive

    A specific folder must be configured in the trigger by the user. This folder is monitored for any new files.

    Upon detection of a new file, the trigger starts the flow.

     

    4_1
    Field Name Default Value Value Comments Visibility
    Folder No To be specified by the user The folder that the trigger is monitoring Basic
  2. Step 2 - Action: Upload a document and get a document ID

    Creates a document ID from the uploaded file.

    Automatically populated values pulled from the previous action:

    • File Name : The name of the document that has been uploaded
    • File Content : The file stream of the uploaded document
    4_2

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    File Name Yes Auto-filled by the output response from the "When a file is created" trigger The name of the document to be uploaded Basic
    File Content Yes Auto-filled by the output response from the "When a file is created" trigger The File stream of the document to be uploaded Basic
  3. Step 3 - Action: Create an agreement from an uploaded document and send for signature

    Using the document ID as the file, an agreement is configured to include a list of recipients, a signing order, and a signature type.

    The following output values from the previous action are auto-populated :

    • Document Id 
    • File Name - The name of file that was created; to be used as name of the agreement
    4_3

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Agreement Name Yes Auto-filled by the output response from the "When an asset is added" trigger This value is auto-filled in the template Basic
    Document Id Yes Auto-filled by the output response from the "Upload a document and get a document ID" action This value is auto-filled in the template Basic
    Signature Type Yes E-Signature Specifies the Signature Type Basic
    Recipient Email No To be specified by the user The recipient email to which the agreement is being sent for signature Basic
    Recipient Signing Order Yes
    1 Start from 1 Basic
    Recipient Role Yes SIGNER The role of the recipient Basic
    Message Yes

    Please review and complete this document

    An optional message to the recipients requesting their action

    Basic
  4. Step 4 - Action: Send me a mobile notification

    After the agreement is configured and sent, notification about the successfully creation of the agreement is sent to the user

    The following output values from the previous action are auto-populated :

    • File Name
    4_4

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Text Yes

    Your agreement <FILE_NAME> has been successfully sent for signature using Adobe Sign.

    The <FILE_NAME> value is auto-filled in the template Basic

Get signatures on a new file in OneDrive for Business

Description of the Flow

Creating a new file in a designated OneDrive for Business folder triggers the Flow.

The new file is uploaded to AdobeSign and a document ID is created.

The file, as identified by the document ID, is used as the base for a new agreement, and that agreement is sent for signature.

After the successful creation of the agreement, a notification is sent to the user on the Microsoft Flow mobile application.

Prerequisites

Users need to establish a connection with Adobe Sign and OneDrive for Business

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step

Type

Connector

Operation Name

1.

Trigger

OneDrive for Business

When a file is created in OneDrive for Business

2.

Action

Adobe Sign

Upload a document and get a document ID

3.

Action

Adobe Sign

Create an agreement from an uploaded document and send for signature

4.

Action

Notification

Send me a mobile notification

  1. Step 1 - Trigger: When a file is created in OneDrive for Business

    A specific folder must be configured in the trigger by the user. This folder is monitored for any new files.

    Upon detection of a new file, the trigger starts the flow.

    ob3-1_trigger

    Field Name

    Need Default Value(Yes/No)

    Value

    Comments

    Visibility

    Folder

    No

    To be specified by the user while creating flow

    The folder on which the event is to be triggered

    Basic
  2. Step 2 - Action: Upload a document and get a document ID

    Creates a document ID from the uploaded file.

    Automatically populated values pulled from the previous action:

    • File Name : The name of the document that has been uploaded
    • File Content : The file stream of the uploaded document
    ob3-2_action_-_uploadadocument

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    File Name

    Yes

    Will come auto-filled by the output response of "When a file is created" trigger of OneDrive for Business.

    The name of the document to be uploaded

    Basic

    File Content

    Yes

    Will come auto-filled by the output response of "When a file is created" trigger of OneDrive for Business.

    The File stream of the document to be uploaded

    Basic
  3. Step 3 - Action: Create an agreement from an uploaded document and send for signature

    Using the document ID as the file, an agreement is configured to include a list of recipients, a signing order, and a signature type.

    The following output values from the previous action are auto-populated :

    • Document Id 
    • File Name - The name of file that was created; to be used as name of the agreement
    ob3-3_action_-_createagreement

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Agreement Name

    Yes

    Will come auto-filled by the output response of "When a file is created" trigger of OneDrive for Business. (File Name)

    The Name of the agreement.

    Basic

    Document ID

    Yes

    Will come auto-filled by the output response of "Upload a transient document and get a document ID".(Document ID)

    This value will be auto-filled in the template

    Basic

    Signature Type

    Yes

    E-Signature

    The type of signature you would like to request - E-signature or Written

    Basic

    Recipient Email

    No

    To be specified by the user while creating flow

    Email of the recipient

    Basic

    Recipient Signing Order

    Yes

    1

    It should start from 1

    Basic

    Recipient Role

    Yes

    Signer

    The role of the recipient

    Basic

    Message

    Yes

    Please review and complete this document.

    An optional message to the recipients requesting their action



    Basic
  4. Step 4 - Action: Send me a mobile notification

    After the agreement is configured and sent, notification about the successfully creation of the agreement is sent to the user

    The following output values from the previous action are auto-populated :

    • File Name
    ob3-4_action_-_sendnotification

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Text

    Yes

    Your agreement <FILE_NAME> has been successfully sent for approval using Adobe Sign.

    **Note : The <File_Name> Will come auto-filled by the output response of "When a file is created" trigger of OneDrive for Business.

    The value will be auto-filled in the template

     

Get approval on a new file in OneDrive for Business

Description of the Flow

Creating a new file in a designated OneDrive for Business folder triggers the Flow.

The new file is uploaded to AdobeSign and a document ID is created.

The file, as identified by the document ID, is used as the base for a new agreement, and that agreement is sent for signature.

After the successful creation of the agreement, a notification is sent to the user on the Microsoft Flow mobile application.

Prerequisites

Users need to establish a connection with Adobe Sign and OneDrive for Business

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name
1. Trigger OneDrive for Business When a file is created
2. Action Adobe Sign Upload a document and get a document ID
3. Action Adobe Sign Create agreement and send for signature
4. Action Adobe Sign Send me a mobile notification
  1. Step 1 - Trigger: When a file is created in OneDrive for Business

    A specific folder must be configured in the trigger by the user. This folder is monitored for any new files.

    Upon detection of a new file, the trigger starts the flow.

     

    5_1
    Field Name Default Value Value Comments Visibility
    Folder No To be specified by the user The folder that the trigger is monitoring Basic
  2. Step 2 - Action: Upload a document and get a document ID

    Creates a document ID from the uploaded file.

    Automatically populated values pulled from the previous action:

    • File Name : The name of the document that has been uploaded
    • File Content : The file stream of the uploaded document
    5_2

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    File Name Yes Auto-filled by the output response from the "When a file is created" trigger The name of the document to be uploaded Basic
    File Content Yes Auto-filled by the output response from the "When a file is created" trigger The File stream of the document to be uploaded Basic
  3. Step 3 - Action: Create an agreement from an uploaded document and send for signature

    Using the document ID as the file, an agreement is configured to include a list of recipients, a signing order, and a signature type.

    The following output values from the previous action are auto-populated :

    • Document Id 
    • File Name - The name of file that was created; to be used as name of the agreement
    5_3

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Agreement Name Yes Auto-filled by the output response from the "When an asset is added" trigger This value is auto-filled in the template Basic
    Document Id Yes Auto-filled by the output response from the "Upload a document and get a document ID" action This value is auto-filled in the template Basic
    Signature Type Yes E-Signature Specifies the Signature Type Basic
    Recipient Email No To be specified by the user The recipient email to which the agreement is being sent for signature Basic
    Recipient Signing Order Yes
    1 Start from 1 Basic
    Recipient Role Yes APPROVER
    The role of the recipient Basic
    Message Yes

    Please review and complete this document

    An optional message to the recipients requesting their action

    Advanced
  4. Step 4 - Action: Send me a mobile notification

    After the agreement is configured and sent, notification about the successfully creation of the agreement is sent to the user

    The following output values from the previous action are auto-populated :

    • File Name
    5_4

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Text Yes

    Your agreement <FILE_NAME> has been successfully sent for signature using Adobe Sign.

    The <FILE_NAME> value is auto-filled in the template Basic

Get signatures on a new file in SharePoint

Description of the Flow

Creating a new file in a designated SharePoint folder triggers the Flow.

The new file is uploaded to AdobeSign and a document ID is created.

The file, as identified by the document ID, is used as the base for a new agreement, and that agreement is sent for signature.

After the successful creation of the agreement, a notification is sent to the user on the Microsoft Flow mobile application.

Prerequisites

Users need to establish a connection with Adobe Sign and SharePoint

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name
1. Trigger SharePoint When a file is created
2. Action Adobe Sign Upload a document and get a document ID
3. Action Adobe Sign Create agreement and send for signature
4. Action Adobe Sign Send me a mobile notification
  1. Step 1 - Trigger: When a file is created in SharePoint

    A specific folder must be configured in the trigger by the user. This folder is monitored for any new files.

    Upon detection of a new file, the trigger starts the flow.

     

    6_1
    Field Name Default Value Value Comments Visibility
    Site Address No To be specified by the user Site Address of the User's account in Share Point Basic
    Folder Id No To be specified by the user The folder that the trigger is monitoring
    Basic
  2. Step 2 - Action: Upload a document and get a document ID

    Creates a document ID from the uploaded file.

    Automatically populated values pulled from the previous action:

    • File Name : The name of the document that has been uploaded
    • File Content : The file stream of the uploaded document
    6_2

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    File Name Yes Auto-filled by the output response from the "When a file is created" trigger The name of the document to be uploaded Basic
    File Content Yes Auto-filled by the output response from the "When a file is created" trigger The File stream of the document to be uploaded Basic
  3. Step 3 - Action: Upload a document and get a document ID

    Creates a document ID from the uploaded file.

    Automatically populated values pulled from the previous action:

    • File Name : The name of the document that has been uploaded
    • File Content : The file stream of the uploaded document
    6_3

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Agreement Name Yes Auto-filled by the output response from the "When an asset is added" trigger This value is auto-filled in the template Basic
    Document Id Yes Auto-filled by the output response from the "Upload a document and get a document ID" action This value is auto-filled in the template Basic
    Signature Type Yes E-Signature Specifies the Signature Type Basic
    Recipient Email No To be specified by the user The recipient email to which the agreement is being sent for signature Basic
    Recipient Signing Order Yes
    1 Start from 1 Basic
    Recipient Role Yes SIGNER The role of the recipient Basic
    Message Yes

    Please review and complete this document

    An optional message to the recipients requesting their action

    Advanced
  4. Step 4 - Action: Send me a mobile notification

    After the agreement is configured and sent, notification about the successfully creation of the agreement is sent to the user

    The following output values from the previous action are auto-populated :

    • File Name
    6_4

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility
    Text Yes Your agreement <FILE_NAME> has been successfully sent for signature using Adobe Sign. The <FILE_NAME> value is auto-filled in the template Basic

Get signatures for a new SharePoint item using Adobe Sign Library

Description of the Flow

When a new item is added to a SharePoint list, an agreement is created and sent, using a Library Template.

Prerequisites

Users need to establish a connection with Adobe Sign and SharePoint.

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name
1. Trigger SharePoint When a new item is created
2. Action Adobe Sign Create an agreement from a library template and send for signature
  1. Step 1 - Trigger: When a new item is created

    Whenever a new item is created under a user specified list in a particular site, then this workflow is triggered.

    When the template is created, you need to specify the Site Address and the List Name upon which this trigger will act.

    All the site addresses and the corresponding List Names that are available in the your SharePoint account will be listed for you to choose from. 

    7_1
    Field Name Default Value Value Comments
    Site Address No To be specified by the user Site Address of the user's account in Share Point
    List Name No To be specified by the user The folder on the event is to be triggered

    Note:

    This template makes the assumption that there exist a Library Template with form fields in user's Adobe Sign library whose values are intended to be filled with the output values of the "When a new item is created" trigger.

  2. Step 2 - Action: Create an agreement from a library template and send for signature

     

    Creates a document ID from the identified library template.

    Automatically populates fields on the library template with values pulled from the SharePoint list.

    Sends the document for signature to the identified recipient.

    7_2

     

    Required fields for this action:

    Field Name

    Default Value

    Value

    Comments

    Agreement Name No To be specified by the user The Name of the agreement
    Document Library Template No To be specified by the user The Library template which will be used to create agreements
    Signature Type Yes E-Signature

    The type of signature you would like to request - E-signature or Written

    Recipient Email No To be specified by the user

    Email of the recipient

    Recipient Signing Order Yes 1 It should start from 1
    Recipient Role Yes SIGNER The role of the recipient
    Message Yes

    Please review and complete this document

    An optional message to the recipients requesting their action

Get signatures for a selected SharePoint item using Adobe Sign Library

Description of the Flow

Use data from the selected item in your SharePoint list, to send an agreement for signatures using Adobe Sign.

To run this flow, select an item and choose this flow from the Flow menu.

Prerequisites

Users need to establish a connection with Adobe Sign and SharePoint

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name

1.

Trigger

SharePoint

For a selected item

2.

Action

SharePoint

Get item

3.

Action

Adobe Sign

Create an agreement from a library template and send for signature

  1. Step 1 - Trigger: When a list item is created in SharePoint

    A specific list must be configured in the trigger by the user. This list is monitored for any new items.

    Upon detection of a new item, the trigger starts the flow.

    sp3-1_sharepoint-trigger-foraselecteditem

    Field Name

    Default Value

    Value

    Comments

    Site Address

    No

    To be specified by the user

    Site Address of the User's account in Share Point . But will come auto filled when created from within sharepoint

    List Name

    No

    To be specified by the user

    The list which is selected. But will come auto filled when created from within sharepoint

  2. Step 2 - Action: 

     

    sp3-2_sharepoint-action-getitem

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Site Address

    No

    To be specified by the user

    Site Address of the User's account in Share Point. But will come auto filled when created from within sharepoint

    Basic

    List Name

    No

    To be specified by the user

    The list which is selected. But will come auto filled when created from within sharepoint

    Basic

    Id

    Yes

    The value will be auto-filled using the output of “For a selected item” trigger of sharepoint

    The ID of the row in the List.

    Basic
  3. Step 3 - Action: Create an agreement from a library template and send for signature

     

     

    sp3-adobe_sign_-action-createagreementfromlibraryandsendforsigna

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Agreement Name

    No

    To be specified by the user

    The Name of the agreement

    Basic

    Document Library Template

    No

    To be specified by the user

    The Library template which will be used to create agreements

    Basic

    Signature Type

    Yes

    E-Signature

    The type of signature you would like to request - E-signature or Written

    Basic

    Recipient Email

    No

    To be specified by the user

    Email of the recipient

    Basic

    Recipient Signing Order

    Yes

    1

    It should start from 1

    Basic

    Recipient Role

    Yes

    SIGNER

    The role of the recipient

    Basic

    Message

    Yes

    Please review and complete this document.

    An optional message to the recipients requesting their action

    Basic

Get signatures on a selected file in SharePoint

Description of the Flow

Get signatures on a selected file in SharePoint document library using Adobe Sign. To run this flow, select an item and choose this flow from the Flow menu.

Prerequisites

Users need to establish a connection with Adobe Sign and SharePoint

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name

1.

Trigger

SharePoint

For a selected item

2.

Action

SharePoint

Get item

3.

Action

SharePoint

Get file content

4.

Action

Adobe Sign

Upload a document and get a document ID

5.

Action

Adobe Sign

Create an agreement from an uploaded document and send for signature

6.

Action

Notification

Send me a mobile notification

  1. Step 1 - Trigger: For a selected file

     

    sp4-1_sharepoint-trigger-foraselecteditem

    Field Name

    Default Value

    Value

    Comments

    Site Address

    No

    To be specified by the user

    Site Address of the User's account in Share Point . But will come auto filled when created from within sharepoint

    List Name

    No

    To be specified by the user

    The list which is selected. But will come auto filled when created from within sharepoint

  2. Step 2 - Action: Get item

     

    sp4-2_sharepoint-action-getitem

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Site Address

    No

    To be specified by the user

    Site Address of the User's account in Share Point. But will come auto filled when created from within sharepoint

    Basic

    List Name

    No

    To be specified by the user

    The Library Name which is selected. Will come auto filled when created from within sharepoint referring to that particular sharepoint library.

    Basic

    Id

    Yes

    The value will be auto-filled using the output of “For a selected item” trigger of sharepoint

    The ID of the row in the List.

    Basic
  3. Step 3 - Action: Get file content

     

     

    sp4-3_sharepoint-action-getfilecontent

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Site Address

    No

    To be specified by the user

    Site Address of the User's account in Share Point. But will come auto filled when created from within sharepoint

    Basic

    File Identifier

    Yes

    The value will be auto-filled using the output of “Get Item” trigger of sharepoint

    The unique Identifier of the file.

    Basic
  4. Step 4 - Action: Upload a document and get a document ID

    Creates a document ID from the uploaded file.

    Automatically populated values pulled from the previous action:

    • File Name : The name of the document that has been uploaded
    • File Content : The file stream of the uploaded document

     

    sp4-4_adobe_sign-action-uploadadocandgetdocid

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    File Name

    Yes

    Will come auto-filled by the output response of “Get Item” action

    The name of the document to be uploaded

    Basic

    File Content

    Yes

    Will come auto-filled by the output response of “Get Item” action

    The File stream of the document to be uploaded

    Basic
  5. Step 5 - Action: Create an agreement from an uploaded document and send for signature

    Using the document ID as the file, an agreement is configured to include a list of recipients, a signing order, and a signature type.

    The following output values from the previous action are auto-populated :

    • Document Id 
    • Agreement Name - The name of the file that was created; to be used as name of the agreement

     

    sp4-5_adobe_sign-action-createagreementfromuploadeddocandsendfor

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Agreement Name

    Yes

    Will come auto-filled by the output response of “Get Item” action of sharepoint.

    The Name of the agreement.

    Basic

    Document ID

    Yes

    Will come auto-filled by the output response of "Upload a transient document and get a document ID".(Document ID)

    This value will be auto-filled in the template

    Basic

    Signature Type

    Yes

    E-Signature

    The type of signature you would like to request - E-signature or Written

    Basic

    Recipient Email

    No

    To be specified by the user while creating flow

    Email of the recipient

    Basic

    Recipient Signing Order

    Yes

    1

    It should start from 1

    Basic

    Recipient Role

    Yes

    Signer

    The role of the recipient

    Basic

    Message

    Yes

    Please review and complete this document.

    An optional message to the recipients requesting their action



    Basic
  6. Step 6 - Action: Send me a mobile notification

    After the agreement is configured and sent, notification about the successfully creation of the agreement is sent to the user

    The following output values from the previous action are auto-populated :

    • File Name

     

    sp4-6_notifications-action-sendmobilenotification

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Text

    Yes

    Your agreement <FILE_NAME> has been successfully sent for signature using Adobe Sign.

    **Note : The <File_Name> Will come auto-filled by the output response of “Get item” of sharepoint.

    The value will be auto-filled in the template

    Basic

Get signatures for a selected SharePoint item

Description of the Flow

Use this flow to request signature for a selected item using Adobe Sign. Upload the document and use the data of the selected item to send an agreement. 

To run this flow, select an item and choose this flow from the Flow menu.

Prerequisites

Users need to establish a connection with Adobe Sign and SharePoint

A connection for each service can be establish by successfully logging in to that service in the Flow.

Elements of the Flow

Building blocks of the Flow

Step Type Connector Operation Name

1.

Trigger

SharePoint

For a selected item

2.

Action

SharePoint

Get item

3.

Action

Adobe Sign

Upload a document and get a document ID

4.

Action

Adobe Sign

Create an agreement from an uploaded document and send for signature

5.

Action

Notification

Send me a mobile notification

  1. Step 1 - Trigger: For a selected item

     

    sp5-1_sharepoint-trigger-foraselecteditemplusfilecontent

    Field Name

    Default Value

    Value

    Comments

    Site Address

    No

    To be specified by the user

    Site Address of the User's account in Share Point . But will come auto filled when created from within sharepoint

    List Name

    No

    To be specified by the user

    The list which is selected. But will come auto filled when created from within sharepoint

    File Content

    NA Description: Please select a document

    -NA-

    Input parameter of Type FILE

    File Name

    NA Description:

    Please enter the file name with extension

    -NA-

    Input parameter of Type TEXT

  2. Step 2 - Action: Get item

     

    sp5-2_sharepoint-action-getitem

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Site Address

    No

    To be specified by the user

    Site Address of the User's account in Share Point. But will come auto filled when created from within sharepoint

    Basic

    List Name

    No

    To be specified by the user

    The list which is selected. But will come auto filled when created from within sharepoint

    Basic

    Id

    Yes

    The value will be auto-filled using the output of “For a selected item” trigger of sharepoint

    The ID of the row in the List.

    Basic
  3. Step 3 - Action: Upload a document and get a document ID

     

     

    sp5-3_adobe_sign-action-uploadadocandgetdocid

     

    Required fields for this action:

      Field Name Default Value Value Comments Visibility

    1.

    File Name

    Yes

    Will come auto-filled by the output response of "For a selected Item" trigger of Sharepoint. The name of the document to be uploaded Basic

    2.

    File Content

    Yes

    Will come auto-filled by the output response of "For a selected Item " trigger of Sharepoint. The File stream of the document to be uploaded Basic
  4. Step 4 - Action: Create an agreement from an uploaded document and send for signature

     

     

    sp5-4_adobe_sign-action-createagreementfromuploadeddocandsendfor

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Agreement Name

    Yes

    Will come auto-filled by the output response of "For a selected Item " trigger of Sharepoint. (File Name)

    Kindly note Not of “Get Item”

    The Name of the agreement.

    Basic

    Document ID

    Yes

    Will come auto-filled by the output response of "Upload a transient document and get a document ID".(Document ID)

    This value will be auto-filled in the template

    Basic

    Signature Type

    Yes

    E-Signature

    The type of signature you would like to request - E-signature or Written

    Basic

    Recipient Email

    No

    To be specified by the user while creating flow

    Email of the recipient

    Basic

    Recipient Signing Order

    Yes

    1

    It should start from 1

    Basic

    Recipient Role

    Yes

    Signer

    The role of the recipient

    Basic

    Message

    Yes

    Please review and complete this document.

    An optional message to the recipients requesting their action



    Basic
  5. Step 5 - Action:  Send me a mobile notification

    After the agreement is configured and sent, notification about the successfully creation of the agreement is sent to the user

    The following output values from the previous action are auto-populated :

    • File Name

     

     

    sp5-5_notifications-action-sendmobilenotification

     

    Required fields for this action:

    Field Name Default Value Value Comments Visibility

    Text

    Yes

    Your agreement <FILE_NAME> has been successfully sent for signature using Adobe Sign.

    **Note : The <File_Name> Will come auto-filled by the output response of “For a selected item” of sharepoint.

    The value will be auto-filled in the template

    Basic

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy