Hello all,
I am curious if it is possible to make the token select (object tokens) in a deal-based custom workflow action to include objects other than deal tokens? See below.
I assume the UI would want me to use DataOps and copy the cross-o bject data to the deal workflow. For example, I want to get First Name and Last Name of associated contact into this custom workflow action. Do I have to copy it? Or can it be available as a token directly in this same action?
@thecoolcoder wrote:
Hello all,
I am curious if it is possible to make the token select (object tokens) in a deal-based custom workflow action to include objects other than deal tokens? See below.
I assume the UI would want me to use DataOps and copy the cross-o bject data to the deal workflow. For example, I want to get First Name and Last Name of associated contact into this custom workflow action. Do I have to copy it? Or can it be available as a token directly in this same action?
In most CRM or workflow automation platforms, the tokens available within a custom workflow action typically correspond to the fields and properties directly associated with the triggering object, such as a deal or opportunity. If you need to access data from related objects, such as a contact associated with a deal, there are several approaches you might consider. Some platforms support actions or integrations (like DataOps) that allow you to fetch and manipulate data from related objects. Alternatively, you can create custom fields within the deal object to store relevant information from associated objects like contacts.
This approach ensures the data you need is accessible through standard tokens in your workflows. Advanced workflow builders may also offer options for scripting or conditional logic to dynamically include related object data directly within your workflow actions.