Trigger: Signature deadline passed
1 min read
Fires when an open request's deadline passes without a signature. Checked every five minutes — an expiry happens because nobody acts, so somebody has to notice.
Step by step
- Create an automation and pick “Signature deadline passed”.
- Common: a call-back task, stage back, or a fresh request with a longer deadline.
- The deadline itself sits on the “Request signature” step and counts from dispatch.
Can I remind before that?
Yes, and it is the better route: “Wait” with the condition “file exists” and a three-day cap, then a branch — in the “still missing” branch, request again with “Send again” switched on.
Why branch on the field, not the status?
Because “field is empty” still holds after a re-run, and it is the only condition that also covers the paper route.
What does the link show after expiry?
That the deadline passed, and the way back. Not an empty page and not an error.
Does the recipient get a message?
Not by itself. What happens on expiry is your automation's decision — that is what this trigger is for.