HubSpot is a developer and marketer of software products for inbound marketing and sales. It was founded by Brian Halligan and Dharmesh Shah in 2006. Its products and services aim to provide tools for social media marketing, content management, web analytics and search engine optimization.
This datasource slice collects data from a HubSpot API and writes it to S3 and Redshift.
Steps to add this slice to your installation
The steps to launch your slice are:
- Generate HubSpot API keys
- Specify the slice config
- Add the HubSpot slice
1. Generate HubSpot API keys
Before getting started please make sure to have the following information:
- Access to an active HubSpot account
You need to have admin access in your HubSpot account, you can access your API key in your integrations settings through the following steps:
- In your HubSpot account, click your account name in the top right corner, then click Integrations.
- In the left sidebar menu, navigate to Integrations > API key.
- If a key has never been generated for your account, click Generate API key.
- Once an API key has been created for your account, the key will appear here. Click Copy to copy the API key to your clipboard.
2. Specify the slice config
To get a template for the HubSpot slice configuration save the output of the
describe --input-parameters command as follows:
Necessary input parameters:
api_key- your HubSpot api key
hubspot_parameters_file file to add the api_key generated from HubSpot
3. Add the Slice
slice-nameName of your slice. A schema with your slice-name is automatically created in your warehouse
params-fileFile path to your input parameters file. Ex. hubspot_parameters_file.json
Supported load units
contacts: captures all the attributes for contacts that anchors all contacts within HubSpot
contact_lists: contact lists for a portal. contact_lists.
subscriptions: For a given portal, return a list of all subscriptions changes and subscription status subscriptions.
subscription_changes: Represents all the changes asscociated with subscriptions subscription_changes.
campaigns: For a given portal, return all campaign IDs sorted by recent activity associated with the portal. campaigns.
events: For a given portal, return a list of all the event log for events matching specified parameters events.
Output of this slice is stored in S3 and Redshift.
Data stored in AWS S3 is partitioned by date and time in the following bucket
AWS Redshift: Schema - schema name will be same as a slice-name. Tables produced by the slice are: