Loading
Extend Salesforce with Clicks, Not Code
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          View an Action’s Unique Apex Name

          View an Action’s Unique Apex Name

          Use this example to understand how External Services actions in Apex or Flow map to specific actions in an External Service registration. An object’s unique Apex class name is specified in View Actions > More Details. This name also appears when searching for actions in Flow Builder.

          Required Editions

          Available in: Lightning Experience
          Available in: Enterprise, Performance, Unlimited, and Developer Editions

          For example, if your API spec defines a response accountDetails for a getAccount operation, referenced in the spec as

          "paths": {
                  "/accounts/{accountName}": {
                      "get": {
                          "operationId": "getAccount",
                          "summary": "Retrieves an account",
                          "description": "Retrieves the account with specific name",
                          "consumes": [
                              "text/plain"
                          ],
                          "produces": [
                              "application/json"
                          ],
                          "parameters": [
                              {
                                  "name": "accountName",
                                  "in": "path",
                                  "required": true,
                                  "type": "string",
                                  "description": "Name of the account"
                              }
                          ],
                          "responses": {
                              "200": {
                                  "description": "The response when system finds an account with given name",
                                  "schema": {
                                      "$ref": "#/definitions/accountDetails"
                                  }
          

          Where the definition for accountDetails is defined at the end of the spec as

          "definitions": {
                  "accountDetails": {
                      "required": [
                          "id",
                          "name",
                          "type",
                          "availableBal"
                      ],
                      "properties": {
                          "id": {
                              "type": "string",
                              "description": "id"
                          },
                          "name": {
                              "type": "string",
                              "description": "name"
                          },
                          "type": {
                              "type": "string",
                              "description": "type"
                          },
                          "availableBal": {
                              "type": "string",
                              "description": "availableBal"
                          }
                      }
                  },
          

          When the spec is registered in External Services, you can see the Apex Class name during registration.

          edit an external service

          Or you can navigate to the action in External Services and then click View Actions > More Details.

          external service actions

          External Services automatically registered our accountDetails object as BankService_accountDetails.

          Now in Flow, when you add a resource for a new action, it’s clear that you’re selecting the correct action from the correct registration.

           
          Loading
          Salesforce Help | Article