Triggers
A trigger is an event that starts a flow. In Power Automate, you can use triggers to start a flow when something happens in an envelope, a recipient, or a deliverable.
For example, you can start a flow when a deliverable (the signed document) is generated, or when an email to a recipient bounces.
Filtering Triggers
You can filter triggers using topics. This allows you to limit events to only the envelopes you’re interested in. Learn more in Topics.
Most Used Triggers
SignatureAPI offers a full set of triggers to help you automate your workflows. Below are some of the most commonly used ones:
When a deliverable is generated
Most electronic signature workflows use two flows:
- A flow that creates an envelope, usually triggered by an event in another app (for example, when a new customer is added to a CRM).
- A second flow that runs when the envelope is completed. It retrieves the deliverable (the signed document) and uses it—such as storing it in a document repository or sending it to a supervisor.
For the second flow, use the When a deliverable is generated trigger. This trigger runs when the envelope is completed and the deliverable PDF is created. You can then retrieve the PDF and use it in your flow.
When a deliverable is generated
Triggered when a deliverable, such as an audit log, is successfully generated.
When a recipient is completed
The When a recipient is completed trigger runs when a recipient finishes their part of the signing process.
You can use it to start a flow that sends a notification or updates another system (such as a SharePoint list).
When a recipient is completed
Triggered when a recipient completes their part of the signing process.
All Triggers
Envelope Triggers
When an envelope is created
Triggered when an envelope is created.
When an envelope has started
Triggered when an envelope status changes from processing to in_progress, indicating it is ready to be sent to recipients.
When an envelope is completed
Triggered when an envelope status changes from in_progress to completed, indicating it has been completed by all recipients.
When an envelope is canceled
Triggered when the signing process is intentionally stopped before completion, resulting in an envelope status of canceled.
When an envelope fails
Triggered when an envelope fails, resulting in an envelope status of failed.
Recipient Triggers
When a recipient is released
Triggered when a recipient is ready to be sent a request to complete an envelope.
When a recipient is sent
Triggered when a request is sent to a recipient.
When a recipient is completed
Triggered when a recipient completes their part of the signing process.
When a recipient is replaced
Triggered when a recipient is replaced with a new one.
When a recipient is resent
Triggered when a request is resent to a recipient.
When a recipient bounces
Triggered when a request email to a recipient is undeliverable, either temporarily (soft bounce) or permanently (hard bounce).
When a recipient fails
Triggered when there is a failure related to a recipient, resulting in a recipient status of failed.
When a recipient rejects
Triggered when a recipient rejects completing (for example, signing) the envelope.
Deliverable Triggers
When a deliverable is generated
Triggered when a deliverable, such as an audit log, is successfully generated.
When a deliverable fails
Triggered when the generation of a deliverable fails, resulting in a deliverable status of failed.
Troubleshooting
Triggers
A trigger is an event that starts a flow. In Power Automate, you can use triggers to start a flow when something happens in an envelope, a recipient, or a deliverable.
For example, you can start a flow when a deliverable (the signed document) is generated, or when an email to a recipient bounces.
Filtering Triggers
You can filter triggers using topics. This allows you to limit events to only the envelopes you’re interested in. Learn more in Topics.
Most Used Triggers
SignatureAPI offers a full set of triggers to help you automate your workflows. Below are some of the most commonly used ones:
When a deliverable is generated
Most electronic signature workflows use two flows:
- A flow that creates an envelope, usually triggered by an event in another app (for example, when a new customer is added to a CRM).
- A second flow that runs when the envelope is completed. It retrieves the deliverable (the signed document) and uses it—such as storing it in a document repository or sending it to a supervisor.
For the second flow, use the When a deliverable is generated trigger. This trigger runs when the envelope is completed and the deliverable PDF is created. You can then retrieve the PDF and use it in your flow.
When a deliverable is generated
Triggered when a deliverable, such as an audit log, is successfully generated.
When a recipient is completed
The When a recipient is completed trigger runs when a recipient finishes their part of the signing process.
You can use it to start a flow that sends a notification or updates another system (such as a SharePoint list).
When a recipient is completed
Triggered when a recipient completes their part of the signing process.
All Triggers
Envelope Triggers
When an envelope is created
Triggered when an envelope is created.
When an envelope has started
Triggered when an envelope status changes from processing to in_progress, indicating it is ready to be sent to recipients.
When an envelope is completed
Triggered when an envelope status changes from in_progress to completed, indicating it has been completed by all recipients.
When an envelope is canceled
Triggered when the signing process is intentionally stopped before completion, resulting in an envelope status of canceled.
When an envelope fails
Triggered when an envelope fails, resulting in an envelope status of failed.
Recipient Triggers
When a recipient is released
Triggered when a recipient is ready to be sent a request to complete an envelope.
When a recipient is sent
Triggered when a request is sent to a recipient.
When a recipient is completed
Triggered when a recipient completes their part of the signing process.
When a recipient is replaced
Triggered when a recipient is replaced with a new one.
When a recipient is resent
Triggered when a request is resent to a recipient.
When a recipient bounces
Triggered when a request email to a recipient is undeliverable, either temporarily (soft bounce) or permanently (hard bounce).
When a recipient fails
Triggered when there is a failure related to a recipient, resulting in a recipient status of failed.
When a recipient rejects
Triggered when a recipient rejects completing (for example, signing) the envelope.
Deliverable Triggers
When a deliverable is generated
Triggered when a deliverable, such as an audit log, is successfully generated.
When a deliverable fails
Triggered when the generation of a deliverable fails, resulting in a deliverable status of failed.