Introduction to the Org Intelligence

The Org Intelligence enhances development in the AI Context Hub by giving the Build Agent access to org metadata. This allows the AI Agent to help you with the following tasks:

• Understand metadata dependencies before starting development.
• Optimize implementations based on actual metadata.
• Query metadata using natural language.
• Gain insights into historical metadata configurations.
• Accelerate development using real objects and fields.
• Create formulas and validation rules more efficiently.

Together, these features help reduce the need for manual documentation.

Prerequisites

Before configuring Org intelligence, ensure you meet the following requirements: 

• You are an active Copado AI user.

• You have a valid API key.

• You have a valid org credential.

• You have a Salesforce org with Copado CI/CD installed.

• You are using a AI Context Hub org.

• Your CI/CD user has an authenticated org credential record.

• Your CI/CD user has a Copado license assigned.

Note

If you are not a Copado CI/CD user, you can still use Org Intelligence through the Salesforce Integration. In this case, the Build Agent will access your Salesforce metadata directly.

Configuration

If you are a Copado CI/CD user, the "Configure the CI/CD Integration" section in the article Copado CI/CD to configure Org Intelligence. Otherwise, see the "Connect the AI Context Hub to Salesforce" section in the article Salesforce Integration.

After the configuration is complete, you can query metadata directly from the Build agent within a workspace. You can also prompt the Build agent to generate code, validation rules, or formulas based on your metadata.

Capabilities and Limitations

Capabilities

• Understands most metadata types described in the Salesforce Metadata API v63.
• Reads metadata items by name using the Metadata API. If the name is incorrect, the AI can suggest alternatives.
• Describes various Salesforce metadata types and their structures.
• Understands Salesforce SObjects and their fields, enabling tasks like SOQL generation.
• Provides AI agents with metadata type documentation for more accurate responses.

Limitations

• What works best: Specific requests like "Which flows are associated with the Account object?"
• What to avoid: Open-ended queries requiring a full org assessment (e.g., "Analyze all metadata in my org"), which may result in incomplete or inaccurate responses.

Data Size

• The AI can process up to 180 KB of content per request. Larger metadata may be truncated.
• Profiles and permissions are not supported in this version.
• Other metadata types affected by this limit include:
• Long Apex classes
• Flows
• Lightning Web Components (LWC)
• Aura components
• Although the system is designed to notify users when data is truncated, the message may not always appear reliably. 

Search Functionality

• List Flows, Fields, and Objects support filtering by label and name.
• Search support for Custom Objects and Fields is limited. It's unclear if the search includes formulas, help texts, descriptions, or relationship names.
• Content search is not supported for most metadata types, including the following: 
• Flows
• LWCs​
• Aura components

• Static Resources

• Layouts

• Reports

• Dashboards

Because of this, some queries, such as “Where is this field used?” may not return accurate results.

Incomplete Metadata Details

Some metadata lists display the associated SObject name (e.g., in Fields, Triggers, Record Types, Flows, and FlexiPages), but may not provide additional information.

Unsupported Metadata Types

The following metadata types are not supported or may not function as expected:

• Reports
• Dashboards
• Email Templates
• Folders
• Profiles and permissions

Sample Prompts

Here are some example prompts you can use with Org Intelligence:

• Find usage: “Can you see where the EnvironmentCreate flow is called and used?”
• Explain flows: “Explain the EnvironmentCreate flow.”
• List configurations: “How many compact layouts are there for the User Story object?”
• Analyze logic: “Explain the logic of the triggers on the Account object.”

Next Steps

Enable context-aware AI responses that help you streamline DevOps workflows and deliver high-quality results. Connect the AI Context Hub to your Copado CI/CD and give the Build Agent access to your org's metadata.