Connect HubSpot deals to the rest of the customer story.
HubSpot remains the CRM. SixDegree connects each company and deal to the operational evidence that can confirm or challenge its forecast and renewal state.
What SixDegree reads from HubSpot
This page is generated from the connector contract in the SixDegree molecule registry. The entities below reflect the integration implementation, not a generic compatibility claim.
SixDegree reads HubSpot contacts, companies, deals, tickets, and pipelines. For deals that includes the stage, pipeline, amount, close date, and associated company; for tickets, the status, priority, category, and open and close dates. Pipeline definitions let SixDegree interpret each stage the way your team configured it.
HubSpot remains the system of record. SixDegree resolves each company to the same customer in billing, support, product, and conversation tools, keeps the source of every value, and records when it changed. If you run Service Hub, HubSpot tickets are connected to the same accounts as your deals.
Spot Contact
A contact in HubSpot CRM representing an individual person
Spot Company
A company in HubSpot CRM representing an organization or business
Spot Deal
A sales deal in HubSpot CRM representing a revenue opportunity
Spot Ticket
A service ticket in HubSpot Service Hub representing a customer support request
Spot Pipeline
A sales or service pipeline in HubSpot defining workflow stages
Questions it answers with HubSpot
- Which HubSpot deals closing this month belong to companies with open high-priority tickets?
- Which customers renewing next quarter have fewer active users than paid seats?
- Where does the deal amount in HubSpot differ from what Stripe invoiced?
- Which companies opened more tickets this month than in the previous three?
- Which open deals sit in a pipeline stage that has not changed in 30 days on accounts with new support issues?
Use case: renewal risk for a HubSpot-run company
A company runs sales and support in HubSpot and bills through Stripe. A renewal deal for a $90,000 customer sits in the expected stage with no recent changes.
SixDegree connects the company to its HubSpot tickets and Stripe invoices and finds six high-priority tickets in the last 30 days, three times the account’s usual rate, and a downgrade on the latest invoice. The renewal moves onto the at-risk list with both reasons, so the owner can act while there is still time.
The owner opens the account, sees which tickets drove the change and which invoice line went down, and books a call with the customer’s admin the same week. HubSpot stays the place the deal is managed; SixDegree supplies the evidence that it needs attention.
HubSpot integration FAQ
- Does SixDegree use HubSpot pipeline stages?
- Yes. SixDegree reads your pipeline definitions, so a deal stage means what your team configured it to mean, including separate pipelines for new business and renewals.
- What HubSpot data does SixDegree read?
- Contacts, companies, deals, tickets, and pipelines, including deal stage, amount, close date, and company, and ticket status, priority, and category.
- Does SixDegree work with HubSpot Service Hub?
- Yes. HubSpot tickets are read alongside deals and companies, so support load can be tied to the same customer and its revenue.
- Can SixDegree combine HubSpot with other support tools?
- Yes. If support runs in Zendesk instead, SixDegree resolves Zendesk organizations and requesters to the same HubSpot company.
- Does SixDegree change HubSpot records?
- Connections start read-only. The integration supports actions such as updating a deal or creating a note; whether to use any of them is agreed with your team when production is scoped.