DeepSign Power Automate – Process

Release a document for signature

1. Action: Upload
2. Action: Start process
3. Action: Download

Upload:

First, a document must be uploaded to DeepSign and saved as a draft.

The following definitions must be entered in the “Upload Document” action:

Example JSON:

{

“companyId”:“3fa85f64-5717-4562-b3fc-2c963f66afa6”,

“initiatorAliasName”: “name xy”,

“comment”: “Please sign this document.”,

“signatureMode”: “timestamp”,

}, “jurisdiction”: “certes”,

“scanPredefined”:true,

“callbackEventTypes”:[

“document-completed”

   ],

“callbackUrl”: “https://myserver.com/my/lovely/callback”,

“visualSignatureRequirement”: “required”

}

---

• To determine the companyId, log in with your DeepCloud account via app.deepbox.swiss. The UUID after the DeepBox domain (https://app.deepbox.swiss/) corresponds to your companyId.
• The initiatorAliasName parameter corresponds to the name that is displayed as the inviter in the invitation email.
• The signatureMode can contain one of the following values:
  • “timestamp” – Simple Electronic Signature (SES)
  • “advanced” – Advanced Electronic Signature (AES)
  • “qualified” – Qualified Electronic Signature (QES)
• The jurisdiction can contain one of the following values:
  • “certes” – Federal Act on the Electronic Signature (CH based jurisdiction)
  • “eidas” – Electronic Identification, Authentication and Trust Services (EU based jurisdiction)
• If the document contains placeholders, these can be read out if the scanPredefined Boolean has been set to true.
• As soon as a registered event is triggered, a POST request is sent to the stored callbackUrl.
  The following events can be registered:
  • “signee-completed” – a signatory has signed the document or rejected the signature
  • “document-completed” – the document has been signed or rejected
• With the visualSignatureRequirement parameter, the signatory can be forced to place a visual signature.

Start signature process:

Before the signature process is started, the signatories must be defined. If this has not been done with placeholders during the upload, this must be done with separate actions. The signature process can then be initialized with the “Start Signature Process” action.

Download signed document:

Info: Additional actions from the HTTP Connector are used

If a webhook / callback URL has been registered, a process can be created in Power Automate which is triggered based on the message in a DeepSign event.

The trigger “On receipt of an HTTP request” can be stored for this purpose.

The webhook message follows this pattern:

{

“type”: “object”,

“properties”: {

“eventType”: {

“type”: “string”

        },

“documentId”: {

“type”: “string”

        },

“timestamp”: {

“type”: “string”

        }

    }

}

---

The HTTP URL, which is generated after the process is saved, must be entered as the callback URL in the DeepSign upload.

If a corresponding event is then triggered on DeepSign, this initiates the trigger.

If the document has been signed, the details of the document can be retrieved using the “Get Document Details” action. The DownloadUrl is returned in the response, which can then be called up with an HTTP request.