SFDCWallah

HTTP Callout pulls or sends data (beta) between the Salesforce database and an external system via Flow Builder without using code.

You can set up direct integrations as needed without having to work with a developer or call a middleware tool, such as Mulesoft.

After you configure the HTTP callout action in a flow, Flow Builder auto-generates an external service registration, an invocable action, and Apex class that you can use to create an Apex-defined resource for flows.

You can then use the data output of the API request as input within Flow Builder and across Salesforce.

HTTP Callout Considerations:

• JSON response with fields in a list that have the same data type is supported. For example, [1, 2, 3, 4] is a list of numbers with the same data type. But [“one”, 2, “three”, “four”] doesn’t have the same data type because 2 is a number, and the other values are strings.
• Enum data type isn’t supported. For example, if the API includes a Status field with finite values of Accepted and Rejected, the values don’t appear in Flow Builder as a multi-picklist. The Status field is instead inferred as a string data type and the callout response includes one value.
• Float and long data types aren’t supported. If the API response provided during configuration includes a field with float or long data types, you can set the data type to integer or double.
• Include headers within the named credential when configuring the authentication, which supports global merged fields. Set headers on the URL endpoint for the callout rather than the invocable action.

Limits

• HTTP Callout API requests count toward your org-wide API request limits.
• Every time you create an HTTP callout action within Flow Builder, it auto-generates an external service registration, which counts toward your org-wide External Services registration limit.
• You can have up to 15 nested levels of fields and objects in a JSON hierarchy.

Manage HTTP Callout Actions

When you create an HTTP Callout action in a flow, Flow Builder creates an external service object and an invocable action object. Anyone with permissions in your org can reuse the invocable action in Flow Builder and across Salesforce.

To update flow-specific input values of an HTTP Callout action, edit the respective Action element from the Flow Builder canvas. For example, update a query parameter value from the respective Action element.

• Update an HTTP Callout Action Configuration
  To update the configuration of an HTTP Callout action, edit it from the External Services page in Setup. For example, update a path URL, keys, or a JSON sample. After you create an HTTP Callout action from Flow Builder, you can reuse it in another flow or across Salesforce via Apex, Einstein Bots, or quick actions.
• Change the Named Credential for an HTTP Callout Action
  To select a different named credential for an HTTP Callout action after the action is created, update the action from the External Services page in Setup.
• Delete an HTTP Callout Action
  To delete an HTTP Callout action, you delete the external service registration record. If an external service registration and HTTP Callout action are referenced in any flows, you can’t delete them.