Record merge fields connect your prompt templates to Salesforce object fields. The
prompt template type and the objects that you associated with your prompt template determine which
merge fields are available.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Performance, and Unlimited
Editions with the Einstein for Platform, or Einstein or Agentforce for Sales or
Service add-on, or Agentforce Foundations
Sales email prompt templates can have merge fields corresponding to these objects.
Recipient (the contact or lead)
Sender (the user)
Current Organization (the Sender’s Organization)
Field generation prompt templates can have merge fields corresponding to these objects.
Current User
Current Organization (the user’s Organization)
The object that you associated with the prompt template
Flex prompt templates can have merge fields corresponding to these objects.
Current User
Current Organization (the user’s Organization)
The objects that you associated with the prompt template
When you select a standard or custom object field in the Prompt Template Workspace, the field
is added to your template as Input:RecordName.FieldName.
During prompt resolution, real CRM values populate the merge fields based on the specific records
that your user selects.
For example, you have a prompt template that includes this sentence:
You are a support representative and you need to create a short summary of all open cases for the [Account Name] account.
You select the Astro’s
Bakery account record in Prompt Builder to associate it with your template, and then you run your
template.
You are a support representative and you need to create a short summary of all open cases for the {!$Input:Account.Name} account.
Prompt Builder replaces the Input:Account.Name merge field
with the account name “Astro’s Bakery.” The resolved response could look like this.
You are a support representative and you need to create a short summary of all open cases for the Astro’s Bakery account.
To use record merge fields in Prompt Builder, see:
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.