What you can build
Workflow routing
Fire on an opportunity stage change and route the account down the right path.
Handover Briefs
AI-drafted briefs from opportunity context, contacts and notes, reviewed by the AE.
Agent context
Agents read the opportunity, stakeholder map, calls, files and activity — scoped to the account they’re working.
Milestone verification
Salesforce reads can serve as the evidence that closes a Motion milestone.
Connect Salesforce
The setup wizard walks through three steps in about five minutes. Start it from Connectors → Salesforce.1
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.
2
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.3
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.
See Building workflows for the full node reference.
What agents can read
Beyond the trigger, connected agents get read-only, account-scoped Salesforce tools: the opportunity (stage, amount, owner, line items), the account and its full stakeholder map, contact roles, logged calls and activities, files on the opportunity, and object schemas for custom fields. The agent never picks which account’s records it touches — the account in context resolves that. The only Salesforce write available to agents is an opportunity update (stage, amount, close date), and it is approval-gated like every state-changing action.What Thread sees
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
Handover Briefs
Build the AE-reviewed brief that Salesforce data drafts for you.
Building workflows
The full node reference for routing accounts.