Salesforce External Services: Calling Any REST API From Flow Without Code (2026)
Import an OpenAPI spec, wire up a Named Credential, and call any external API from Flow or an Agentforce action. No Apex required. Here is how.
You open Flow Builder, realize you need to call a shipping-rate API every time an Order closes, and brace yourself for an afternoon of Apex callouts, JSON parsing, and a wrapper class you will have to [[unit](/t
erms/unit) test](/terms/unit-test) before it goes anywhere near production. Then someone on your team mentions External Services. Twenty minutes later you have a typed, invocable action sitting in the Flow palette that calls that API, and you wrote zero lines of code.
Share this article
Sources
Related dictionary terms
Keep reading
Salesforce Integration Patterns: REST vs SOAP vs Bulk vs Composite vs GraphQL (2026 Reference)
The complete 2026 reference for Salesforce APIs - REST, SOAP, Bulk 2.0, Composite, GraphQL, Pub/Sub, Streaming, Metadata, Tooling. When to use each, rate limits, OAuth flows, and patterns.
Building Custom Agentforce Actions: Apex, Flow, and Prompt Templates Explained
Standard Agentforce actions only go so far. Here's how to build custom Apex actions, Flow-based actions, and Prompt Template actions that give your agents real org-specific capabilities.
Salesforce Flow vs Apex in 2026: A Decision Matrix for Admins, Developers & Consultants
Flow vs Apex is not a religious war anymore. Here is the 2026 decision matrix. Capability gaps, governor limits, the 70/30 rule, and 12 worked scenarios with the right answer for each.
Salesforce Named Credentials and External Credentials: The Complete 2026 Guide
Legacy Named Credentials are retiring. The new split between Named Credentials and External Credentials is how Salesforce expects every integration to authenticate in 2026. Here is what changed and how to migrate.
Comments
No comments yet. Start the conversation.
Sign in to join the discussion. Your account works across every page.