In regard to receiving a notification when a custom created document is used, it is possible if I'm understanding what you're saying. We ran into the same issue as when sending the now "Legacy Estimate" directly, there wasn't a way to enter any special notes or add to the email body wording. So we created a custom document explaining the process, added the signature line feature, and in the automations created one to trigger based on being a task when an activity is created. I believe you have to cover all the bases with the actions by choosing all the possible criteria, as well as having to create a task within JobNimbus. It's been a few years since setting it up, but prior to that JobNimbus said there wasn't a way, and didn't seem willing to look into a way to implement one. There is a way to do it, and may even be a way to incorporate it utilizing it based on the Job Type. I don't mind looking into our automation for this if sounds like what you were wanting to accomplish.

I’m requesting the ability to trigger automations or notifications when a JobNimbus document is fully signed.

Specifically, I would like to:

Notify certain users (or external emails) when a document has been completed/signed

Update job status or fields when a document is fully signed

Currently, JobNimbus logs a system-generated email with the phrase "Document fully signed" when all signers complete a document. However, this email is not treated as a “Note” for automation triggers. Since the “Activity Created” automation only supports “Note” types (and not emails), we’re unable to create a reliable automation based on document completion.

Additionally, it appears JobNimbus already sends an internal notification to one user when a document is signed, so this functionality does exist — it’s just not currently exposed through the UI or automation builder. If admins had access to configure who is notified when a document is signed, this would solve the issue without needing custom triggers or complex workarounds.

Suggested Improvements:

Allow "email" to be a valid activity type for automation triggers.

Treat system-generated emails (like “Document fully signed”) as triggerable events.

Provide UI access to customize recipients for document signature notifications.

(Ideal) Add a new automation trigger: “When document is fully signed” → perform action (notify, update status, etc.)

This is an EXTREMELY important!! I have managed to master the HTML and make our documents look great. I wanted to use automations for actions based on when a document is signed or sent (even if signature isn't needed), but since I use documents for internal items, I cannot differentiate between those documents and the triggers I need to set. Being able to categorize the TYPE of document would change the game.

These types of things make our processes run smoother

if nobody knows the change order is signed, from accounting to production, it's pointless.