Ingest data from HubSpot into Databricks
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
Learn how to create a managed ingestion pipeline to ingest data from HubSpot into Databricks.
Requirements
To create an ingestion pipeline, you must meet the following requirements:
-
Your workspace must be enabled for Unity Catalog.
-
Serverless compute must be enabled for your workspace. See Serverless compute requirements.
-
If you plan to create a new connection: You must have
CREATE CONNECTIONprivileges on the metastore.If the connector supports UI-based pipeline authoring, an admin can create the connection and the pipeline at the same time by completing the steps on this page. However, if the users who create pipelines use API-based pipeline authoring or are non-admin users, an admin must first create the connection in Catalog Explorer. See Connect to managed ingestion sources.
-
If you plan to use an existing connection: You must have
USE CONNECTIONprivileges orALL PRIVILEGESon the connection object. -
You must have
USE CATALOGprivileges on the target catalog. -
You must have
USE SCHEMAandCREATE TABLEprivileges on an existing schema orCREATE SCHEMAprivileges on the target catalog.
To ingest from HubSpot, you must complete the steps in Configure OAuth for HubSpot ingestion.
Create an ingestion pipeline
- Databricks Asset Bundles
- Databricks notebook
You can deploy an ingestion pipeline using Databricks Asset Bundles. Bundles can contain YAML definitions of jobs and tasks, are managed using the Databricks CLI, and can be shared and run in different target workspaces (such as development, staging, and production). For more information, see What are Databricks Asset Bundles?.
-
Create a new bundle using the Databricks CLI:
Bashdatabricks bundle init -
Add two new resource files to the bundle:
- A pipeline definition file (
resources/hubspot_pipeline.yml). - A workflow file that controls the frequency of data ingestion (
resources/hubspot_job.yml).
- A pipeline definition file (
-
Deploy the pipeline using the Databricks CLI:
Bashdatabricks bundle deploy
To create an ingestion pipeline using a Databricks notebook:
-
Import the following notebook into your Databricks workspace:
-
Leave cells one and two as they are.
-
Modify cell three with your pipeline configuration details. See Values to modify.
-
Click Run all.
Values to modify
Value | Description |
|---|---|
| A unique name for the pipeline. |
| The name of the Unity Catalog connection that stores authentication details for HubSpot. |
| The name of the schema that contains the data you want to ingest. |
| The name of the table you want to ingest. |
| The name of the catalog you want to write to in Databricks. |
| The name of the schema you want to write to in Databricks. |
| Optional. A unique name for the table you want to write to in Databricks. If you don't provide this, the connector automatically uses the source table name. |
Pipeline definition templates
- YAML
- JSON
These are templates to use with Databricks Asset Bundles. The following is an example resources/hubspot_pipeline.yml file:
resources:
pipelines:
pipeline_hubspot:
name: <pipeline>
catalog: <destination-catalog>
target: <destination-schema>
ingestion_definition:
connection_name: <connection>
objects:
- table:
source_schema: <source-schema>
source_table: <source-table>
destination_catalog: <destination-catalog>
destination_schema: <destination-schema>
destination_table: <destination-table>
The following is an example resources/hubspot_job.yml file:
resources:
jobs:
hubspot_dab_job:
name: hubspot_dab_job
trigger:
# Run this job every day, exactly one day from the last run
# See https://docs.databricks.com/api/workspace/jobs/create#trigger
periodic:
interval: 1
unit: DAYS
email_notifications:
on_failure:
- <email-address>
tasks:
- task_key: refresh_pipeline
pipeline_task:
pipeline_id: <pipeline-id>
This is a pipeline definition template for use with Databricks notebooks.
pipeline_spec = """
{
"name": "<pipeline>",
"ingestion_definition": {
"connection_name": "<connection>",
"objects": [
{
"table": {
"source_schema": "<source-schema>",
"source_table": "<source-table>",
"destination_catalog": "<destination-catalog>",
"destination_schema": "<destination-schema>",
"destination_table": "<destination-table>"
}
}
]
}
}
"""
Common patterns
For details about advanced pipeline configurations, see Common patterns for managed ingestion pipelines.