salesforce-industries-routing

Parse Salesforce Industries XML metadata to extract component details and relationships.

2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/PranavNagrecha/Salesforce-Intelligence --skill salesforce-industries-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: salesforce-industries-routing
Source: https://github.com/PranavNagrecha/Salesforce-Intelligence/tree/main/.claude/skills/salesforce-industries-routing
Command: npx skills add https://github.com/PranavNagrecha/Salesforce-Intelligence --skill salesforce-industries-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users understand and navigate Salesforce Industries / OmniStudio components and their metadata, providing insights into workflows and data mappings.

Core Features & Use Cases

  • Component Mapping: Provides detailed mapping of Salesforce Industries / OmniStudio components (OmniScript, Integration Procedure, DataRaptor, FlexCard, DecisionTable) and their relationships.
  • Version Detection: Identifies the version of Salesforce Industries / OmniStudio in use within an org.
  • Query Routing: Routes queries to the appropriate tools based on the user's request.
  • Use Case: For a developer, this Skill can be used to understand the flow of a specific OmniScript or to identify the endpoints hit by an Integration Procedure.

Quick Start

Query the Salesforce Industries component 'AccountLinking_Existing_English_1' to retrieve its flow and dispatched actions.

Frequently Asked Questions about salesforce-industries-routing

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

FAQPage Schema
How do I extract component relationships from Salesforce Industries metadata XML?

To extract component relationships from Salesforce Industries metadata, you parse the XML files to analyze OmniStudio components. This process identifies component details, maps relationships between OmniScripts and DataRaptors, and retrieves version information.

How do I trace the flow of an OmniScript component?

Tracing the flow of an OmniScript component requires analyzing its underlying metadata XML. By parsing these files, you retrieve the specific flow structure and identify the dispatched actions executed within the Salesforce Industries automation.

Does this metadata analysis apply to all Salesforce orgs?

No, this metadata analysis applies specifically to Salesforce orgs using Salesforce Industries for process automation and integration. It targets OmniStudio metadata structures rather than standard Salesforce configuration files.

How do I identify which endpoints are hit by an Integration Procedure?

To identify endpoints hit by an Integration Procedure, you analyze the component's metadata XML. Parsing this metadata reveals the integration mappings and dispatched actions, allowing you to see the specific external endpoints called during execution.

What is the best way to detect the OmniStudio version in use within an org?

The best way to detect the OmniStudio version in use is by analyzing the org's metadata XML files. Parsing these files extracts specific version information embedded in the Salesforce Industries component definitions.

What components are supported by Salesforce Industries metadata mapping?

Salesforce Industries metadata mapping supports OmniStudio components including OmniScript, Integration Procedure, DataRaptor, FlexCard, and DecisionTable. It extracts their details and maps the relationships between these elements.