HubSpot is a widely used CRM platform that includes marketing, sales, service, operations, and website-building software to help grow your business. The DNIF HubSpot connector utilizes the CMS Content Audit API to collect, normalize, and monitor HubSpot audit logs of CMS changes in your HubSpot account. This helps you identify abnormal activity in real-time. Note that this endpoint is only available for accounts with a CMS Hub Enterprise subscription.
Pre-requisites
- Access token
Steps to derive prerequisites:
- In your HubSpot account, click the settings icon in the main navigation bar.
- In the left sidebar menu, navigate to Integrations > Private Apps.
- Click Create Private App.
- On the Basic Info tab, configure the details of your app:
- Enter your app's name.
- Hover over the placeholder logo and click the upload icon to upload a square image that will serve as the logo for your app.
- Enter a description for your app.
- Click the Scopes tab.
- Use the Find a scope search bar to search for content scope. Select the Read or Write checkbox for the content scope your private app needs to access.
- After you're done configuring your app, click Create app in the top right.
- In the dialog box, review the info about your app's access token, then click Continue creating.
- On the Access token card, click Show token to reveal your access token. Click Copy to copy the token to your clipboard.
You can then paste the access token into your connector configuration. For more information about Token creation, refer to this site.
NOTE: You must be a super admin to access private apps in your HubSpot account.
Configurations
The following are the configurations to forward HubSpot Connector logs to DNIF.
Field Name |
Description |
Connector Name |
Enter a name for the connector |
Access Token |
Enter HubSpot Access Token |
- Click Save after entering all the required details and click Test Connection, to test the configuration.
- A Connection successful message will be displayed on the screen along with the time stamp.
- If the connection is not successful an error message will be displayed. Refer Troubleshooting Connector Validations for more details on the error message.
Once the connector is configured, validate if the connector is listed under Collection Status screen with status as Active. This signifies the connector is configured successfully and data is ready to ingest.