Salesforce Certified OmniStudio Developer – Complete Winter '26 Guide

Custom LWC Integration with OmniStudio

OmniStudio Developer extends the platform with custom Lightning Web Components (LWC) embedded within OmniScripts and FlexCards. Custom LWC elements in OmniScripts receive and pass data via the OmniScript SDK methods (omniApplyCallResp, omniUpdateDataJson). Custom FlexCard actions can trigger custom LWC components. The developer creates reusable custom components that follow OmniStudio data contracts — understanding the JSON data model that flows through OmniStudio is critical. The exam tests how to integrate custom LWC with OmniScript data binding.

DataRaptor Architecture: Extract, Load, Transform

DataRaptor Extract queries Salesforce data using SOQL within a structured configuration — supports parent-child relationships and field mapping. DataRaptor Load creates or updates records using a structured JSON input — supports multi-object transactions (parent + children in one call). DataRaptor Transform maps and reshapes JSON data between two structures — no Salesforce DML involved. Turbo Extract is a simplified, high-performance version of Extract that runs a direct SOQL query. The developer exam tests DataRaptor configuration for complex data transformation scenarios and when each type is appropriate.

Integration Procedures: Advanced Patterns

Advanced IP design: chaining Integration Procedures (calling a sub-IP from a parent IP), conditional branching (If Block, Filter Block), and looping (Loop Block to iterate over arrays). Error handling: Set Error action captures exceptions from HTTP actions or Apex. Response mapping transforms the action response into the IP's output structure. Combining multiple data sources in one IP — e.g., call DataRaptor Extract for Salesforce data, HTTP Action for external pricing API, then Transform to merge results. The developer designs IPs that are efficient, maintainable, and handle errors gracefully.

Debugging OmniStudio Components

OmniScript debug mode activates the step-by-step data viewer — showing the JSON data model at each step. DataRaptor preview allows testing Extract, Load, and Transform configurations with sample inputs without running through a full OmniScript. Integration Procedure test console sends test payloads and inspects responses. FlexCard preview shows the rendered card with sample data. Browser developer tools (Network tab, Console) help debug HTTP Action calls and LWC component errors. The developer uses these tools systematically to isolate issues — checking data, mapping, and API calls independently.

OmniStudio Deployment and Packaging

OmniStudio components are deployed as metadata via Salesforce CLI (sfdx or sf commands). OmniScript and FlexCard definitions export as JSON — they can be version-controlled in Git. DataRaptors and Integration Procedures also export as JSON. Import/Export in the OmniStudio UI allows moving components between orgs. For managed packages (ISV deployment), OmniStudio components follow standard Salesforce packaging rules. The developer understands the deployment sequence — DataRaptors and IPs must be deployed before the OmniScripts that reference them.

OmniScript Design

Know how to configure OmniScript elements: Text/Number/Date inputs, Select (picklist/multi-select), File Upload, Validation, Set Values, and Navigate. Understand Step navigation, conditional visibility, and error handling patterns.

DataRaptor Transforms

Know the four DataRaptor types: Extract (reads Salesforce data), Load (writes to Salesforce), Transform (reformats data without CRM access), and Turbo Extract (simplified read). Know input/output JSON mapping configuration.

Integration Procedures

Know how to build Integration Procedures for server-side data orchestration: HTTP Action (external API calls), DataRaptor Turbo Action, Loop Action, Conditional Action, and Set Values. Understand how they differ from DataRaptors.

FlexCard Development

Know how to configure FlexCard elements (field blocks, action blocks, state management) and how to embed FlexCards in Lightning pages and OmniScripts. Understand datasource configuration and card state transitions.

Custom LWC in OmniStudio

Know how to create custom LWC components that extend OmniStudio: OmniscriptBaseMixin for accessing OmniScript context, custom components in FlexCards, and how to register custom components as OmniStudio elements.