HubSpot data in Zendesk

Show HubSpot customer data inside your Zendesk tickets, queried live on every ticket open. No middleware, no sync lag, no code.

HubSpot is where sales, marketing, and CS keep the full picture of a customer — contact properties, company attributes, deals, lifecycle stage, revenue, last activity. Zendesk doesn't know about any of that by default, so support agents end up alt-tabbing to HubSpot, searching by email, opening the contact, scrolling through deals and custom properties, and pasting the answer back. On a busy shift that adds up to hours.

FactBranch fixes that by pulling the matching HubSpot records live every time a Zendesk ticket is opened, and rendering them as a panel inside the ticket sidebar. The agent sees the HubSpot context they need without leaving Zendesk.

How it works

FactBranch is a visual pipeline builder, not a sync tool. There's no copy of your HubSpot data stored on our end, no sync schedule to tune. The Zendesk app passes the ticket context (requester email, ticket ID, organization, and anything else you want) to FactBranch. FactBranch calls HubSpot's API using the ticket context to find the matching contact, company, and any related records. The results are rendered into an HTML panel you design, and shown inside the Zendesk sidebar.

Each step is a node in the visual editor. You pick the HubSpot objects you want to surface, choose the properties, and design one HTML template. Everything else — the Zendesk integration, the OAuth handshake, the token refresh, the rendering — FactBranch handles.

Connecting to HubSpot

You connect HubSpot via OAuth. FactBranch requests read-only access to the scopes you need — usually contacts, companies, and deals — and stores the resulting tokens encrypted. You can revoke access from HubSpot's settings at any time.

Because OAuth scopes are granular, you can limit FactBranch to only what Zendesk agents actually need. Most support use cases only need read access to contact and company properties; deal data is optional if your team references deals during support.

Picking the data

In the editor, you pick which HubSpot objects to fetch and which properties to include. The most common setup is:

• The contact matching the ticket's requester email — lifecycle stage, customer segment, account manager, last active date, any custom properties your team tracks.
• The company the contact belongs to — subscription plan, MRR or ARR, renewal date, industry, whatever's relevant.
• Any deals associated with the contact or company — current stage, amount, close date.

You can also chain HubSpot calls if the data you need isn't on a single object: look up the contact first, then fetch the associated deals, then roll everything up into the display.

Designing the sidebar UI

Once HubSpot returns the records, FactBranch pipes them into a display node where you design the Zendesk panel. There's a "Generate a UI" button that produces a working HTML template from the shape of your data — a sensible starting point you can then edit. You can tweak the template directly, add conditionals for empty fields (not every ticket's requester will be in HubSpot yet), style it with CSS, and loop through deals. The templating language is Jinja2-compatible.

Keeping it safe

Your HubSpot data stays in HubSpot. FactBranch authenticates via OAuth and only reads the scopes you've authorised. Tokens are stored encrypted. We don't cache HubSpot responses by default, so every ticket gets a fresh read — there's no stale data, and no long-lived copies of your CRM in our systems.

Because FactBranch queries HubSpot directly, it also respects any permissions set in HubSpot. If you want stricter isolation, create a dedicated HubSpot user for the OAuth connection with read access only to the pipelines you want to expose.

Setup

Most teams are live in about 10 minutes. Create a free FactBranch account, connect HubSpot via OAuth, pick the contact and company properties you want to surface (and deals if relevant), and design the panel in the display node. The final step is installing the FactBranch app from the Zendesk marketplace and pasting in your API key — agents see the HubSpot panel on the next ticket they open.

See the full walkthrough in our HubSpot documentation or watch a support agent use the sidebar in practice.