Building Omnistudio Integration Procedure

This is your guide for building server-side Integration Procedures in OmniStudio, the orchestration layer that chains together DataRaptors, Apex callouts, HTTP actions, and conditional logic. It enforces a 110-point scoring system across six categories and won't let you deploy with circular IP calls or DML steps without error handling. The orchestration order matters: you need to build Data Mappers first, then the IP, then any OmniScripts or FlexCards that call it. Particularly helpful if you're hitting the edge cases like creating IPs via the Data API where you need to set IsIntegrationProcedure manually and remember that Name is required despite the docs being silent on it.