Omnistudio Integration Procedure Generate

This generates server-side Integration Procedures for OmniStudio, the declarative orchestration layer that chains together DataRaptors, Apex callouts, HTTP actions, and conditional logic. You'd reach for it when you need multi-step server processes that combine data from Salesforce objects and external APIs without writing code. It enforces a 110-point scoring system that blocks deployment if you're missing error handling on DML operations or referencing DataRaptors that don't exist yet. The workflow is opinionated about build order: dependencies first, then DataRaptors, then the Integration Procedure itself, then any OmniScripts or FlexCards that call it. One honest take: the validation is strict enough to catch the circular dependency and hardcoded ID mistakes that usually surface in production.

skills.sh installs: 4.8K
GitHub stars: 1.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add forcedotcom/sf-skills --skill omnistudio-integration-procedure-generate --agent claude-code

Installs into .claude/skills of the current project.

Files

omnistudio-integration-procedure-generate: OmniStudio Integration Procedure Creation and Validation

Expert OmniStudio Integration Procedure (IP) builder with deep knowledge of server-side process orchestration. Create production-ready IPs that combine DataRaptor/Data Mapper actions, Apex Remote Actions, HTTP callouts, conditional logic, and nested procedure calls into declarative multi-step operations.

Scope

In scope: Creating well-structured Integration Procedures from requirements; selecting and wiring element types (DataRaptor, Remote Action, HTTP, Conditional Block, Loop, Set Values, nested IP); dependency validation; error handling patterns; 110-point scoring; deployment and activation
Out of scope: Building OmniScripts (use omnistudio-omniscript-generate), creating Data Mappers directly (use omnistudio-datamapper-generate), designing FlexCards (use omnistudio-flexcard-generate), mapping full dependency trees (use omnistudio-dependencies-analyze), deploying metadata to org (use platform-metadata-deploy)