Home Power PlatformsPower Automate Adobe Sign and Power Automate triggers

Adobe Sign and Power Automate triggers

by Mo Faheem
Adobe Sign and Power Automate triggers

Contracts and agreements can be fully automated using Adobe Sign with Power Automate. Adobe has built a Power Automate connector to integrate Adobe Sign into solutions. For more information about Adobe Sign and Power Automate triggers, read the link.

For additional information about using Adobe Sign with Power Automate.

Triggering contracts’ automation

The automation can be fired using any trigger Power Automate connectors. For example, when an email is received or when a database record is created. In the example below, an Adobe Sign agreement will be created when a Gmail email arrives.

Additional conditions can be confirgured on the Power Automate flow trigger.

Adobe Sign and Power Automate Trigger

Adobe Sign and Power Automate Connector

An overview of Adobe Sign working with Power Automate connector in a previous post. In this post, we will drill down into Adobe Sign and Power Automate triggers and actions. This post will discuss Adobe Sign with Power Automate connector’s triggers and, in a later post, will explain the Power Automate actions.

Sign in Adobe account

When adding the Adobe Sign connector to the flow, we will sign using a paid Adobe Sign account or a trial account.

Adobe Sign sign in

The logged-in account used will be the sender and the creator of the Adobe Sign agreement.

Enterprise users will require to be assigned an Adobe Sign licence by the Adobe account admin.

Sign in Adobe account

Adobe Sign and Power Automate Triggers

Adobe provides five different triggers for Adobe Sign agreements from Power Automate.

  • When a new agreement is created
  • When an agreement is sent to a participant
  • When an agreement workflow is completed successfully
  • When an event occurs
  • When the state of an agreement changes
Adobe Sign and Power Automate Triggers

Below is the list of Adobe Sign and Power Automate triggers that can included in Power Automate flow.

When a new agreement is created

This trigger will indicate when an agreement is created, regardless if it was sent or signed. Important and required information is the scope of where the agreement was created.

When a new agreement is created

Also, we can include the created agreement and the participant information, which can be used in a later flow step.

When an agreement is sent to a participant

This trigger is used when the agreement is sent after it has been created. Similar properties as the previous trigger in addition to other properties that were not available during the agreement creation.

This Adobe Sign and Power Automate trigger can include the information of the agreement document sent to be used in the following step.

When an agreement is sent to a participant
Scope

In addition to the scope options of the creation trigger, we can set the Adobe Sign and Power Automate trigger to a specific agreement.

Scope
Agreement Name/ID

Specify the agreement name of the ID number. This option is selected only if the scope is set to a specific agreement.

Agreement Name/ID

When an agreement workflow is completed successfully

This trigger will fire the process when the agreement is completely completed as signed by all parties and signers.

As the previous triggers the same properties, additional settings, including the signed agreement information, are to be used in later flow action.

When an agreement workflow is completed successfully

When an event occurs

This Adobe Sign and Power Automate trigger are several other triggers over a specific event that allow flexibility to run flows. Examples of important events are as follows.

  • When the agreement expires, deleted, cancelled, rejected, shared, delegated or modified.
  • When an agreement email is viewed or bounced.
  • When a participant completes their action
  • The resource ID is a specific ID of one of the resources. The resources can be one of the types discussed below, either agreement, Mega Sign or Widget.
When an event occurs

It is important to note that more than one event can be conditioned to fire the Power Automate flow.

Resource type

Generally, the agreement is the most common Adobe Sign resource type. Agreements are used to send the document to participants on a specific agreement between parties. Furthermore, Adobe Sign offers two more resource type document, Mega Sign and Widget.

Adobe Sign Resource type
Mega Sign

Mega Sign is one contract that can be sent to more than one recipient. Each of the recipients has his own independent contract and, once signed considered completed. Not a contract with more than one signer.

Widget

A widget is a web form that has the ability to include signature and agreement between parties. This requirement is needed by many companies that want to allow their clients to agree on web forms easily.

When the state of an agreement changes

This Adobe Sign and Power Automate trigger is listening to the state of the agreement change, As show in the snapshot.

The events are as follows.

  • When an agreement is created
  • When a participant completes the 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
When the state of an agreement changes

Related Articles

Leave a Comment