There are two key improvements needed to unlock full workflow automation for Custom Objects:
  1. Full Workflow Support for Custom Object Triggers
Custom Object triggers (Record Created / Updated) should support the entire action set, specifically:
Send Document & Contract
Webhooks
Branching logic
Communication actions
Right now these triggers are restricted, preventing CO-based automation flows from functioning end-to-end.
  1. Custom Object Record as Document Context
Document Templates should support Custom Object Records as the primary context, allowing:
Dynamic population of Custom Fields
Selecting the associated Contact automatically
Sending the generated document directly within a workflow
Even though templates allow inserting CO fields, values remain empty because the workflow cannot assign a CO record as the active context.
Impact:
Enabling these two upgrades would allow proposals, contracts, project documents, and reports to be automatically generated from Custom Object data — a major step for advanced CRM implementations.