Can SixDegree read custom Salesforce objects?

Yes. When your process depends on custom objects, such as a contract or subscription object, SixDegree can query them alongside the standard objects and connect them to the same account.

What Salesforce data does SixDegree read?

Accounts, contacts, opportunities, leads, and cases, including opportunity amount, stage, close date, and probability, and case status, priority, and escalation. Reports and custom objects can also be read when needed.

Does SixDegree write to Salesforce?

Connections start read-only. The integration also supports actions such as updating an opportunity or logging an activity; whether to use any of them is agreed with your team when production is scoped.

How does SixDegree match Salesforce accounts to other systems?

It resolves each account to the same customer in tools like Zendesk, Stripe, HubSpot, and Gong using shared identifiers such as domains and CRM IDs, and keeps each match visible so it can be reviewed.

Does SixDegree replace Salesforce reporting?

No. Salesforce remains the system of record and its reports still work. SixDegree adds the evidence from outside the CRM that can change a forecast, renewal, or revenue figure.

Connect Salesforce to the evidence around every deal.

Salesforce owns the opportunity. SixDegree resolves that record to the customer activity outside CRM that can change forecast, renewal, and revenue outcomes.

Book a working session See Salesforce forecast risk

What SixDegree reads from Salesforce

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 Salesforce accounts, contacts, opportunities, leads, and cases. For opportunities that means the amount, stage, close date, probability, and type; for cases, the status, priority, origin, and whether the case is escalated. Custom objects can be read by query when your process depends on them.

Salesforce stays the system of record for the opportunity. SixDegree matches each account to the same customer in your support, billing, product, and conversation tools, using shared identifiers such as domains, and keeps the match visible so it can be checked. Every value keeps the time SixDegree observed it, so you can see when a stage or amount changed.

Account

A Salesforce account representing a company or organization

Contact

A Salesforce contact representing an individual associated with an account

Opportunity

A Salesforce opportunity representing a potential deal or sale

Lead

A Salesforce lead representing a prospective customer

Case

A Salesforce case representing a customer support request

Report

A Salesforce analytics report that can be run to retrieve pre-computed aggregate data

Salesforce

Get one Salesforce record of ANY object type by ID, standard objects, and

Questions it answers with Salesforce

Which opportunities in commit this quarter have an open P1 escalation or a past-due invoice?
Which renewals in the next 90 days sit on accounts with falling product usage?
Where does the opportunity amount disagree with what Stripe actually billed?
Which escalated Salesforce cases belong to accounts with open expansion deals?

Use case: a commit deal with problems outside the CRM

A $220,000 opportunity is in commit with a close date at the end of the quarter. In Salesforce it looks clean: the stage is current and the probability is 90 percent.

SixDegree connects the account to Zendesk, Stripe, and product analytics and finds two open P1 tickets, an invoice 20 days past due, and active users down 28 percent over six weeks. The deal shows up on the forecast risk list with those three reasons and a link to each record, before the forecast call rather than after the quarter closes.

The owner reviews the evidence, confirms the escalations are real, and moves the deal to best case. The forecast changes because of a decision someone made with the facts in front of them, and Salesforce stays the record of that decision.

Salesforce integration FAQ

Can SixDegree read custom Salesforce objects?: Yes. When your process depends on custom objects, such as a contract or subscription object, SixDegree can query them alongside the standard objects and connect them to the same account.
What Salesforce data does SixDegree read?: Accounts, contacts, opportunities, leads, and cases, including opportunity amount, stage, close date, and probability, and case status, priority, and escalation. Reports and custom objects can also be read when needed.
Does SixDegree write to Salesforce?: Connections start read-only. The integration also supports actions such as updating an opportunity or logging an activity; whether to use any of them is agreed with your team when production is scoped.
How does SixDegree match Salesforce accounts to other systems?: It resolves each account to the same customer in tools like Zendesk, Stripe, HubSpot, and Gong using shared identifiers such as domains and CRM IDs, and keeps each match visible so it can be reviewed.
Does SixDegree replace Salesforce reporting?: No. Salesforce remains the system of record and its reports still work. SixDegree adds the evidence from outside the CRM that can change a forecast, renewal, or revenue figure.

Connect Salesforce with the systems around it

These connectors expose overlapping business concepts in their published contracts, giving SixDegree evidence it can resolve into the same operational picture.

Outreach