Envelope - Sign Multiple Files

*** AVAILABLE OCTOBER 2026 *** 

Overview

The 'Envelope - Sign Multiple Files' action for Power Automate creates an envelope for a collection of files with a multiple stage approval/sign process aligned to the workspace associated to the API Key used within the Power Automate connection.

Default Options

The default 'Envelope - Sign Multiple Files' flow action parameters are detailed below:

  • Title: Set the title of the envelope
  • Message: Set a message to share with recipients
  • Sender: The email address of the 'Sender' who must be a licenced member of the workspace
  • Files: The collection of files
    • ID: A unique identifier for this uploaded file, used to map fields to the correct file
    • Filename: The filename of the file
    • File: The file (File Content) to submit for signature
  • Delivery Mode: Set whether the file should be sent to recipients sequentially or in parallel
  • Requirement Mode: Set whether one or all recipients are required to sign the document. Only applies where the 'Delivery Mode' = 'Parallel'
  • Recipients: The recipient's (signers and/or reviewers) assigned to the 'Envelope'
    • Type: Set the recipient type (Signer or Reviewer)
    • First Name: Set the recipient's first name
    • Last Name: Set the recipient's last name
    • Email Address: Set the recipient's email address
    • Order: Set the order in which this recipient will receive the document
    • Language: Set the recipients language
    • Fields: The fields contained within the document(s) which are to be completed by the recipient
      • Type: Set the field type (Signature, Text, Email, etc.)
      • Field Name: Set the name of the target field within the document
      • Placeholder Text: et the value of the placeholder text within the document to replace with the 'Field' specified
      • Default Value: Set the default value for the field
      • Required: Set whether the field is required
      • Read Only: Set whether the field is read-only 
      • File ID: The unique file identifier used to map this field to one of the uploaded files

JSON Models

Utilise the following JSON models as opposed to configuring through the Power Automate user interface:

Files

[ 
  {
    "inputFileId": "string", 
    "fileName": "string", 
    "file": FileContent 
  } 
]

Recipients

[ 
  { 
    "type": "Signer" | "Reviewer", 
    "firstName": "string", 
    "lastName": "string", 
    "emailAddress": "string", 
    "order": int, 
    "language": "Default" | "EN" | "BG" | "CS" | "DA" | "DE" | "ES" | "FR" | "IT" | "JA" | "NL" | "NO" | "PL" | "PT" | "RO" | "RU" | "SV" | "TH" | "ZH_CN" | "ZH_TW" 
    "fields": 
      [ 
        { 
          "fieldType": "Signature" | "TextBox" | "CheckBox" | "Name" | "Initials" | "DateSigned" | "Email" | "Title" | "Company" | "EditableDate" | "Image" | "Attachment", 
          "fieldName": "string", 
          "placeholderText": "string", 
          "defaultValue": "string", 
          "isRequired": boolean, 
          "isReadOnly": boolean, 
          "inputFileId": "string" 
        } 
      ] 
    } 
  ] 

Advanced Options

The advanced 'Envelope - Sign Multiple Files' flow action parameters are detailed below:

  • Expires In (Days): Set the expiration time for the envelope in days
  • Download As: Set whether the deliverable (Signed document(s) + completion certificate) is provided as a single PDF or separate files

Return Parameters

The 'Envelope - Sign Multiple Files' flow action returns the following data. 

Action Specific Return Values

  • Envelope ID: The envelopes unique identifier
  • Created: The date and time the envelope was created
  • Status: The envelope status

Standard Return Values

  • OperationId - The unique ID assigned to this operation.
  • HttpStatusCode - The HTTP Status code for the response.
  • HttpStatusMessage - The HTTP Status message for the response.
  • Errors - An array of error messages should an error occur.
  • Operation Status - Indicates whether the operation has been completed, has been queued or has failed.
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk