Salesforce Docs Portal

HTTP Action (Managed Package)

For the managed package runtime, call internal and external web services from Omniscript without coding or making Salesforce API calls using the HTTP Action.

Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

Note
Note

In an LWC Omniscript, to use an HTTP Action that calls Apex, you must add the Salesforce org's domain into a Remote Site's Remote Site URL field. For more information, see Adding Remote Site Settings.

To make an external call with an HTTP Action:

Use the HTTP Action to:

  • Send GET, POST, PUT, or DELETE requests to standard REST Endpoints.

  • Call Apex REST.

  • Access Salesforce Named Credential (OAuth) identity services.

Settings:

  • HTTP Path: The request URL of the API. For example, /NS/v1/application. NS = namespace of the Apex REST API. The path can contain merge fields. For example, to pass a UserId node from the data JSON, add the node name with percentage signs on either side, i.e., %UserId%.

    Note
    Note

    Beginning with Vlocity Summer '19, you can pass percentage signs in the URL by replacing the percentage sign in the URL with the variable $Vlocity.Percent.

  • HTTP Method: The method name, which has two parameters. For example, doPost(String fullJSON, String filesMap).

  • Option Source: The type of HTTP Action.

  • Use Named Credentials (OAuth via Salesforce).

  • SOAP/XML (Simple Object Access Protocol)

  • Web (Unauthenticated or Credentials in Header)

  • Remote Timeout: The timeout for the request, in milliseconds. Defaults to 30,000 (30 seconds. Maximum 12,0000 (120 seconds).

  • Pre- and Post-Transform Data Mapper Interface: (Optional) Omnistudio Data Mapper Transform interface to run before or after the REST Action.

Prior to Summer '17, the HTTP Action was known as the REST Action.