Introduce hidden, fillable custom fields within contracts that can be automatically populated with dynamic merge tags through workflows. These hidden fields would act as unique identifiers, making it easier to track and search contracts via the API.

Example Use Case:

An opportunity moves to a new stage, triggering a workflow that sends a contract.

The workflow inserts a dynamic merge tag (such as the opportunity ID) into a hidden custom field in the contract.

When the contract is signed, another workflow captures the contact ID.

Using the hidden custom field, we can look up the contract and directly tie it back to the correct opportunity.

This enhancement would provide a seamless way to link contracts to specific opportunities without relying on manual tracking or external mapping.

Current Workaround:

Right now, we’re forced to use a non-public endpoint to download the full JSON of the contract, then run regex to extract the ID we need in order to upload the contract to the right opportunity. This is fragile and risky since that internal endpoint may be shut down at any time.

Adding official support for hidden contract fields would eliminate the need for this workaround and create a reliable, long-term solution.