Definition
External Data Sources is a Setup page where administrators configure connections to external data systems that Salesforce can query in real time using Salesforce Connect. Supported protocols include OData 2.0, OData 4.0, and custom Apex adapters, allowing Salesforce to display external data as External Objects without importing it.
Real-World Example
The admin at GlobalTech configures an External Data Source using OData 4.0 to connect to their SAP system's product inventory API. Salesforce queries the SAP data in real time and displays it as an External Object called "SAP_Inventory." Sales reps can check live inventory levels from within the Salesforce Opportunity page without logging into SAP.
Why External Data Sources Matters
External Data Sources is the Setup page in Salesforce where administrators configure and manage all connections to external data systems that power Salesforce Connect. Each entry on this page represents a live bridge to an external database, API, or service — whether it's SAP, Oracle, a custom REST endpoint, or any OData-compliant system. The page supports OData 2.0, OData 4.0, and custom Apex adapters, giving organizations flexibility to connect to virtually any external system. Once configured, these data sources enable External Objects that display real-time external data as if it were native Salesforce data.
As an organization's integration architecture matures, the External Data Sources page becomes the central nervous system for cross-platform data access. Managing multiple data sources requires careful attention to authentication credentials, connection timeouts, rate limits, and error handling. Organizations that outgrow simple point-to-point integrations need the governance this page provides — each data source can be individually configured, monitored, and troubleshot. Without centralized management through this page, connections to external systems become scattered across custom code, middleware, and tribal knowledge, making the architecture fragile and difficult to audit during compliance reviews.
How Organizations Use External Data Sources
- GlobalTech Industries — GlobalTech Industries configured three External Data Sources on the setup page — one OData 4.0 connection to their SAP product inventory, one to their Oracle financial system, and a custom Apex adapter to their proprietary warehouse management API. Sales reps see inventory, pricing, and shipping data from all three systems as related lists on the Opportunity page without logging into any external application.
- Nimbus Cloud Services — Nimbus Cloud Services uses the External Data Sources page to manage connections to five different client data environments. Each client's data stays in their own secure system, but Nimbus support agents can view relevant client information through External Objects. The admin monitors connection health and query performance from the setup page to ensure SLA compliance.
- Redline Automotive — When Redline Automotive migrated from an OData 2.0 legacy parts catalog to a modern OData 4.0 API, the admin configured the new data source on the External Data Sources page alongside the old one. During the parallel testing period, they compared query response times and data accuracy between both sources before deprecating the legacy connection.