sf-industry-commoncore-integration-procedure

Creates and validates OmniStudio Integration Procedures with 110-point scoring across six categories.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/amanpraaj/sf-skill-hub --skill sf-industry-commoncore-integration-procedure-amanpraaj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sf-industry-commoncore-integration-procedure
Source: https://github.com/amanpraaj/sf-skill-hub/tree/main/skills/salesforce/sf-industry-commoncore-integration-procedure
Command: npx skills add https://github.com/amanpraaj/sf-skill-hub --skill sf-industry-commoncore-integration-procedure-amanpraaj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Building OmniStudio Integration Procedures requires coordinating DataRaptor actions, Apex Remote Actions, HTTP callouts, and conditional logic while avoiding pitfalls like circular dependencies, unbounded queries, and missing error handling. This Skill guides the creation, validation, and deployment of production-grade server-side orchestrations with a strict 110-point scoring rubric. ## Core Features & Use Cases - IP Generation & Element Composition: Assembles DataRaptor Extract/Load/Transform actions, Remote Actions, HTTP callouts, Conditional Blocks, Loop Blocks, and nested IP calls into coherent multi-step orchestrations with explicit input/output mapping. - Strict Validation & Scoring: Scores procedures across 6 categories (Design, Data Operations, Error Handling, Performance, Security, Documentation) with block/warn thresholds that prevent deployment of anti-patterns like circular calls or DML without error handling. - Deployment & Testing Workflow: Provides CLI commands for querying OmniProcess records, deploying via sf project deploy, and a 5-phase testing strategy from unit to end-to-end. - Use Case: A developer needs to build an AccountOnboarding IP that extracts account data, validates it via an Apex Remote Action, calls an external API, and loads a contact record. The Skill generates the element chain, validates referenced DataRaptors exist, enforces error handling on the DML step, and produces a deployment-ready configuration. ## Quick Start Ask the agent to create an Integration Procedure with a given Type and SubType that orchestrates your DataRaptors and Apex classes, then review the validation score before deploying to your target org.

Frequently Asked Questions about sf-industry-commoncore-integration-procedure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an OmniStudio Integration Procedure?▼

Define a Type/SubType pair, then assemble elements such as DataRaptor actions, Remote Actions, and HTTP callouts in execution order with explicit input/output mappings. Deploy prerequisite DataRaptors first, then deploy the IP and set IsActive=true in the target org.

When should I use an Integration Procedure vs Flow or Apex?▼

Use an Integration Procedure for declarative multi-step server-side orchestration serving OmniStudio components like OmniScripts and FlexCards. Use Flow for standard Salesforce UI automation and Apex when you need complex computation or fine-grained transaction control.

How do I query Integration Procedures in Salesforce CLI?▼

Run sf data query with a filter on the OmniProcess object, for example SELECT Id, Name, Type, SubType FROM OmniProcess WHERE IsIntegrationProcedure=true. The IsIntegrationProcedure filter is required because IPs and OmniScripts share the same OmniProcess table.

Why does my Integration Procedure deployment fail?▼

Deployment fails when referenced DataRaptors or Apex classes are missing or inactive in the target org, or when the Type/SubType collides with an existing active IP. Deploy all prerequisite components first and verify them with a CLI query before deploying the IP.

How do I handle errors and rollback in Integration Procedures?▼

Follow each DataRaptor Load with a Conditional Block that inspects the response for errors, and store created record IDs so compensating actions can undo prior DML if a later step fails. IPs have no native cross-element transaction rollback, so strict atomicity requires an Apex Remote Action.

Can Integration Procedures call other Integration Procedures?▼

Yes, an Integration Procedure Action element calls a nested IP using its Type_SubType identifier in the ipMethod property. Circular calls are prohibited because they cause stack overflow, so map the full dependency graph before wiring nested calls.