Hubsessed Office Hours: Unified Revenue View

Three ways to integrate

Ryan Ginsberg · Friday, October 30, 2026

Before you build a bi-directional sync between HubSpot and another system, it helps to know which of three situations you are in, and only one of them needs a real integration. This is where I finally have an actual opinion. If you just need to see a record from another system, a UI extension (a card on the HubSpot record) with a simple get or post request is a very low bar now. If you just need to ask a question and get information across a variety of accounts, MCP is the right tooling, because it can use tool calls to fetch a bunch of records and reason over the data for that query. If you are trying to do reporting in HubSpot with third-party data, you will need some level of integration, because the data doesn't exist inside of HubSpot and you can't build cross-object reporting without it. If you are scoping an integration, you get a way to sort your case before you map a single field. Which of the three are you actually trying to do? Replay clip from Hubsessed Office Hours: Unified Revenue View. Chris Carolan and I hosted as equals. Session page: https://www.hubsessed.io/office-hours/unified-revenue-view/2026-10-29