For the integration that sends REST commands after retrieving device details, which OmniScript element should be used to perform the REST API call?

For the integration that sends REST commands after retrieving device details, which OmniScript element should be used to perform the REST API call?

• A. REST API Action
• B. DataRaptor Extract Action
• C. HTTP Action
• D. Navigation Action

Answer: (C)

In OmniScript, when you need to reach out to an external REST service after you’ve collected device details, you use the HTTP Action. This element is built specifically to perform HTTP requests, letting you choose the method (GET, POST, PUT, DELETE), specify the endpoint URL (which can incorporate values from the device details), set headers (like Content-Type or Authorization), and include a request body if needed. The response can then be mapped and used by subsequent steps in the script. DataRaptor Extract Action is for pulling data through a DataRaptor, not for making external API calls, and a Navigation Action only changes the flow. There is also a REST API Action in some setups, but the standard, universally supported choice to perform REST calls within OmniScript is the HTTP Action.

In OmniScript, when you need to reach out to an external REST service after you’ve collected device details, you use the HTTP Action. This element is built specifically to perform HTTP requests, letting you choose the method (GET, POST, PUT, DELETE), specify the endpoint URL (which can incorporate values from the device details), set headers (like Content-Type or Authorization), and include a request body if needed. The response can then be mapped and used by subsequent steps in the script. DataRaptor Extract Action is for pulling data through a DataRaptor, not for making external API calls, and a Navigation Action only changes the flow. There is also a REST API Action in some setups, but the standard, universally supported choice to perform REST calls within OmniScript is the HTTP Action.