When I first opened OmniStudio, I felt the way a new student feels on the first day of class: surrounded by unfamiliar words, unsure where to sit. FlexCards, OmniScripts, DataRaptors, Integration Procedures. It sounded like a lot. But after spending real time with it, I learned that OmniStudio is far gentler than its vocabulary suggests. So before we study any single tool, let me give you the map. Once you see the whole landscape, every detail finds its place.
So what is OmniStudio, really?
OmniStudio is Salesforce’s low-code toolset for building guided digital experiences. “Low-code” means you build mostly by configuring components rather than writing long programs. “Guided digital experiences” means the screens and flows a person moves through to get something done: opening an account, filing a claim, checking the status of an order.
It grew out of a company called Vlocity, which Salesforce acquired, and it lives most naturally inside the Industries products: Communications, Insurance, Health, Public Sector, and others. You do not have to work in those industries to use it, but that is where it shines, because those businesses share a common need: complex data, displayed clearly, captured through friendly step-by-step screens.
OmniStudio is not one tool. It is four tools that hand work to each other, each doing the one job it does best.
The four pillars
Here is the whole toolset in plain language. Read it once, and the rest of this series will feel familiar.
FlexCards display data
A FlexCard is a small, reusable card that shows information and offers actions. Think of the summary card you see at the top of a customer record: name, status, a phone number, a button or two. FlexCards are declarative and reusable, and they can change their appearance based on the data, showing a green badge for active accounts and a grey one for closed ones. We go deeper in OmniStudio FlexCards.
OmniScripts guide the user
An OmniScript is a configurable, multi-step flow, much like a wizard. Step one collects a name, step two collects an address, step three confirms and submits. If you have ever built a Salesforce Flow screen, the idea will feel close. OmniScripts are how OmniStudio handles input and guided journeys, and we explore them in OmniScripts.
DataRaptors move the data
FlexCards and OmniScripts need data, and they need somewhere to send it. DataRaptors are the data layer. They read Salesforce data (Extract), reshape it (Transform), and write it back (Load). They are the quiet workers that keep everything supplied.
Integration Procedures orchestrate
When a job needs several steps on the server, like reading two objects and calling an external system, an Integration Procedure runs them together in one efficient server-side call. It keeps the heavy lifting off the screen and out of the browser.
How they fit together
Picture a small ensemble. The FlexCard is the face the audience sees. The OmniScript is the sequence that guides the performance. The DataRaptor fetches and stores the notes. The Integration Procedure conducts the players behind the scenes so they stay in time. Each is modest on its own, but together they produce something complete.
A typical flow looks like this. A FlexCard shows a customer summary. A button on that card launches an OmniScript. As the user moves through the steps, DataRaptors read existing data to pre-fill fields and later write the new data back. If the script needs something more involved, it calls an Integration Procedure to handle the orchestration on the server. Four tools, one smooth experience.
Why learn it this way
You might wonder why Salesforce offers this when it already has Lightning Web Components and Flow. The honest answer is that OmniStudio trades some flexibility for speed and consistency in industry scenarios. For deeply custom needs, code still wins. I compare the two paths openly in OmniStudio vs Lightning Web Components, because choosing the right tool matters more than mastering any one of them.
For now, hold the map in your mind: four pillars, each with a job, each handing work to the next. In the articles ahead we will pick them up one at a time, slowly, the way I would teach any new skill. No rush. The vocabulary stops being scary the moment you see what each word actually does.
Your next step
Start with the visible layer, then follow the data: