This feature is available on SafeBase Advanced & Enterprise plans.
Features
Sync SafeBase activities as Notes for Contacts and Companies
Auto approve based on Account Status
NDA override based on Account Status
Topics covered in this article:
Connecting to HubSpot
To connect to HubSpot, admins can find the Connect button on the Settings page.
Note: If you are presented with a modal that asks for a Developer Key, you may ignore it. This integration does not require a Developer API Key at this time.
You will be prompted to establish a new connection.
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. If you are not already signed into HubSpot, click Sign into your HubSpot account. Use credentials for a user with the appropriate permissions to proceed. You may be presented with either of the below login screens, depending on your prior HubSpot login experience.
After logging in, you will be asked to approve the connection.
Required permissions
If your HubSpot environment is non-enterprise, the integration user for this connection will require super-admin permissions.
If your 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 that will not be leveraging Custom Rules, the integration account will need access to the following fields:
Contact
Read access to:
EmailPrimary Company idOwner idContact id
Write access to:
Notes(if Seeing Activities in HubSpot feature is to be used)
Company
Read access to:
NameOwner idCompany idPrimary domainAdditional domains
Write access to:
Notes(if Seeing Activities in HubSpot feature is to be used)
Owner
Read access to:
Owner idArchivedUser 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, you will see a HubSpot connected message.
Click Next, you will be asked for the Events that you wish to sync to Contacts and Companies.
Note: These events will only be written as Notes a 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. If you wish to make changes afterward, simply click on the gear icon to the far right of the HubSpot connection row.
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 you chose to sync will now appear as Notes for Contacts in the Activities tab.
Note view for Contact
Note view for Company
Auto Approve Using Custom Rules
We 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 your CSM for more information.
Here are some use cases that we have configured for customers:
Auto-approve: Companies with an ARR above a certain monetary amount
Auto-approve: Anyone other than Companies marked as "Competitor"
Auto-approve: Companies with an NDA signed date within the past year
Override NDA: Customers with a Type of "Customer" and require NDAs for others
Override NDA: Only if the NDA was signed in the last 6 months
For more details on what is possible using the Rules Engine, please see this article.
Troubleshooting
If you do not see any notes being created, verify that the connection user has permission to read Contacts/Companies and create notes.
If auto-approving is failing, try running some tests using email domains other than Gmail or your company's domain. Development 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. If needed, you may coordinate testing with us, as we have several email distinct testing domains that can be used:
For example, you can create test Contacts using the following emails: