If a pending contract gets edited and resent for signatures again, this additional action will also activate the “Document is sent for signature” trigger in the Automation Builder.
In addition, each time a contract gets edited and resent as a result of rejection or request for changes, the “Document is sent for signature” automation trigger will be executed.
This applies to automations configured only on the Team Owner’s account but based on templates shared within the entire team as well.
If any of the members have to edit and resend a contract, the automation trigger “Document is sent for signature” will run from the configuration under the team owner’s account.
Read more about setting up centralized automations from the Team Owner’s account here.