Salesforce setup
Overview
Section titled “Overview”The goal is for your team to own the integration: secrets in Named Credentials, contracts in External Services, logic in Flow.
Step 1 — Named Credential
Section titled “Step 1 — Named Credential”- Create a Named Credential with the API base URL from your license materials.
- Configure authentication to send the ApiKey header (custom header on the credential or linked External Credential).
- Test with a simple GET from Apex or Workbench-style tooling before wiring Flow.
Step 2 — External Service
Section titled “Step 2 — External Service”- Import the OpenAPI spec for your target service (OpenAPI import).
- Complete the import wizard and note the generated operation name.
Step 3 — Flow callout
Section titled “Step 3 — Flow callout”- Add an Action using the imported External Service operation.
- Pass lat, long, and service from record fields or formulas.
- Store outputs in Flow variables; branch on
status/ response code when present.
Common pitfalls
Section titled “Common pitfalls”| Issue | What to check |
|---|---|
| Duplicate URL segments | Named Credential base URL + External Service path may double up—leave path prefix on only one side |
| HTML instead of JSON | Wrong host, missing ApiKey, or blocked callout—see Troubleshooting |
| Empty properties | Coordinates outside layer extent; wrong service name; lat/long swapped |
Example debug output
Section titled “Example debug output”Flow debug may show inputs like lat, long, service, sType (e.g. near) and a responseCode of 200 with populated properties when the lookup succeeds. Exact field names follow your imported schema.
Need help? Contact support.