❕ PLEASE NOTE: The HubSpot connector's version "3" is the only one that currently supports some o the operations performed in these examples. Therefore, if you want to use this functionality, either go back to version 3.11 or use the Raw Http Request procedure.
There are 5 types of Engagement activity in HubSpot, and the properties of each engagement type are different.
You need to select from the dropdown menu before creating an engagement
The "Engagement type" must be known before updating an engagement. This is accessible through the "Get engagement" procedure (as explained below).
Here’s how you can create Engagement
In this example, we'll build a Call engagement and associate it with a HubSpot contact that already exists.
Three sections make up the input: "Engagement information," "Metadata," and "Associations."
All engagement kinds have fields called "Engagement details." At the moment, they are the "Owner ID" and the "Timestamp" of the interaction activity.
The type-specific properties for the engagement itself are contained in the "Metadata" section.
Having picked the "Call" metadata type, we can see that the "Call" attributes include the following fields: "From number," "To number," "Duration," "Recording URL," "Body," and "Deposition."
You can associate the Engagement with a person, organization, or deal using the 'Associations' section.
By doing this, the Engagement will show up on that specific contact or company view in the HubSpot account ui.
Two things are necessary in order to upgrade an Engagement. As noted above in the Engagement section, the "Engagement ID" and "Engagement type" are required. This makes it possible to select the appropriate metadata properties.
❕ NOTE: If there are no updated metadata properties, the proper "Engagement type" (or "Metadata" type) MUST be selected. Even if you are simply changing the "Owner ID," for instance.
Make sure to reset the fields if no metadata is being updated. This will change the Empty spring to No Value.
❕ NOTE: If this is not done, it will get overwritten the data returned with empty strings instead.