Agentforce Record Update Actions
Salesforce documents a standard Agentforce action, UpdateRecordFields, that updates one or more fields on an existing Salesforce record.
Recorded characteristics
- Function
- Salesforce documents a standard Agentforce action, Update Record (API name UpdateRecordFields), that updates one or more fields on an existing record. Salesforce states that the Extract Fields and Values from User Input action must run before it. The documentation limits the action to updating field values on one existing record at a time and states that record creation, cloning, merging, associating a related record, transferring account ownership and submitting a quote are not supported.
- Data access
- Salesforce documents that only existing records that are searchable and User Interface API enabled, on objects with layouts, can be updated by this action, and that only fields on the record page layout that can be updated or created are returned, with read-only fields filtered out. Salesforce states that users must have permission to view and edit the record and the fields they want to update. Salesforce separately documents that agents in channels restricted to logged-in users operate in the context of the logged-in user with that user's access controls applied, while agents in channels that are not restricted to logged-in users operate in the context of an agent user record.
- Actions
- Can take actions
- External actions
- Unknown
- Human confirmation
- Conditional
- Permission basis
- Mixed
- Administrative control
- Salesforce documents that administrators assign permissions either to individual users or user profiles, or to the agent's user record, depending on the channel, and documents feature-level permissions for flows, Apex classes, prompt templates and knowledge or data features used by agent actions. Salesforce also documents that the Confirm, Edit Full Record and Cancel buttons shown by this action in Lightning Experience appear by default and cannot be configured.
- Default state
- Not established
- Availability
- Salesforce documents the Update Record action as available in Lightning Experience and in Enterprise, Performance, Unlimited and Developer Editions with Foundations, or Agentforce 1 or Einstein 1 Editions.
- Licensing
- Salesforce documents the edition requirements above for this action. The reviewed documentation does not establish further licensing terms for this specific action.
- External model or provider
- Not established
- Limitations and uncertainty
- The reviewed documentation establishes that the action itself writes field values to one existing record, but does not establish whether the action can act on records outside Salesforce or trigger external-system changes. The records and fields reachable depend on searchability, User Interface API support, page layouts and field-level access, which the documentation does not enumerate. The identity under which execution occurs differs by channel: the logged-in user in channels restricted to logged-in users, and an agent user record in channels that are not. Human confirmation is documented for Lightning Experience, where Confirm, Edit Full Record and Cancel appear by default and cannot be configured; the reviewed documentation does not establish confirmation behaviour for this action in other channels.
Evidence
- Agentforce Platform | Update Record
Supports: Function · Data access · Actions · Human confirmation · Availability · Licensing · Limitations · Primary source
Update Record action (UpdateRecordFields) updates one or more fields on an existing record.
Only searchable, User Interface API enabled records on objects with layouts; only updatable layout fields; users must have view and edit permission.
Confirm applies the updates to the record.
In Lightning Experience the action shows Confirm, Edit Full Record and Cancel buttons by default, which cannot be configured.
Available in Lightning Experience and listed editions.
Editions with Foundations, or Agentforce 1 or Einstein 1 Editions.
Documented considerations: one record at a time, no record creation, no cloning, merging, related-record association, ownership transfer or quote submission.
- Common User Access for Standard Agent Actions
Supports: Permission basis · Admin controls · Data access · Primary source
Channels restricted to logged-in users operate in the context of the logged-in user; other channels operate in the context of an agent user record.
Administrators assign permissions to users, profiles or the agent user record, plus feature permissions for flows, Apex and prompt templates.
User access controls are applied according to the channel context in which the agent runs.