The Adobe Sign For Power Automate connector has been improved to allow for three connection types:
Actions can be executed in the name of other users from the connection owner's account (or group) when the connection owner is an Adobe Sign administrator (group or account level).
Power Automate, Power Apps, and Logic Apps flows can be shared with the created connection by adding new owners of the flow, or as a run-only sharing (with or without sharing the connection).
For more details, see User Guide.
The Adobe Sign For Power Automate connector has been improved to allow for three connection types:
Actions can be executed in the name of other users from the connection owner's account (or group) when the connection owner is an Adobe Sign administrator (group or account level).
Support had been added for array inputs (recipients, documents, and form fields) for the following actions:
Several Actions have been updated to the REST v6 API:
Post-signing redirects
A parameter for a post-signing redirect has been added to the three create and send Actions:
The Adobe Sign for Power Automate 3.0 update introduces new REST v6 Actions that are intended as replacements for existing actions of the same name.
Legacy Actions will be hidden and deprecated by January 2021.
The list of Actions being deprecated is:
v2.1.1 introduces support for customers who are on the Microsoft Government Community Cloud (GCC).
Functionality is essentially the same, with a few platform limitations as noted by Microsoft.
To meet increasing demand from customers with complicated workflows and approval processes, we increase the maximum number of recipients, form fields, and files for Adobe Sign actions:
With this launch, we introduce two new actions:
For both new actions introduced in this release, we are providing sample workflows (templates):
Adobe Sign for Microsoft Power Automate ver 2.0 introduces the Adobe Sign Triggers!
Five Adobe Sign based triggers have been added to the integration:
Microsoft Power Automate 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 Power Automate 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 workflows. Connectors must have Actions that drive what happens within the workflow. 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.
Power Automate creates an environment where any supported service can be connected to another. Use cases for the Adobe Sign connector include:
The Adobe Sign integration comes with twelve Actions. These actions can be coupled with any relevant Trigger, or added to other workflows as part of a larger process:
Eleven templates are provided by Adobe Sign with this first release, giving a broad sample of some of the workflows that can be produced using the Actions described above:
Sign in to your account