Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

How can we help?

{{docApp.searchError}}
{{product.name}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Properties / Create Drop Down List Property

  • Article
  • 2 minutes to read

Operation Information

This is a Hubspot integration that allows you to create a drop down list property within the contacts details section.

This is a Premium Integration.

Authentication

This operation requires authentication, the details of which can be securely stored on your instance in a KeySafe Key of type HubSpot.

To create a key of this type:

  • In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
  • Click on the + Create New Key button;
  • On the resulting Create New Key form, choose HubSpot in the Type pick list;
  • Give the HubSpot KeySafe key a Title (this is the name / identifier for the HubSpot account as you will see it when using the cloud automation node in your workflows);
  • Optionally populate the Description field;
  • Click the Create Key button to create your new key;
  • Once the Key is created, you will need to connect to the target service, and your account, in order to authorize the connector app access to the listed operations. Click the Connect button and you will be redirected to the service provider in a popup window;
  • Log in to your account, and then you will be prompted to review the options you are authorizing the Hornbill connector to be allowed to perform using the chosen account;
  • Accept the review and you will be returned to your KeySafe key.

Revoking Access

If at any point you wish to revoke access to any of the above accounts from your Hornbill instance, just hit the Revoke button in the relevant KeySafe key(s).

Warning

This will revoke the rights of any existing Cloud Automation Node in your Hornbill Workflows that are using the revoked HubSpot account, so you will need to manage these workflows accordingly.

Input Parameters

Display Name ID Type Description Required Supported Values
Property To Create name string This is the name used in the API of the property that is going to be created. It must be in lowercase with no spaces, if you do not do this it will be automatically done for you and as such the value in Hubspot may not directly represent the value you typed Yes None provided
Property Label plabel string None provided Yes None provided
Property Description desc string None provided No None provided
Property Group pgname string None provided Yes None provided
Drop Down List Options options array None provided No None provided
Form Field formfield boolean Selecting this indicates that the field will appear as an option when building a form in the HubSpot form builder. No None provided
Field Type ftype string This controls how the property appears in a form when the property is used as a form field. Yes Select, Radio, Checkbox, Boolean Check Box
Hidden hid boolean Selecting this indicates that the field will be hidden from view. No None provided

Output Parameters

Display Name ID Type Description
Propertys name for reference in further API calls pname string None provided
  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document