Notes on using HubSpot

Scopes cont.

During your authentication setup you are asked to select project relevant scopes. Since the deprecation of the contacts scope, HubSpot uses more granular CRM scopes. If you have an old authentication, update your scopes by replacing contacts with the specific granular scopes you need (e.g. crm.objects.contacts.read). The following table gives a scope summary and is based on the information available within the HubSpot scopes documentation. So before going further please make sure you have only ticked the scope boxes which your account has access to and which are required for the operations you want to carry out. Remember that the scopes required will depend on the specific user / app / portal setup of your account.

Headers

Please be warned that HubSpot headers are case sensitive. If this is a problem for your use case note that this can be mitigated by using the HTTP Client instead.

Create / update

Any operations that has the term create / update in its title is essentially an **Upsert **operation. For example if we take a look at 'Batch create/update contacts':

• If a HubSpot contact does exist, the contact record is updated.
• If a HubSpot contact does not exist, a new contact record is created. All batch create / update operations work in this manner. For an example of how this works please see the Example use cases section.

Engagements

We have 5 of the main HubSpot Engagement types within out list of available operations:

• Note
• Email
• Task
• Meeting
• Call The properties related to each Engagement type is different. You will need to check out the HubSpot engagements documentation for more information on what they and the limitations associated are if you intend to use any. The individual engagement type docs are:
• Calls
• Meetings
• Notes
• Tasks As it stands you can Create / List / Update (eg. 'Create email engagement') the main 5 engagement types using the various operations available.

Create an Engagement

To Create an Engagement the Engagement type needs to be selected from the dropdown.

List & / or Update an Engagement

When Listing or Updating an Engagement the Engagement type needs to be known beforehand.

Properties with history

Operations which have the optional Properties with history input field have a maximum number of items that the operation can return per call.

• Requests made with the 'Properties with history' field return **50 **items
• Requests made without the 'Properties with history' field return **100 **items

Fallback values

HubSpot should return null values without any issue. Should you find that this is not the case then please use Fallback values to fix it.