Use Action steps to run autolaunched flows and send emails. Action steps let your bot
use Apex to create, read, update, or delete Salesforce objects, retrieve data and display it,
and retrieve external data from a third-party API. Add a goal to a dialog to evaluate how well
your bot is helping your customers.
Apex methods must be written with InvocableMethod annotation to be accessible to bots.
For more information on the annotation, visit the Developer Guide.
When a custom value is entered as an Apex input, it’s interpreted as a string.
When logging exceptions in Apex, remove all references to personal identifying
information (PII) and customer inputs in the error message.
When processing object values, we support up to five levels of nested objects in outputs
and one level of nested objects in inputs.
Apex actions have a default timeout of 10 seconds each.
The overall processing time limit for a bot response is 20 seconds.
A maximum of 50 apex calls (across any number of dialogs) can be made before sending an
outbound message.
To add an Action step to the dialog, from the Dialog Component Library, drag a step
from the Actions section onto the canvas.
In the Step Properties panel, set the action name and any input and output
variables.
Save the dialog.
You can debug Apex calls from the event logs in the Performance page.
Add an Object Search Action Deliver records from standard or custom objects to your Einstein Bot to create an integrated bot experience. The Object Search action type can be added to any dialog.
Add an External Service Action Add an action from a registered external service in Bot Builder to allow your bot to send and receive data between Salesforce and external API providers. Deliver personalized customer experiences without writing a single line of code.
Add a Standard Action Call a standard invocable action directly from your bot, without referencing it from an Apex class or flow. Use Knowledge actions, custom and standard notification actions, and more.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.