This feature is available on SafeBase Advanced & Enterprise plans.
Overview
The Trust Center's Hubspot integration enables organizations to sync Trust Center activities as Notes for Contacts and Companies and auto-approve Trust Center access requests/ override NDA requirements, based on Account or Contact information held within Hubspot.
Connecting to HubSpot
To connect to HubSpot, navigate to the Integrations tab of the Settings page, and click the Connect button next to the Hubspot integration.
A pop-up will appear asking to establish a new connection.
Note: If you are presented with a modal that asks for a Developer Key, ignore it. This integration does not require a Developer API Key at this time.
Note: Our integration only supports a single connection. If you are finished with testing in your sandbox, please remove it before connecting to production.
Click Create.
The integration will piggyback off of the current Hubspot connection sessoin
If signed into HubSpot, it will automatically attempt to establish the connection
If not, click Sign into your HubSpot account.
Use credentials for a user with the appropriate permissions to proceed.
Depending on any prior HubSpot login experience, users maybe be presented with either of the following login screens
After logging in, approve the connection.
Permissions
Note: If the HubSpot environment is non-enterprise, the integration user for this connection will require super-admin permissions.
If the HubSpot environment is enterprise, the integration does not require super-admin permissions, as it will have access to the required API scopes.
For standard integrations, the integration user needs access to the following fields:
Contact
Read
Email
Primary Company id
Owner id
Contact id
Write
Notes (if Seeing Activities in HubSpot feature is to be used)
Company
Read
Name
Owner id
Company id
Primary domain
Additional domain
Write
Notes (if Seeing Activities in HubSpot feature is to be used)
Owner
Read
Owner id
Archived
User id
Note: If using Custom Fields, the integration will need Read access to those fields.
When connecting, you will see an OAuth modal asking you to allow our middleware service. Tray.ai to access your HubSpot instance.
If the connection was successful, a HubSpot connected message will display
Click Next,
Optional: View and configure event settings in the integration window
Note: These events will only be written as Notes on the Company if the Contact is linked to a Company. If a Contact is not linked to a company, there will only be a Note written to the Contact.
Click Finish to complete the setup.
To make changes afterward, navigate back to the integration configuration page
Check Permissions Tool
The check permissions tool is located on the right corner of the HubSpot integration UI.
Click the kebab menu next to the gear icon.
Click Check Permissions.
The permissions checker will show all currently used fields for the integration and a status.
The status indicates if the HubSpot user used to connect the integration has the correct access to required HubSpot fields.
Activities in HubSpot
The events chosen to sync willappear as Notes for Contacts in the Activities tab.
Note view for Contact
Note view for Company
Auto Approve Using Custom Rules
The Trust Center can automatically approve access requests and override NDAs based on custom rules using both standard and custom HubSpot fields.
Note: Custom Rules are available for Enterprise plans. Please contact a Drata CSM for more information.
Examples of potential use cases for Custom Rules
Auto-approve: ARR above a certain monetary amount
Auto-approve: All companies not marked as "Competitor"
Auto-approve: Company with NDA signed date within the past year
NDA-Override: Company with Type = "Customer" + require NDAs for others
NDA-Override: If the NDA on record was signed in the last 6 months
For more details on what is possible using the Rules Engine, please see this article.
Troubleshooting
If notes are not being created, verify that the connection user has permission to read Contacts/Companies and create notes.
If auto-approving is failing, try running tests using unique email
Dev/Sandbox environments with many Company records with the same domain likely will result in conflicts in which our system is unable to determine which Company to associate the request with.