> ## Documentation Index > Fetch the complete documentation index at: https://docs.thread.app/llms.txt > Use this file to discover all available pages before exploring further. # Salesforce > Trigger workflows from opportunity stage changes and pull rich CRM context into handover briefs, success plans and SOW analysis. Salesforce is the source of truth for most of your accounts. Connecting it lets Thread react the moment a deal moves — kicking off the right onboarding workflow, drafting the handover brief, and routing the right CSM — without anyone copying data between tools. Salesforce connected on the Thread connectors page ## What you can build AE → CSM handover briefs auto-drafted from opportunity context, contacts and notes. Apply the right plan based on segment, ARR or any Salesforce field. Route accounts to the right CSM by territory, ARR, vertical, or load. 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](https://stitch.thread.app/home/connectors/salesforce)**. 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. Step 1 of 3 — Install the Thread package, with an Install Package in Salesforce button and an I've installed the package confirmation button If your org blocks managed packages, contact support — we can configure the webhook via Flow Builder instead. 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. Step 2 of 3 — Connect to Salesforce, with a radio toggle between Production and Sandbox / Scratch Org and a Connect to Salesforce button 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. Step 3 of 3 — Configure and test, showing Configuration complete checked off, Test the integration step pending, and a Waiting for first webhook polling state Once Thread receives the test webhook, the wizard flips to a success state and the integration is live. Salesforce setup success screen reading You're all set with a View settings button ## 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. Workflow builder with a Salesforce trigger node selected A typical onboarding workflow: | 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 | See [Building workflows](/csm-guide/workflows/building-workflows) for the full node reference. ## 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](https://stitch.thread.app/home/connectors/salesforce) → Field mappings** | ## Tips from the field Inconsistent stages cause workflows to miss. Audit your stages before going live. Contact roles power who shows up on the handover and in the customer portal. The more detail in the opportunity, the stronger the AI-drafted handover. Validate complex workflows in a Salesforce sandbox before pointing at production. ## Troubleshooting 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. Check the workflow is **Active** (not Draft), the trigger stage matches the opportunity's stage exactly, and the managed package is installed. **[Connectors → Salesforce](https://stitch.thread.app/home/connectors/salesforce) → Test webhook** sends a synthetic event to verify delivery. 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](https://stitch.thread.app/home/connectors/salesforce) → Field mappings**. 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 Build the AE → CSM brief that Salesforce data drafts for you. The full node reference for orchestrating onboarding.