Structured Salesforce Agent
Update one or more Salesforce object types in a single, structured step, with explicit control over which objects to find, which properties to change, and how each change is generated. Optionally uses a meeting as context for extracting property values.

What It Does
For each object type you configure (for example Opportunity, Contact, Account, Lead, or Task), the agent searches Salesforce using your search instructions, optionally creates the object if it is not found, and then updates each property you list according to your natural-language instructions. It can read a property's existing value before writing, require other properties to be read first for context, replace or append to existing content, and pause for human approval before syncing a given property.
When To Use It
Use this when a workflow needs to update Salesforce with AI-generated content but you want guardrails around exactly what gets written, such as syncing meeting notes into specific opportunity or contact fields while requiring approval on sensitive properties. This is the preferred node for CRM updates; use it instead of Salesforce Agent for anything that writes data.
Configuration
Configure the node with these settings:
Field | What it controls |
|---|---|
Meeting | An optional meeting to use as context when extracting property values. Leave blank if there is no relevant meeting. |
Object Configurations | One entry per object type to update. At least one is required. External Object Type.: The Salesforce object type to update, such as |
Outputs
The node passes these values downstream. Check the Outputs tab on the configured node to confirm exact paths.
Variable | Type | Description | Example |
|---|---|---|---|
|
| Results for each object configuration, mirroring input structure |
|
|
| The search instructions that were used |
|
|
| Object IDs found/created by the search phase |
|
|
| Objects that were processed |
|
|
| Salesforce object ID |
|
|
| Salesforce object name/title |
|
|
| Status of each property update |
|
|
| Property name |
|
|
| Integration push event ID for lookup |
|
|
| The AI reasoning used to generate the property update value |
|
|
| Update status |
|
|
| Error message if failed |
|
|
| Error if the configuration failed entirely |
|
Example Workflow
After a discovery call, a workflow uses this node to find the account's open opportunity and update its Next Steps field with a summary generated from the meeting, while requiring confirmation before updating the Amount field.
Related Nodes
Salesforce Agent
Update Opportunity
Search Opportunity by Stage
Need More Help?
Reach the AskElephant support team by:
clicking the Support tab on the right side of your screen,
emailing [email protected],
or using
@askelephant supportin your dedicated Slack channel.