In our backend integration, we are trying to distribute meetings between Hubspot Users.
Each user in our system has a corresponding `Contact` in HS. A user should be able to get a `Meetings Scheduler` link that leads them to the `Owner` of their `Contact`
My plan was:
1. Create a one-on-one `Meeting Scheduler` link for every Hubspot `User` who is responsible for this meeting pool (this works)
2. Create a custom property on every Hubspot `User`, store the link from (1) there (this works)
3. Retrieve this property via the API, by:
a. first querying a `Contact` by an ID, and retrieving their owner ID (this works)
b. getting the Hubspot `User` object by the aforementioned user ID (which is the same as the owner ID) (this works)
c. Getting the aforementioned custom property from the User object retrieved in (b) (this does not work)
The basic idea is to retrieve the custom `Meetings Scheduler` link of a `Owner` of a specific `Contact`, to embed it in our frontend. The contact must not have the option to meet with anyone but their owner and the slots should reflect the owners' availability for this meeting.
Unfortunately, this does not work as the Users/Owners API does not return custom properties, as I just now found out from the forum. Am I missing something? Are there better ways to implement this? Thanks
@SAfonchenko - It looks like a great logical setup, but I believe that you are mitaken in suggesting that an owner ID is the same as a user ID. My experience indicates that there are three record ID values that you need to consider for a user:
- user ID (for this instance)
- user ID (HubSpot global - confusingly called internal user ID in the documentation.
Plus of course the email address, which is pretty handly for use as an idProperty in the API of course.