External Services
A Salesforce feature that lets admins register third-party REST APIs (via OpenAPI specifications) and automatically generate Apex actions from them, making external API calls available in flows without code.
Definition
A Salesforce feature that lets admins register third-party REST APIs (via OpenAPI specifications) and automatically generate Apex actions from them, making external API calls available in flows without code.
In plain English
“External Services lets you register a third-party REST API in Salesforce by giving it an OpenAPI spec. Salesforce then auto-generates Apex actions for that API so you can call it from Flows and Process Builder without writing any code.”
Worked example
The admin at Skyway Logistics needs Flow to call the company's chosen shipping-carrier APIs to fetch live tracking events, but doesn't want to write Apex for each of the four carriers in use. She uploads each carrier's OpenAPI specification through External Services in Setup; Salesforce reads each spec and auto-generates a set of named Apex actions ("FedEx_GetTracking," "UPS_GetTracking," and so on). The on-shipment-update Flow now has a "Call External Service" element where the admin picks the carrier action from a dropdown, maps inputs and outputs in Flow Builder, and ships an integration the same week - without ever opening an Apex editor.
Why External Services matters
External Services is a Salesforce feature that lets admins register third-party REST APIs through their OpenAPI specifications and automatically generate Apex actions from them. After registration, the API's operations appear as available actions in Flow Builder and other declarative tools, so admins can call external APIs from Flows without writing Apex code. The platform handles the request building, authentication, and response parsing based on the OpenAPI definition.
External Services democratizes API integration for admin-led teams. Without it, calling a REST API from a Flow required writing custom Apex code, which created a developer dependency for every new integration. With it, admins import the OpenAPI spec, configure the named credential for authentication, and the API becomes available as Flow actions immediately. This is particularly valuable in admin-heavy organizations where developer capacity is limited and integrations should be configurable by admins.
How organizations use External Services
Registered their internal REST APIs through External Services so their admin team can call them from Flows for various automation scenarios without developer involvement.
Uses External Services for third-party API integrations like address verification, calling them from Lead and Contact Flows when records are created.
Trained their admin team to work with OpenAPI specs and External Services so most integration work happens declaratively, freeing developers for harder problems.
Trust & references
Straight from the source - Salesforce's reference material on External Services.
- External ServicesSalesforce Help
- OpenAPI 2.0 and 3.0 SupportSalesforce Help
Test your knowledge
Q1. What does External Services enable?
Q2. What format does External Services use to define APIs?
Q3. What's the value of External Services for admin-led teams?
Discussion
Loading discussion…