Manage opportunity records

  • Release version: Australia
  • Updated June 9, 2026
  • 4 minutes to read

    • Retrieve, update, create, and delete opportunity records and related CRM data from an MCP client using plain language.

    Before you begin

    Role required: admin

    About this task

    All changes go through the same server-side business rules, validation scripts, and access controls that apply on the standard form. Every create, update, or delete action requires explicit confirmation before the agent commits.

    Procedure

    1. Connect through your MCP client.
      For information on how to connect to an MCP server from an MCP client, refer Connecting to an MCP server from an MCP client
    2. Type a natural language prompt for the operation you want to perform.
      Operation What to type
      Retrieve

      Examples by data type:

      • Pipeline: "Show me all my open opportunities" or "What's my pipeline split by stage?"
      • Opportunity detail: "I'm getting on a call with <company name> — fetch the open opportunity details."
      • Tasks — today: "What tasks do I have today including overdue?"
      • Tasks — overdue: "Show me all my overdue tasks."
      • Tasks — by opportunity: "Show me all open tasks for the <company name> opportunity."
      • Touchpoints: "Show me all touchpoints logged against <company name> in the last month."
      • Contacts: "Fetch all the stakeholders for this opportunity" or "Who are my contacts at <company name>?"
      • Competitors: "Fetch all competitors for this opportunity."
      • Opportunity lines: "Fetch the products being sold in this opportunity."
      • Accounts: "Show me all accounts I own."
      Update

      Examples by field or entity:

      • Stage: "Move the <company name> Q3 deal to Proposal/Price Quote" or "Move OPTY100001 to the next stage."
      • Forecast category: "Change the forecast category on the <company name> deal to Commit."
      • Close date: "Push the close date for <company name> to end of next month." Relative expressions such as "Q3 end" or "next Friday" are supported. Close dates can't be set in the past.
      • Deal size: "Set OPTY100001 amount to 350K." Formatted inputs such as $350,000 and 0.35M are supported.
      • Work notes: "Add a note to <company name>: 'Budget confirmed, decision in 30 days.'" Notes are appended and never overwritten.
      • Custom or OOB fields: "Set next steps on <company name>: 'Send revised proposal by Friday'" or "Update loss reasons on OPTY100001."
      • Multi-field (up to five fields): "Update <company name>: stage to Negotiation, close date to June 30, forecast to Commit."
      • Owner: "Reassign the <company name> deal to Sarah Johnson."
      • Contact role: "Change Jane Smith's role on <company name> from Influencer to Decision Maker."
      • Competitor details: "Mark ABC as an incumbent on the opportunity."
      • Task — close: "Mark my <company name> follow-up task as complete."
      • Task — notes: "Add a note to my <company name> call task: 'Left voicemail, retry Thursday.'"
      • Task — reassign: "Reassign my <company name> follow-up task to Sarah Johnson."
      • Touchpoint — complete: "Mark my <company name> touchpoint from yesterday as completed."
      • Touchpoint — outcome: "Set the outcome of my last Acme call to Positive."
      • Touchpoint — notes: "Add a work note to my Acme touchpoint: 'Send SOW by Friday.'"
      • Contact fields: "Update Jane Smith's mobile to +1-555-0199" or "Change Jane Smith's title to Chief Procurement Officer."
      Create

      Examples by record type:

      • Opportunity: "Create a new opportunity for <company name>, $200K, closing in June." The account must already exist; if it's not found, the agent asks you to clarify.
      • Opportunity competitor: "Add Salesforce as a competitor on the <company name> deal." The agent prevents duplicate competitor entries on the same opportunity.
      • Opportunity contact with role: "Add Jane Smith as the economic buyer on <company name>." If the contact doesn't exist, the agent asks whether to create one.
      • Opportunity task: "Create a follow-up task on <company name> for next Monday." Relative due dates such as "next Thursday" are supported. The task is assigned to you by default.
      • Touchpoint — call or meeting: "Log a 30-minute discovery call with Jane Smith at <company name> today."
      • Contact: "Create a contact: John Doe, VP Sales at <company name>, john@abcd.com."
      Delete

      Supported operations:

      • Opportunity competitor: "Remove Salesforce from the <company name> competitor list" or "Delete Oracle as a competitor on OPTY100001."
      • Opportunity associated contact: "Deactivate Jane Smith from the <company name> opportunity" or "Disassociate John Doe from OPTY100001."
    3. Optional: Provide any additional information the agent asks for.
      Note:
      • For create operations, the agent asks for missing mandatory fields one at a time.
      • For update operations, it resolves ambiguous record references by asking you to select from a list.
      • Field-type validations run before any change is committed; if a value is invalid, the agent returns an error and suggests a correction.
    4. For create, update, and delete operations: review the confirmation card and confirm to commit.
      Note:
      The confirmation card shows what will change before anything is saved or deleted. For update operations, it shows the old and new value for each field. Retrieve operations return results directly without a confirmation step.
      The agent performs the operation and returns the result. For create operations, it returns the record name and a link. For delete operations, it confirms the record was removed. If you don't have the required access, the agent returns a permission denied message.