Integration Definitions
Integration Definitions is a Setup page for managing reusable integration configurations that define how Salesforce connects to external systems.
Definition
Integration Definitions is a Setup page for managing reusable integration configurations that define how Salesforce connects to external systems. These definitions encapsulate connection details, authentication methods, and data mapping rules that can be referenced by multiple integration processes.
In plain English
“Here's a simple way to think about it: Integration Definitions package connection details into reusable units. Connection, schema, retry policy, error handling - encapsulated as a single named unit referenceable from Flows, Apex, and other consumers.”
Worked example
The developer at DataSync Corp creates an Integration Definition for their ERP system that specifies the REST endpoint, OAuth credentials via a Named Credential, and field mappings between Salesforce Order fields and the ERP's order schema. Multiple Flows and Apex classes reference this definition, so when the ERP endpoint changes, she updates it in one place.
Why Integration Definitions package connection details into reusable units
An integration to an external system needs a connection (URL, auth method), a data shape (schema), and a handful of behavior decisions (retry policy, error handling, transformation rules). Without a higher-level construct, those settings spread across Apex code, Named Credentials, Custom Metadata, and external configuration files. Integration Definitions consolidate them. One Integration Definition encapsulates all the per-integration details, making it referenceable by Flows, Apex, and other integration consumers as a single named unit.
The reason it's worth using over the alternative (each integration scattered across multiple Setup surfaces) is consistency. Multiple consumers calling the same external system can reference the same Integration Definition; a change to the connection happens in one place; the audit story for what the org connects to becomes legible. Build the habit of defining integrations here, and treat the catalog as the canonical inventory of external connections.
How organizations use Integration Definitions
Migrated scattered integration configs to Integration Definitions; consistent reuse across multiple consumers.
ERP integration defined once; multiple Flows reference the same Integration Definition.
Test your knowledge
Q1. What skill set is typically needed to work with Integration Definitions?
Q2. What is a Governor Limit in the context of Integration Definitions?
Q3. Where would a developer typically work with Integration Definitions?
Discussion
Loading discussion…