Considerations for Using Agentforce with Account Engagement

Account Engagement Agentforce actions deploy from Account Engagement. Before you can deploy the actions, you must create an External Client App and a Named Credential.

Agent User Requirements

• Provide the agent with the Named Credential user and business unit ID for each Account Engagement Agentforce actions.
• Actions don’t run if the Named Credential isn't authenticated. To confirm access, we recommend testing a related invocable action after you authenticate the named credential.
• The agent user must have access to the APEX classes that are used to power the Account Engagement actions. To provide access, manually update their permission set.

Using Account Engagement Fields and Records with Agentforce

• To have the agent pull a value from a specific Account Engagement field, include the field in the agent instructions. This is especially helpful for record IDs, such as a list ID.
• The IDs used in Account Engagement actions almost always refer to Account Engagement ID fields. Prospect record actions include Account Engagement IDs. To translate IDs from a Salesforce record, additional actions are needed.
• Account Engagement actions return only 1,000 records, sorted by the most recently updated records.