You are here:
Load Data into Omniscript Elements
You’ll likely need to pull data into an Omniscript to prefill elements, create selectable options, dynamically display elements, or test your Omniscript. You can use data from Salesforce objects or external and internal sources. Omniscripts use several ways to get this data: Omnistudio Data Mappers, Integration Procedures, REST APIs, or Apex. Users can also add or change data in an Omniscript.
For each of these methods, you’ll use Omniscript elements.
- To get data from Salesforce objects, you can use a Data Mapper Extract or Turbo Action element or an Integration Procedure Action element.
- If you need data from an internal or external source or to collect data from multiple sources, you can also use an Integration Procedure Action element.
- Or you can directly connect with the HTTP (to use REST APIs) and Remote (to use Apex classes and methods) action elements.
You can think of user input as a method to get data. Omniscripts have many types of input elements, including images, choices, URLs, phone numbers, signatures, time, and currency.
To prefill an Omniscript with data, see Seed Data Into an Omniscript
- Load Salesforce Data into an Omniscript Using an Omnistudio Data Mapper
Add Salesforce data to your Omniscript using a Data Mapper Turbo Action or Data Mapper Extract Action. - Prefill Repeatable Blocks
Prefill repeatable blocks with data by passing data to the block in an array format. - Set a Default Value for an Omniscript Element
The Default Value property sets the JSON value of an element to a static value by default. The default value is overwritten if the element is prefilled from an Omnistudio Data Mapper or JSON response. The Default Value property is available for the Input elements (except Custom LWC, Disclosure, File, Image, and Password).
