Introducing the HubSpot Materialization Connector

Send data back to HubSpot with enriched insights

Estuary has allowed capturing data from HubSpot for a while now, including support for custom objects, data sync intervals, and calculated properties. But oftentimes, you’ll want to send data back into your CRM as well, automating enrichment and ensuring your CRM has all the latest information about your contacts from across your systems.

Estuary has therefore released a HubSpot materialization connector to write data back to your CRM objects. Use it with millisecond-latency sources and in-flight transformations for truly real-time reverse ETL workflows.

How the HubSpot Materialization Connector Works

Reverse ETL SaaS connectors are a little different from the standard materialization. HubSpot expects certain objects with certain properties, with some properties expecting only specific enum values.

You will therefore likely need to transform your data into a shape HubSpot expects in order to enrich your HubSpot objects. You can do this in a couple of different ways:

• Transform your data in a warehouse, like Snowflake. You can then use Snowflake as a source connector with HubSpot as your destination.
• Transform your data in-flight using Estuary’s derivations. Derivations can combine data from multiple collections with Python, SQL, or TypeScript and feed directly into your HubSpot materialization. This can allow for real-time updates.

Whichever route you take, you should be aware of your object type’s match property. To match up existing records with new updates, Estuary compares HubSpot records against the collection key.

Ensure this property is unique to avoid duplicate records.

Supported HubSpot Objects

The connector currently supports the following HubSpot CRM object types to materialize into:

• Calls
• Companies
• Contacts
• Deals
• Emails
• Line Items
• Meetings
• Postal Mail
• Products
• Quotes
• Tasks
• Tickets

Getting Started

To begin loading data into HubSpot, you’ll need:

1. A HubSpot account
   1. The connector accepts OAuth or service key credentials, with OAuth recommended for production tasks
2. Properties you want to populate must already exist on the HubSpot object types you want to materialize to
3. A designated match property for each object type to identify existing records

You can optionally configure settings around requests, such as limiting the number of requests Estuary’s connector will make to HubSpot’s API.

Once your materialization is published, Estuary will start streaming updates to your HubSpot objects as they occur.

📚 See more setup details in the HubSpot materialization documentation.

FAQs

How can I transform data before sending it to HubSpot?

You can either transform data within a warehouse and then capture it, or transform data in-flight with a derivation. This lets you hook into existing data transformation flows or create new ones for real-time delivery.

I want to materialize to a HubSpot object that’s not listed. What can I do?

Drop us a line to let us know what additional functionality you’d find useful!

I use a CRM other than HubSpot. When will I be able to reverse ETL into it?

We plan to ramp up development on more reverse ETL SaaS connectors, so other options will be available soon. If you have a specific system in mind for your use case, share it with us. This helps us prioritize upcoming connectors.

Estuary’s new HubSpot materialization connector lets you reverse your flow to send data back into your CRM.