This article walks through how to create automations that trigger notifications, tasks, or other actions based on the status of an e-signature document.
E-signature status automations allow you to respond automatically when a document is created, countersigned, completed, or expired, helping you keep processes moving without manual follow-up.
Before You Begin
- The e-signature document must be related to the card on the board where the automation is created.
- If the document is not related to the card, the e-signature status fields will not evaluate and the automation will not fire.
- Automations must be created on the same board where the e-signature document was sent from.
Creating the Automation
- Navigate to the board where your e-signature document is sent.
- Open Automations.
- Create a new automation and select Custom Condition Automation.
- Configure the conditions using the available e-signature status fields.
Available E-Signature Status Fields
When building your custom condition, you’ll have access to the following e-signature–related fields. These fields evaluate the status of the related document on the card.
Field | Description | How It’s Evaluated |
Countersigned | Indicates whether all required parties have signed the document. | True or False |
Created | The date the e-signature document was created. | Date-based conditions (before, after, on, etc.) |
Expiration | The expiration date of the e-signature document. | Date-based conditions |
Status | The current status of the e-signature document. | Matches a specific e-signature status value |
Configuring Conditions
You can select any one or multiple e-signature fields when building your automation conditions.
For each field, you can define different criteria:
Field-Specific Notes
- Countersigned
- Evaluates as True or False
- Commonly used to trigger actions once all signatures are complete
- Created
- Uses date-based logic
- Can be used to trigger actions a certain number of days after document creation
- Expiration
- Uses date-based logic
- Ideal for monitoring documents that are about to expire or have already expired
- Status
- Evaluates against specific e-signature statuses (for example, Completed, Sent, or Expired)
- Useful for branching logic based on document progress
Setting the Automation Timing
After defining your conditions, choose when the automation should run:
- Immediately when conditions are met
- A specified amount of time after the conditions are met
Timing controls when your notification, task, or update occurs once the e-signature status matches your criteria.
Choosing Automation Actions
Once timing is set, select the action you want to occur. Common actions include:
- Sending an internal or external notification
- Creating a task
- Moving the card to a new stage
- Updating a field
- Assigning the card to a user
Common Use Cases
Move a Card When a Document Is Completed
- Condition: Status is Completed
- Action: Move card to a “Completed” or “Next Steps” stage
Manage Expired E-Signature Documents
- Condition: Expiration date has passed
- Action: Create a task to follow up with signers or extend the document expiration
Notify Teams When a Document Is Countersigned
- Condition: Countersigned is True
- Action: Send an internal notification or assign the card to the next owner
Using e-signature status automations helps ensure that important document milestones never go unnoticed and that follow-up actions happen automatically at the right time.