What you can build
Customer handover
AE → CSM handover briefs auto-drafted from opportunity context, contacts and notes.
Success plans
Apply the right plan based on segment, ARR or any Salesforce field.
CSM assignment
Route accounts to the right CSM by territory, ARR, vertical, or load.
SOW analysis
Pull notes and attachments into a SOW review against your standard terms.
Connect Salesforce
The setup wizard walks through three steps in about five minutes. Start it from Connectors → Salesforce.Install the Thread package
Thread uses a managed Salesforce package to detect stage changes and emit webhooks. Click Install Package in Salesforce to open Salesforce’s package installer, accept Install for All Users, and come back to Thread.
If your org blocks managed packages, contact support — we can configure the webhook via Flow Builder instead.
Authorize Thread (OAuth)
Pick Production or Sandbox / Scratch Org — the sandbox option points OAuth at 
test.salesforce.com. Click Connect to Salesforce, sign in, and approve the OAuth scope. Thread reads opportunities, accounts, contacts, notes and attachments — never writes back unless you explicitly add a write action to a workflow.Auto-configure and test
Click Auto-Configure Salesforce. Thread sets your API key, webhook endpoint and trigger stage in your Salesforce org with no manual steps. Then change a test opportunity’s stage in Salesforce — the wizard polls and confirms the moment the first webhook lands.
Use Salesforce in a workflow
Drop a Salesforce trigger as the start node of any workflow. Every node downstream gets full opportunity context — Account, Contacts, Notes, Owner, custom fields — to power AI drafting, branching and assignment.
| Node | What it does |
|---|---|
| Salesforce trigger | Fires when an opportunity hits Closed Won |
| Branch | Splits Enterprise (≥ $100k ARR) from SMB |
| Handover brief | AI drafts the brief from SF context; AE reviews |
| Route to CSM | Round-robins or routes by territory/segment |
| Apply success plan | Instantiates milestones from a template |
What Thread sees
| Salesforce object | Default Thread field | Notes |
|---|---|---|
| Opportunity Name | Account name | Customizable |
| Amount | ARR | Auto-converted |
| Close Date | Close date | Format normalized |
| Account → Name, Website, Industry | Company details | |
| Opportunity Owner | AE email | Used for handover routing |
| Contacts (with role) | Contact list | Primary contact required for best output |
| Notes & Activities | AI context | Powers handover drafts and SOW analysis |
| Custom fields | Mappable | Add via Connectors → Salesforce → Field mappings |
Tips from the field
Standardize stage names
Inconsistent stages cause workflows to miss. Audit your stages before going live.
Set primary contacts
Contact roles power who shows up on the handover and in the customer portal.
Encourage rich AE notes
The more detail in the opportunity, the stronger the AI-drafted handover.
Test in sandbox first
Validate complex workflows in a Salesforce sandbox before pointing at production.
Troubleshooting
Can't connect
Can't connect
Confirm you have System Administrator (or delegated admin) permissions, that API access is enabled on the org, and that any IP allowlists include Thread’s egress range. If sign-in succeeds but the connect step fails, ensure your user has access to the Opportunity, Account and Contact objects.
Workflow isn't firing
Workflow isn't firing
Check the workflow is Active (not Draft), the trigger stage matches the opportunity’s stage exactly, and the managed package is installed. Connectors → Salesforce → Test webhook sends a synthetic event to verify delivery.
Missing fields in Thread
Missing fields in Thread
Field-level security in Salesforce is respected — if the connecting user doesn’t have read access to a field, Thread won’t see it. Add custom field mappings under Connectors → Salesforce → Field mappings.
Sandbox vs production
Sandbox vs production
Sandbox and production are separate connections. Token refresh detects sandbox URLs automatically (
*.sandbox.salesforce.com), so reconnecting is only required if you migrate the org type.Next steps
Customer handover
Build the AE → CSM brief that Salesforce data drafts for you.
Building workflows
The full node reference for orchestrating onboarding.