OmniStudio Implementation Guide: OmniScripts, FlexCards & DataRaptors Explained
OmniStudio is the declarative engine powering every Salesforce Industry Cloud — a suite of no-code/low-code tools that lets teams build guided processes, contextual UI cards, and server-side data orchestrations without writing Apex.
Originally acquired as Vlocity for $1.33 billion in 2020, OmniStudio now ships standard with all 12+ Industry Clouds: Health Cloud, Financial Services Cloud, Automotive Cloud, Communications Cloud, and every other vertical. For Salesforce architects, developers, and implementation partners, OmniStudio fluency is no longer optional — Gartner projects the industry cloud platform market will reach $260.9 billion by 2027 at a 17% CAGR.
Yet OmniStudio appears zero times on most Salesforce partner websites, including (until this article) ours. This guide changes that. We’ll break down every core component, explain when to use OmniStudio vs Apex or Flow, cover licensing, and show how OmniStudio connects to Data Cloud and Agentforce.
The Four Pillars of OmniStudio
OmniStudio operates as a three-layer stack: a digital experience layer (OmniScripts and FlexCards for the UI), a service management layer (Integration Procedures and DataRaptors for backend orchestration), and a developer tooling layer (SF CLI and IDX for deployment). Understanding how these layers interact is the foundation for every implementation decision.
OmniScripts: Guided Multi-Step Wizards
What they are: OmniScripts are guided, multi-step processes that walk users through complex business workflows — loan applications, care plan creation, vehicle service scheduling, insurance claims. Everything is configured declaratively through a drag-and-drop designer. The underlying architecture is JSON-based: every element maps to a JSON key, and data flows between steps through this structure.
How they work: When activated, OmniStudio compiles each OmniScript into a Lightning Web Component automatically. OmniScripts are identified by a unique Type + SubType + Language combination, and only one active version can exist per combination. The element library spans five categories: Group elements (Steps, Blocks, Edit Blocks, Type Ahead Blocks), Input elements (text, number, date, file, lookup, etc.), Action elements (Integration Procedure, DataRaptor, HTTP, Remote Apex, Email, DocuSign, PDF generation), Display elements (Text Blocks, Headlines, Data Tables), and Function elements (formula calculations, conditional logic).
When to use: Choose OmniScripts over Screen Flows when you need pixel-perfect branded experiences, complex hierarchical JSON data handling, external API integration without code, or multi-channel deployment (web, mobile, Experience Cloud, external CMS via OmniOut). Salesforce’s own Architect Decision Guide states: “If you’re an Industries customer and need pixel-perfect branding or complex hierarchical data, use OmniStudio.”
FlexCards: Contextual UI Components
What they are: FlexCards are contextual data display components that surface information at a glance and provide entry points to actions. Built with a WYSIWYG drag-and-drop editor, they compile into LWCs on activation. Think of them as smart, data-driven cards that replace custom Lightning components for 80% of display-only use cases.
How they work: FlexCards support ten data source types: SOQL, SOSL, DataRaptor, Integration Procedure, Apex Remote, Apex REST, Named Credential REST, Custom JSON, SDK, and parent card inheritance. Their key design feature is states — multiple visual configurations of the same card triggered by data conditions. A patient’s FlexCard might show a green “Active Coverage” state or a red “Expired” state based on the same data source. Flyouts provide popovers for additional detail without navigation.
When to use: Choose FlexCards over custom LWCs for record detail displays, summary cards, and contextual data panels. FlexCards render at 1,800–2,000ms for large datasets versus 600–700ms for equivalent custom LWCs — so for high-performance, data-heavy scenarios (5,000+ items), custom LWC remains the better choice. For most record-context displays, FlexCards deliver faster time-to-deploy with no Apex test class overhead.
DataRaptors: Declarative ETL for Salesforce Data
What they are: DataRaptors (renamed Data Mappers in 2024) are declarative tools that read, transform, and write Salesforce data without SOQL or DML in code. Four types exist:
Turbo Extract: High-performance reads from a single object (up to 5 parent levels). 14–30% faster runtime than standard Extract. Use this as the default for all single-object queries.
Extract: Multi-object reads with full formula support, paging, and complex JSON/XML output mapping. Use when querying across multiple related objects.
Transform: Reshapes data in memory — converting JSON to XML, renaming fields, applying formulas — without touching the database. Use between Extract and Load to reshape data structures.
Load: Writes data to one or more objects, supporting upsert via external keys, parent-child linking in a single transaction, and batch sizes up to 2,000 records.
Integration Procedures: Server-Side Orchestration
What they are: Integration Procedures are the orchestration engine — server-side processes that execute multiple actions in a single server call, eliminating client round-trips. They chain DataRaptor extracts, loads, transforms, HTTP callouts, Apex invocations, and sub-Integration Procedures into sequenced or parallel workflows.
How they work: Block types include Cache Blocks (configurable TTL, reducing query times by 40–60%), Conditional Blocks (if/else branching), Loop Blocks (array iteration), and Try-Catch Blocks for error handling. Integration Procedures can run synchronously, asynchronously (Future), Fire-and-Forget, Non-Blocking, or as Queueable chains to avoid governor limits. Response Actions trim output payloads by 25–35%.
Why they matter: Integration Procedures deliver 35–45% higher developer productivity versus equivalent Apex controller classes. A single Integration Procedure can serve as a FlexCard data source, an OmniScript action, a REST API endpoint, AND an Agentforce agent action simultaneously. This reuse is the architectural superpower of OmniStudio.
The canonical data flow: User → FlexCard/OmniScript → Integration Procedure → DataRaptor → Salesforce Data/External APIs. This separation of concerns keeps the UI decoupled from the data layer, enabling reuse that’s impossible with tightly-coupled Apex controllers.
OmniStudio vs Custom Apex vs Lightning Flow: When to Use What
| Dimension | OmniStudio | Lightning Flow | Custom Apex |
| Best for | Industry Cloud guided processes | Internal automation | Complex logic, high-volume batch |
| Coding required | No (declarative) | No (declarative) | Yes (Apex + LWC) |
| JSON handling | Native hierarchical | Limited | Full (manual) |
| External API calls | HTTP Actions (no code) | HTTP callout (limited) | Full HttpRequest class |
| Multi-channel deploy | Web, mobile, CMS, OmniOut | Salesforce only | Custom build per channel |
| Branding control | Pixel-perfect CSS | Salesforce-themed | Full custom |
| Test coverage | Built-in Test Procedures | Flow test framework | 75% Apex test coverage |
| Agentforce native | Yes (IP as Agent Action) | Yes (Flow as Action) | Yes (Invocable Apex) |
| Performance | Turbo Extract 14-30% faster | Standard | Optimized (manual) |
| Licensing | Industry Cloud or add-on | Included in all editions | Included in all editions |
The hybrid approach wins: Use OmniStudio as the default for all Industry Cloud work. Invoke Apex via Remote Actions only when declarative capabilities are insufficient (complex calculations, advanced batch processing). Embed custom LWCs within OmniScripts/FlexCards when UI requirements exceed the declarative toolkit. This pattern gives you 80% declarative speed with 100% capability coverage.
Licensing: What’s Included and What Costs Extra
Included with Industry Clouds: OmniStudio comes bundled at no extra charge with every Salesforce Industry Cloud license — Financial Services Cloud, Health Cloud, Automotive Cloud, Communications Cloud, Insurance Cloud, Energy & Utilities Cloud, Media Cloud, Education Cloud, Public Sector Solutions, Nonprofit Cloud, Manufacturing Cloud, Consumer Goods Cloud, and Contract Lifecycle Management. If you already use any Industry Cloud, you already have OmniStudio.
Standalone add-on: For organizations wanting OmniStudio without a full Industry Cloud subscription, a standalone license is available through Salesforce sales representatives. Per-user pricing is not publicly listed. Additional API calls (OmniStudio Additional Calls 2M) are priced at $10,000/unit/month.
Standard vs Managed Package runtime: This is the most critical licensing distinction in 2026. The standard runtime uses native Salesforce objects (OmniProcess, OmniUiCard), supports SF CLI deployment, receives all new features, and integrates with Agentforce. The managed package (Vlocity) runtime is in maintenance mode — no new features. Migration to standard runtime is not optional. It’s inevitable.
How Industry Clouds Use OmniStudio in Practice
Health Cloud
OmniScripts power care management: the Care Plan Creation Wizard guides care managers through building enhanced care plans from templates. Additional pre-built scripts handle utilization management, provider recruitment with primary source verification, member ID card generation, and health risk assessments. FlexCards power the patient 360 view — the CareGapManager FlexCard helps care managers identify and act on gaps in care. Integration Procedures connect to external EHR systems (Epic, Cerner) via HL7/FHIR APIs and MuleSoft.
Financial Services Cloud
FSC includes a complete prebuilt onboarding application with OmniScripts, Flows, Integration Procedures, and Data Mappers ready for customization. Loan origination OmniScripts create compliant, guided approval workflows. KYC processes leverage FSC’s data model through OmniStudio-powered identity verification. FlexCards display real-time client portfolio views and relationship hierarchies via the Actionable Relationship Center. The Discovery Framework uses OmniStudio for digital data-gathering forms.
Automotive Cloud
OmniStudio powers appointment scheduling workflows. The Driver Console FlexCard provides a complete view of customer interactions, browsing history, and service journeys. The Vehicle Console FlexCard displays odometer readings, market value, and real-time service data. At Xillentech, DealerVogue extends Automotive Cloud’s OmniStudio components with pre-built warranty verification agents, parts lookup, and service scheduling — each powered by Integration Procedures that serve both FlexCards and Agentforce agents from the same declarative logic.
OmniStudio + Data Cloud + Agentforce: The 2026 Integration
The most significant 2025–2026 development: Integration Procedures now run natively as Agentforce agent actions. This is a first-class integration that lets autonomous AI agents trigger backend logic, call APIs, and execute multi-step workflows.
Configuration: In the Integration Procedure Designer, click “Configure Agentforce,” define input/output JSON, verify data, and activate. Then create an Agent Action in Setup referencing the procedure and link it to an Agent Topic. The Atlas Reasoning Engine determines when to invoke the IP based on conversational context.
This creates a powerful pattern: an Agentforce agent receives a customer request, reasons about it, invokes an Integration Procedure to fetch data from Data Cloud and external systems, processes business logic through chained DataRaptors, returns results to the agent, and surfaces contextual information on FlexCards for the human agent. One Integration Procedure serves FlexCards, OmniScripts, REST consumers, AND Agentforce agents — the ultimate reuse pattern.
Data Cloud connectivity: Integration Procedures serve as the bridge to Data Cloud (now Data 360). Data Mappers query Data Cloud DMOs materialized as accessible Salesforce objects. HTTP Actions call Data Cloud’s Query API and Data Graph API directly. FlexCards display unified customer profiles by using Integration Procedures as their data source, aggregating data across DMOs — unified individual records, engagement data, segment membership, and calculated insights.
Spring ’26 update: Salesforce introduced the OmniStudio Assistance AI Agent (pilot) — a context-aware AI that provides guidance directly in the OmniStudio designer while building components. It requires both a Data 360 license and Agentforce add-ons, signaling Salesforce’s vision of these three platforms as a single converged solution.
Implementation Best Practices: 8 Patterns That Separate Success from Failure
1. Never deploy OmniStudio via Change Sets. OmniStudio components have nested dependencies that Change Sets don’t handle reliably. Use the Vlocity Build Tool (VBT), SF CLI, or specialized tools like Gearset and Copado. Deploy standard Salesforce metadata first, then OmniStudio DataPacks, and automate component activation post-deployment.
2. Default to Turbo Extract for all single-object queries. 14–30% faster than standard Extract. Reserve standard Extract for multi-object joins with formula support. This single decision impacts every DataRaptor in the org.
3. Cache aggressively in Integration Procedures. Cache Blocks with configurable TTL reduce query times by 40–60% for frequently accessed, infrequently changing data (product catalogs, rate tables, config metadata). Every Integration Procedure should evaluate caching opportunities.
4. Use Response Actions to trim output. By default, Integration Procedures return the entire data payload. Response Actions strip unnecessary fields, reducing data transfer by 25–35%. This matters especially for FlexCard data sources where only 5–10 fields are displayed but 50+ are returned.
5. Establish naming conventions before the first component. The standard runtime forbids underscores in component names. Adopt PascalCase consistently: DRExtractAccountDetails, IPCalculatePremium, OSCreateApplication. Inconsistent naming makes VBT queries unmanageable and deployment automation fragile.
6. Respect the 200-element limit per OmniScript. The combined ceiling is 750 elements. Large processes should be split into sub-OmniScripts that launch from parent scripts. This also improves reuse — a common data collection sub-script can serve multiple parent workflows.
7. Plan your Vlocity-to-standard migration now. The December 2025 OmniStudio Migration Assistant automates most conversion, but Angular-to-LWC OmniScript conversion, VlocityOpenInterface-to-System.Callable Apex updates, and reserved keyword removal require manual work. Use a three-phase approach: Dev Sandbox (assess + migrate), Validation Sandbox (regression test), then Production.
8. Build Integration Procedures as your reusable service layer. A single IP can serve a FlexCard, an OmniScript action, a REST API, and an Agentforce agent action. Design IPs as your canonical data access layer — never have FlexCards or OmniScripts query data directly via SOQL data sources when an IP can centralize the logic.
Frequently Asked Questions
What is OmniStudio in Salesforce?
OmniStudio is Salesforce’s declarative toolkit for building guided processes (OmniScripts), contextual UI cards (FlexCards), data orchestration (Integration Procedures), and declarative ETL (DataRaptors/Data Mappers) without writing code. Originally acquired as Vlocity for $1.33 billion in 2020, OmniStudio is now included with all 12+ Salesforce Industry Clouds and serves as the UI and process layer for healthcare, financial services, automotive, communications, and other vertical solutions.
When should I use OmniStudio vs Lightning Flow?
Use OmniStudio when you need pixel-perfect branded experiences, complex hierarchical JSON data handling, external API integration without code, multi-channel deployment (web, mobile, Experience Cloud, external CMS), or when you’re building on any Industry Cloud. Use Lightning Flow for simple internal automation, straightforward guided tasks, or organizations without Industry Cloud licenses. Salesforce’s Architect Decision Guide recommends OmniStudio for Industries customers with complex data or branding requirements.
When should I use OmniStudio vs custom Apex?
Use OmniStudio as the default for data integration, guided processes, and contextual displays. Integration Procedures replace Apex service classes. DataRaptors replace SOQL wrapper classes. FlexCards replace simple display-only LWCs. Use Apex when you need extreme logic complexity, fine-grained performance control for high-volume scenarios, custom batch processing, or specialized UI behaviors beyond the declarative toolkit. The recommended pattern is hybrid: OmniStudio default, Apex via Remote Actions for edge cases.
Is OmniStudio included in my Salesforce license?
OmniStudio is included at no extra cost with every Salesforce Industry Cloud license — Health Cloud, Financial Services Cloud, Automotive Cloud, Communications Cloud, and all others. For organizations without Industry Cloud, a standalone add-on license is available through Salesforce sales (pricing not publicly listed). OmniStudio requires Enterprise, Performance, or Unlimited Edition.
What is the difference between OmniStudio standard runtime and managed package?
The standard runtime uses native Salesforce objects, supports SF CLI deployment, receives all new features, and integrates with Agentforce and Data Cloud. The managed package (Vlocity) runtime uses custom namespaced objects, relies on the Vlocity Build Tool, and is in maintenance mode — no new features. Migration to standard runtime is mandatory for Agentforce integration and all future enhancements. The OmniStudio Migration Assistant (December 2025) automates most of the conversion.
How does OmniStudio connect to Agentforce?
As of Summer ’25, Integration Procedures run natively as Agentforce agent actions. Configure Agentforce in the IP Designer, define input/output JSON, activate, then create an Agent Action in Setup. The Atlas Reasoning Engine determines when to invoke the IP based on conversational context. This means one Integration Procedure can serve FlexCards, OmniScripts, REST APIs, and Agentforce agents simultaneously — the ultimate reuse pattern.
What are OmniStudio implementation best practices?
Eight key practices: deploy via VBT or SF CLI (never Change Sets), default to Turbo Extract for single-object queries (14–30% faster), cache aggressively in Integration Procedures (40–60% query reduction), use Response Actions to trim payloads (25–35% smaller), establish PascalCase naming conventions before first component, respect the 200-element OmniScript limit, migrate from Vlocity managed package to standard runtime now, and build Integration Procedures as your reusable service layer serving all consumers.
Need OmniStudio Expertise for Your Industry Cloud Implementation?
Xillentech builds OmniStudio-native solutions on Automotive Cloud (DealerVogue), Health Cloud (MedVogue), and Financial Services Cloud. Our team holds OmniStudio Developer certifications and 8+ Agentforce certifications. We architect Integration Procedures as reusable service layers that serve FlexCards, OmniScripts, and Agentforce agents from the same declarative logic.
