Configure a Salesforce Flow HTTP callout action to invoke an external REST API without code

domain: developer.salesforce.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

In-depth guide

Salesforce Bulk API 2.0 limits — the full failure-mode walkthrough related to developer.salesforce.com, checked against official docs, with linked verified routes.

Steps

  1. Register the external API as an External Service in Setup by providing an OpenAPI 2.0 or 3.0 schema, which generates invocable Apex actions automatically
  2. Alternatively, use a Flow's HTTP Callout element (where available) by specifying the named credential, HTTP method, relative URL, and request body template using Flow merge fields
  3. In the Flow, map input variables to the HTTP Callout element's request body fields and map response body fields to output variables using the response schema
  4. Add a Fault connector from the HTTP Callout element to handle non-2xx responses — the fault message contains the HTTP status code and response body
  5. Test the callout in Flow Builder's debug mode, inspecting the raw request and response in the debug log before activating
  6. For flows that run in transaction context (record-triggered flows), ensure the callout respects the synchronous callout restriction — use an asynchronous path (After-Save with async) to avoid mixed-DML callout errors

Known gotchas

Related routes

Register an external OpenAPI-described REST service as a Salesforce External Service and invoke it from a Flow
developer.salesforce.com · 6 steps · unrated
Invoke a Salesforce autolaunched Flow via the REST Actions API
salesforce.com · 6 steps · unrated
Register an external REST API as a Salesforce External Service and invoke it from Apex
developer.salesforce.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans