Skip to main content

​
Key Features

This action allows Glean agents to update specific fields on any Salesforce Opportunity that the user has access to. It integrates with your organization’s unique Salesforce schema, supporting both standard and custom fields.
  • Identify the Relevant Opportunity Record: Uses either AI suggestions or user confirmation from a dropdown list.
  • Preview Existing Live Values for Selected Fields: Displays current values and new suggestions.
  • Allow Users to Review and Edit: Enables users to review and modify any field value before changes are submitted.
  • Provide a Direct Link to the Updated Opportunity: Offers a link to the updated Opportunity on success or displays clear error messages on failure.

​
Usage Instructions

​
Set Up in Agent Builder

  1. In the Agent Builder, select the Salesforce update action by navigating to Select Step > Actions > By datasource > Salesforce > Update Salesforce Opportunity.
  2. Configure which Opportunity fields should be updated by selecting fields from your organization’s Salesforce schema using the dropdown.
  3. For each field, decide if the value will be filled by AI, chosen from a set, set as a fixed value, or provided by the user at runtime.
  4. Add instructions to guide how particular fields should be filled out.
  5. Save and deploy the agent.

​
Examples

  • Call Follow-up: After a customer call, an agent reads the call transcript and suggests updates to the Opportunity’s Stage, Next Steps, and Expected Close Date.
  • Batch Update: Reads changes from sheets or lists and batch updates information to Opportunities using agent looping.
  • Correction of Fields: If information changes or errors are detected (e.g., inaccurate Opportunity Owner or Amount), a user can quickly locate the Opportunity and update the relevant fields with guided assistance.

​
Best Practices and Troubleshooting

  • Identify the Opportunity in Previous Steps: Agents should have a search/read step to accurately identify the Opportunity. Skipping this may result in errors or poor matching.

​
Known Limitations

  • Not Supported in Background Agents: This action cannot be added to agents that run in the background.
  • Batch Processing: While batch processing is possible through loops, each update in the batch requires separate user confirmation—there is no “bulk confirm.”
  • No Automatic “Append/Overwrite” Detection: Users must specify text instructions in the step if new information should be appended to existing data in the field.
  • Support for Fields: Only fields the user has view/edit permissions for will be visible. Not all custom or complex field types may be supported in all releases.