# Utilize tokens in Chatbot

**URL:** <https://community.hubspot.com/t/utilize-tokens-in-chatbot/36695>\
**Category:** Tickets & Conversations\
**Tags:** workflows, object, professional, conversations-inbox\
**Created:** [May 4, 2021, 8:54pm UTC](https://community.hubspot.com/t/utilize-tokens-in-chatbot/36695 "2021-05-04T20:54:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Melesa\_Gardon](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/melesa_gardon/32/7115_2.png) [@Melesa\_Gardon](https://community.hubspot.com/u/Melesa_Gardon)\
**Post date:** [May 4, 2021, 8:54pm UTC](https://community.hubspot.com/t/utilize-tokens-in-chatbot/36695/1 "2021-05-04T20:54:30Z")

</div>

Hi everyone,

It seems like there is a limited set of properties you could get via tokens. How to get data of other properties (deal properties), that are not listed there:

 ![42012i4365F4309377D552.PNG](https://d2qpr2jzcazej7.cloudfront.net/original/2X/5/531422e94352dbdd83b7748daabdfb8ee15d032d.png)

Has anyone overcome such a challenge?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [May 5, 2021, 4:06am UTC](https://community.hubspot.com/t/utilize-tokens-in-chatbot/36695/2 "2021-05-05T04:06:33Z")

</div>

Hi [@Melesa\_Gardon](https://community.hubspot.com/t5/user/viewprofilepage/user-id/187549),

This is a limitation not only in bot chatflows but also website forms. HubSpot will only associate input information with the contact object, not any other object (deal, ticket, company). (Although there is currently a recent beta for [Company properties in forms](https://community.hubspot.com/t5/HubSpot-Ideas/Company-Deal-fields-in-forms/idi-p/250710).)

The properties that you’re seeing in the dropdown are still properties associated with the contact object. They contain deal information but they’re contact properties.

The only solution that I know of is to create a clone of the property on the object where it doesn’t exist. For example, if you want to use _Deal owner_ as a personlization token in your chatflow, you would have to create a custom owner property for the contact object first, called _Deal owner_. In a deal-based workflow, you would now (re-)enroll deals when “_Deal owner_ is known”. The second and only action of the workflow would be to copy the value from the deal _Deal owner_ into the new contact _Deal owner_ property.

If you want values to sync between objects, you would have to set up a workflow for the other direction as well. Keep in mind that these copy actions in workflows always copy the value from an object to all associated objects (the _Deal owner_ would copy to all associated contacts, not just one).

Let me know if you need more details or assistance!