What This Update Actually Is
HubSpot shipped a new API endpoint that gives developers a direct lane into Data Studio. It's called the Data Sources File Ingestion API.
Here's what it actually does: a developer defines a named data source through the API, then uploads one or more tabular files into that source. HubSpot stores it as a reusable external data source inside Data Studio. From there, it's available for reporting and activation, just like any native dataset.
The supported file formats are CSV, XLS, XLSX, and TSV. Files can be up to 512 MB. Column types supported include STRING, BOOL, DATETIME, DATE, INTEGER, and DECIMAL. Authentication runs through OAuth 2.0 with scoped access tokens.
Developers get four core operations: create a data source, retrieve a data source, update a data source, and delete a data source. The write scope covers both create and delete. The read scope covers retrieval. That's the whole surface area.
One important caveat: this is a developer API. If your team doesn't have a developer or someone comfortable with OAuth 2.0 and REST APIs, this feature won't be accessible to you out of the box. That's not a knock on HubSpot. It's just the honest reality of where this lives in the product.
Why HubSpot Shipped This
Here's the problem this solves. Data Studio is HubSpot's reporting and analytics layer. It's powerful. But until now, getting external tabular data into it meant mapping that data to CRM objects, contacts, deals, companies, and so on. That's a rigid constraint.
A lot of the data that teams actually need to report on doesn't fit neatly into CRM object schemas. Think financial exports, inventory tables, third-party survey results, product usage CSVs, or regional benchmark data. Forcing those into CRM objects creates technical debt and forces bad data modeling decisions.
The internal frustration for data teams has been real. Humans running RevOps or marketing analytics often know exactly what data they need in a report. But they've had to choose between a messy workaround or leaving the data outside HubSpot entirely. Neither option is good.
HubSpot's answer is schema-agnostic ingestion. Load your raw tabular data, define your column types, and make it available in Data Studio without bending your data to fit an object model it was never meant for. That's the right call.
How to Use It Step by Step
This is the developer implementation path. Each step assumes your developer has access to a Data Hub Professional or Enterprise portal and a valid OAuth 2.0 app.
- Set up OAuth 2.0 authentication. Request the correct scopes: data_integration.data_source.file.write for create, update, and delete operations, and data_integration.data_source.file.read for retrieval. Include your access token as a Bearer token in the Authorization header.
- Create a named data source via the API. This defines the container for your tabular data inside Data Studio. Give it a descriptive name that your reporting team will recognize.
- Upload your file. Supported formats are CSV, XLS, XLSX, and TSV. Maximum file size is 512 MB. Define your column data types during upload: STRING, BOOL, DATETIME, DATE, INTEGER, or DECIMAL.
- Add to or overwrite the data source as needed. You can incrementally push new files into the same named source without rebuilding the dataset from scratch. This is a key workflow advantage for recurring data updates.
- Retrieve the data source to confirm the upload and check its state. Use the read scope for this operation.
- Open Data Studio and locate the new external data source. It's now available as a reusable source for building reports, joining with other datasets, or activating across Data Studio's tools.
- Delete data sources you no longer need using the write scope. Keep your Data Studio environment clean as your reporting needs evolve.
What It Touches in Your HubSpot Strategy
This API lives at the intersection of your reporting strategy, your data architecture, and your developer capacity. It doesn't change HubSpot's CRM object model. It gives you a parallel lane that bypasses it for reporting purposes.
For RevOps teams, this changes what's possible in Data Studio dashboards. If your revenue reporting has required exporting data to a BI tool because HubSpot's CRM layer didn't hold everything you needed, this closes part of that gap. You can push financial data, product data, or operational benchmarks directly into the reporting layer without forcing them into CRM object schemas.
Key Takeaway
This API doesn't replace CRM object-based data. It adds a schema-agnostic lane alongside it. If your data fits CRM objects well, keep using CRM objects. If it doesn't, now you have a real alternative inside HubSpot instead of a workaround outside it.
For marketing ops, this opens the door to richer segmentation and reporting. If you have survey data, event attendance records, or third-party audience data in spreadsheet form, you can now bring those into Data Studio and report alongside your HubSpot marketing data.
The incremental update capability is the feature worth paying attention to. Humans running recurring data pipelines, think weekly sales ops exports or monthly financial reconciliations, can update the same named data source without tearing it down and rebuilding. That's a meaningful reduction in pipeline fragility.
This update also has implications for teams watching HubSpot's API landscape closely. If your portal has custom integrations touching HubSpot's pipeline or data layer, you're already navigating API changes. The
Pipelines API V1 deprecation happening December 4, 2026 is a good reminder that keeping your API integrations current isn't optional. The File Ingestion API is a net-new addition, but it sits in the same developer ecosystem where maintenance debt compounds fast.
If your team is also expanding what you report on inside HubSpot, pair this with better dashboard structure. A more flexible data layer is only as useful as the reports built on top of it.
HubSpot's recent dashboard grid layout update gives you more columns and more precise report placement, which matters when you're surfacing richer external datasets alongside native CRM data.
Key Takeaway
The real strategic value here is consolidation. Every dataset you can bring into HubSpot's reporting layer is one fewer tab open in a spreadsheet, one fewer manual join in a BI tool, and one fewer place where a number can drift from what's in your CRM.
Who Should Care Most
This update is built for a specific kind of portal. Here's who should act on it now.
- Data Hub Professional and Enterprise subscribers who already use Data Studio for reporting and have external datasets they've been routing around HubSpot to analyze.
- RevOps leaders who maintain recurring data pipelines from finance, product, or operations and want those datasets living inside HubSpot's reporting layer instead of a separate BI tool.
- Developers building custom HubSpot integrations who need a clean, schema-agnostic way to push tabular data into the platform without forcing it into object models it doesn't fit.
- Marketing ops professionals who work with third-party audience data, survey exports, or event attendance records and want unified reporting inside HubSpot.
- Growing companies that are consolidating their reporting stack and want HubSpot to serve as the single source of truth across more data types.
Who shouldn't prioritize this right now: teams without developer resources, portals not on Data Hub Professional or Enterprise, and organizations where CRM object-based data covers everything they need to report on.
George's Take
We've sat inside hundreds of portals where the reporting gap wasn't a HubSpot limitation, it was a data architecture limitation. Humans were keeping their most important operational data in spreadsheets and external tools because HubSpot's ingestion layer required CRM object mapping that didn't make sense for their data. This API is HubSpot acknowledging that reality and building a real solution for it. It's not a workaround. It's a proper data lane. If your team has developer capacity and you're sitting on external tabular data that belongs in your reporting layer, the barrier to getting it there just dropped significantly. My advice: don't wait for a perfect use case. Find the one recurring spreadsheet your RevOps team exports every month and start there.
“Every dataset your team keeps outside HubSpot is a decision someone has to make twice. This API is how you start ending that pattern.”
If you're not sure whether your portal is set up to take advantage of this, or if you want help scoping a data ingestion strategy that actually makes sense for your business, let's talk. Book a strategy call with the Sidekick team and we'll walk through your Data Studio setup, your current data gaps, and the fastest path to unified reporting inside HubSpot.
Frequently Asked Questions
What file formats does the HubSpot Data Sources File Ingestion API support?
The API supports CSV, XLS, XLSX, and TSV files. File size is capped at 512 MB per upload. Column types can be defined as STRING, BOOL, DATETIME, DATE, INTEGER, or DECIMAL, giving developers control over how the data is typed and stored inside Data Studio.
Do I need to map my data to HubSpot CRM objects to use the File Ingestion API?
No. That's the key difference with this API. It uses schema-agnostic ingestion, meaning your tabular data doesn't need to conform to HubSpot CRM object models like contacts or deals. You define your own column structure and upload it directly into Data Studio as an external data source.
Which HubSpot plans include the Data Sources File Ingestion API?
The File Ingestion API is available on Data Hub Professional and Data Hub Enterprise. It's not available on free, Starter, or any non-Data Hub subscription. If you're unsure whether your current plan includes Data Hub, check your subscription details in HubSpot's account settings.
Can I update an existing data source without deleting and recreating it?
Yes. The API supports incremental updates. You can upload additional files into an existing named data source or overwrite it without rebuilding the dataset from scratch. This makes it practical for recurring data pipelines like weekly exports or monthly financial reconciliations.
What OAuth scopes are required to use the File Ingestion API?
You need two scopes. Use data_integration.data_source.file.write for create, update, and delete operations. Use data_integration.data_source.file.read for retrieval. Both must be requested through your OAuth 2.0 app and included as a Bearer token in the Authorization header of each API call.
How does the File Ingestion API relate to HubSpot's existing reporting tools?
Once uploaded, your file becomes a reusable external data source inside HubSpot Data Studio. You can use it to build reports, join it with other datasets, and activate it across Data Studio's reporting tools. It sits alongside native CRM data rather than replacing it.
