DataRaptor
DataRaptor is an OmniStudio tool for reading, transforming, and writing Salesforce data in real time - a lightweight, configurable data integration layer that extracts from objects, applies transformations, and persists changes back without custom Apex.
Definition
DataRaptor is an OmniStudio tool for reading, transforming, and writing Salesforce data in real time - a lightweight, configurable data integration layer that extracts from objects, applies transformations, and persists changes back without custom Apex. Starting with Summer '24, Salesforce is renaming DataRaptors to OmniStudio Data Mapper (Data Mapper Extract, Transform, Load, and Turbo Extract); the old and new names refer to the same capability.
In plain English
“A DataRaptor (renamed OmniStudio Data Mapper in Summer '24) is the declarative "pipe" OmniStudio uses to talk to Salesforce data. Instead of writing Apex, an admin points a DataRaptor at an object, says "pull these fields," optionally reshapes the result, and OmniStudio components like OmniScripts and FlexCards use it to read or write data at runtime.”
Worked example
A developer at Meridian Finance builds a customer-service OmniScript that needs to pull a Contact's recent Cases and open Opportunities, reshape the result into a simplified view, and let the agent save a case note. They configure a DataRaptor Extract (now Data Mapper Extract) to read Contact, Case, and Opportunity in one call, a Transform to flatten the result for the UI, and a Load to write the note back - all declarative, with no Apex remote actions.
Why DataRaptor matters
DataRaptor (now being renamed to OmniStudio Data Mapper starting Summer '24) is the OmniStudio tool that provides a configurable data integration layer between OmniStudio components (OmniScripts, FlexCards, Integration Procedures) and Salesforce data. There are four variants: Extract (reads from Salesforce objects), Transform (reshapes data structure without a database call), Load (writes data back), and Turbo Extract (a faster, schema-constrained extract for performance-critical reads). Each is configured declaratively through a UI-based mapping rather than written in Apex.
Because DataRaptors are declarative, they lower the bar for who can own OmniStudio data integrations - admins and configurators can build and maintain them alongside developers, which is a significant part of why OmniStudio projects move faster than Apex-heavy equivalents. For orchestration across multiple data operations (conditional branches, looped calls, remote service calls), combine DataRaptors with Integration Procedures, which sequence one or more DataRaptors plus other actions into a single callable unit.
How organizations use DataRaptor
Built an OmniScript that uses DataRaptor Extract to read customer data, DataRaptor Transform to reshape it for the UI, and DataRaptor Load to save user input back. The whole flow is declarative with no Apex needed.
Uses DataRaptor Turbo Extract for performance-critical reads in customer-facing OmniStudio apps. The Turbo variant cut response times noticeably compared to standard Extract.
Trained their admin team to build DataRaptors for routine OmniStudio data operations. This took the data layer work off the developer team and let admins move faster on customer requests.
Test your knowledge
Q1. What is DataRaptor?
Q2. What are the main DataRaptor types?
Q3. Why use DataRaptor instead of Apex for OmniStudio data operations?
Discussion
Loading discussion…