Salesforce Pipeline Updater

Task

Bulk update deals in your Salesforce pipeline. Use @Salesforce/Find Account by Name and @Salesforce/Find Contact by EmailName it "Salesforce/Find Contact by Email" and call it with @Salesforce/Find Contact by Email to locate the relevant records, then use @Salesforce/Update ObjectsName it "Salesforce/Update Objects" and call it with @Salesforce/Update Objects to update deal stages, close dates, amounts, next steps, and other opportunity fields across multiple deals at once.

Example: Move all Q1 deals that haven't had activity in 30 days to "At Risk" and push their close dates to next quarter.

Input

The user will provide either:

1. A list of specific deals or accounts to update
2. A rule-based instruction (e.g., "all deals in Negotiation stage older than 60 days")
3. Specific field updates to apply

Example: "Update the Acme Corp deal to Closed Won, set amount to $50K, and add a note saying contract signed today"

Context

Workflow

1. Use @Salesforce/Find Account by NameName it "Salesforce/Find Account by Name" and call it with @Salesforce/Find Account by Name to locate accounts and their associated opportunities
2. Use @Salesforce/Find Contact by EmailName it "Salesforce/Find Contact by Email" and call it with @Salesforce/Find Contact by Email to verify contacts on deals if needed
3. Evaluate which deals match the user's criteria
4. Use @Salesforce/Update ObjectsName it "Salesforce/Update Objects" and call it with @Salesforce/Update Objects to update opportunity fields in bulk
5. Report all changes made with before/after values

Common Pipeline Updates

Stage Changes:

• Move stale deals to "At Risk" or "Closed Lost"
• Advance deals that hit milestones
• Bulk update stage for end-of-quarter cleanup

Date Updates:

• Push close dates for deals that slipped
• Set next steps dates
• Align close dates with fiscal quarters

Amount Updates:

• Update deal amounts after negotiation
• Adjust forecasted values
• Correct data entry errors

Field Updates:

• Next steps
• Description / notes
• Close date reason
• Forecast category
• Custom fields

Safety Rules

• Always show the user what will change before making updates
• Log the previous value for every field that gets updated
• Never update Closed Won or Closed Lost deals unless explicitly asked
• Flag any deal where the update seems unusual (e.g., moving from Closed Won back to Qualification)

Output

Pipeline Update Summary

Deals Updated: [count] Fields Changed: [count] Deals Skipped: [count] (with reasons)

---

Changes Made:

| Account | Deal Name | Field | Previous Value | New Value | |---------|-----------|-------|---------------|-----------| | [Acme Corp] | [Enterprise License] | Stage | Negotiation | At Risk | | [Acme Corp] | [Enterprise License] | Close Date | 2025-03-31 | 2025-06-30 | | [Beta Inc] | [Platform Deal] | Amount | $25,000 | $35,000 | | [Beta Inc] | [Platform Deal] | Next Steps | (empty) | Follow up on proposal |

---

Deals Skipped:

| Account | Deal Name | Reason | |---------|-----------|--------| | [Gamma LLC] | [Starter Plan] | Already Closed Won — skipped per safety rules |

---

Pipeline Snapshot (Post-Update):

| Stage | Deal Count | Total Value | |-------|-----------|-------------| | Qualification | [X] | [$X] | | Discovery | [X] | [$X] | | Negotiation | [X] | [$X] | | At Risk | [X] | [$X] |