# Salesforce Pipeline Update

> Bulk-update Salesforce opportunities — stage, close date, amount, next-step notes — from a spreadsheet or conversation. Use when the user says "update my Salesforce pipeline", "push deal notes to SFDC", or "log these meeting outcomes".

- Skill: `composio-community/salesforce-pipeline-update` (Agent Skill)
- Install (CLI): `npx skillmds@latest add composio-community/salesforce-pipeline-update`
- Raw SKILL.md: https://api.skillmd.com/api/skills/composio-community/salesforce-pipeline-update/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: composio-community (https://skillmd.com/u/composio-community)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/composio-community/salesforce-pipeline-update

---


# Salesforce Pipeline Update

Push opportunity updates into Salesforce via Composio.

## Workflow

1. **Collect the updates.** Ask for the source: CSV, sheet, or inline list. Each row needs Opportunity ID (or name + account) + fields to change.
2. **Link Salesforce:**
   ```bash
   composio link salesforce
   ```
3. **Confirm the opportunity exists** before patching:
   ```bash
   composio execute SALESFORCE_GET_OPPORTUNITY_BY_ID -d '{ "opportunity_id": "006..." }'
   ```
   If you only have name + account, run:
   ```bash
   composio search "salesforce query opportunity by name" --toolkits salesforce
   ```
4. **Dry-run an update** first:
   ```bash
   composio execute SALESFORCE_UPDATE_OPPORTUNITY --dry-run -d '{
     "opportunity_id": "006XYZ",
     "StageName": "Proposal/Price Quote",
     "CloseDate": "2026-06-30",
     "NextStep": "Send MSA for legal review"
   }'
   ```
5. **Execute the batch** sequentially (SFDC governor limits punish bursts). Log success/failure to `./sfdc-updates.csv`.
6. **Summarize** at the end: X updated, Y failed, Z skipped; which stages moved.

## Common field patterns

- Stage progression: enforce the account's stage model (don't skip stages unless user confirms).
- Close date: never push past the end of the current quarter without a reason in NextStep.
- Amount changes > 20%: require an activity note explaining why.

## Guardrails

- Never bulk-close opportunities as Won without explicit user approval (revenue recognition risk).
- If an update fails validation rule, surface the exact rule error — do not retry blindly.
- Ask before running against more than 25 records at a time.