When building email templates to use in Salesforce User-based workflow rules, you must choose the correct merge field type to reference the right user's data in the email. Salesforce provides four different merge field types for User-based workflow rules, and selecting the wrong type results in the email containing data for the wrong user or displaying blank fields.
The four merge field types available in User-based workflow email templates are:
Understanding the difference between these types is essential for building accurate, automated email notifications for User object workflows in Salesforce.
When a Salesforce workflow rule is built on the User object, the email template that is triggered can reference different users depending on the purpose of the notification. Use the guidance below to select the correct merge field type.
Use Workflow Target User fields to reference the user record that was created or updated to trigger the workflow rule.
Example: A workflow rule fires when a new User record is created. You want the email to include the new user's name, email address, and profile. Use Workflow Target User merge fields (for example, {!WorkflowTargetUser.Name} or {!WorkflowTargetUser.Email}) to pull data from the newly created user record.
Use User fields to reference the user who created or updated the record that triggered the workflow rule — in other words, the person who performed the action that fired the workflow.
Example: A workflow rule fires when a User record is updated. You want the email to show who made the change. Use User merge fields (for example, {!User.Name} or {!User.Email}) to reference the administrator or person who performed the update.
Use Sending User fields to reference the Salesforce user account configured as the sender of the workflow email alert.
Example: You want the email footer to display the name and title of the system user account that sends automated emails in your org. Use Sending User merge fields for this.
Use Receiving User fields to reference the user who is receiving the workflow email alert.
Example: You want to personalize the email greeting with the recipient's first name. Use Receiving User merge fields (for example, {!ReceivingUser.FirstName}) to address the email to the correct person.
000382943

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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.