Shared data

HubSpot data flow

A narrow, company-record-only data flow. HubSpot sends the fields needed to identify the company; Company Data Guys writes a single property back to the same record.

Setup guide Scope matrix

Object scope: Company records only
Direction: Bidirectional, per record
Trigger: Manual app-card refresh
Writeback fields: 1 today

§ 01

Data flow at a glance

Every field that crosses the integration boundary, in one diagram.

Source

HubSpot

Company record

Fields read by the app card

Company ID
Company name
Domain
LinkedIn URL / handle
Property metadata

reads

writes

reads

writes

Destination

Company Data Guys

Enrichment service

Property written back to the company

LinkedIn employee count

§ 02

Directional summary

HubSpot to Company Data Guys

What we read from the company record

We use the company record fields needed to resolve the right company profile. The app prefers domain or company name and uses an existing LinkedIn company URL on the record directly when one is present. Only the company object is read; never contacts, deals, tickets, or marketing data.

Company ID
Company name
Domain
LinkedIn URL / handle
Property metadata

Company Data Guys to HubSpot

What we write back to the company record

The app currently writes one dedicated Company Data Guys property on the same company record. HubSpot's default employee count field is never overwritten. Broader company-data fields are available through the Company Data Guys API and may be added as HubSpot writebacks in later versions.

Property

company_data_guys_linkedin_employee_count

Labeled LinkedIn employee count.

§ 03

Field-by-field reference

Company ID: Identifies the exact HubSpot company record being enriched from the app card.
Company name: Used to resolve the correct company profile when no LinkedIn URL is supplied.
Domain: Primary identifier for resolving the right company profile.
LinkedIn URL / handle: Used directly when the record already has one (for example https://www.linkedin.com/company/apple/). Otherwise the app resolves the right profile from the domain or company name.
Property metadata: Read on company property schema so the app can create the writeback property if missing.
LinkedIn employee count (writeback): Written to the dedicated property company_data_guys_linkedin_employee_count on the same company record.

§ 04

Data not requested

Out of scope for this HubSpot app

The app does not request or process the following HubSpot objects or scopes. The scope matrix shows the full list of requested scopes.

Contacts

Deals

Tickets

Forms

Marketing email

Lists

Workflows

Content / CMS

Sensitive data scopes

§ 05

Operational guarantees

No silent layout changes

The app does not alter CRM layouts during OAuth install. Admins add the Company Data Guys card from the Card library.

No background syncs

Enrichment runs only when an admin opens the card and presses Pull latest company info.

Broader company data

Other company-data fields are available today through the Company Data Guys API in the dashboard. Additional HubSpot writebacks may land under the same Company Data Guys property prefix.