Sending Email from Omniscripts

Use emails to send alerts or notifications as part of a workflow, such as sending a summary of a customer’s changes to their account information or a report of new customer cases to agents. An Omniscript can send an email from a template or a custom message, and you can use data from Salesforce objects or other data sources in the email address or body fields.

For email templates, you need an email template and the object ID to send the email to (such as a contact, lead, or user). For more information on the What ID, see the Salesforce Email API documentation.

To send a custom email, you can use HTML or plain text for the email body. Also, you can use email addresses or object IDs for the recipient fields with these limits:

• To: 100 addresses
• BCC: 25 addresses
• CC: 25 addresses

For template or custom emails, you can send them from a Salesforce organization-wide email address. For more information, see Organization-Wide Email Addresses. For attachments, you have access to several sources. If your Omniscript has uploaded or retrieved a file, use the JSON node of a single or list of Salesforce sObject IDs.

• File Attachments From Omniscript: The Omniscript JSON node that contains a single or list of Salesforce File sObject IDs.
• Document Attachments From Omniscript: The Omniscript JSON node that contains a single or list of Salesforce Document sObject IDs.

You can also attach files in other locations, such as the Salesforce library or an object with a file attached:

• Content Version ID: Accepts the ID of a ContentDocument that is sent as an attachment with the Email Action.
• Document Attachments: Specifies the Attachment sObjects to add to the email.
• Attachment List: Supports attachment IDs merged from Data JSON. For example, %DocGenId%. When the email is sent, the attachment will be added to the email.

Important When you embed an Omniscript with an Email action in a Lightning or Experience Cloud page, the response from the action isn't included in the Data JSON. This means that if you add a messaging element after the Email action, it won't accurately show whether the action was successful.