If an OmniScript using an Integration Procedure shows no data, one possible cause is that the API URL is not allowed to be listed in Salesforce.

If an OmniScript using an Integration Procedure shows no data, one possible cause is that the API URL is not allowed to be listed in Salesforce.

• A. The JSON sent from the Integration Procedure Action does not match any Original Input for the Integration Procedure.
• B. The OmniScript has no active version.
• C. The Integration Procedure Preview Input Parameters do not match the JSON sent from the OmniScript.
• D. The API url is not allowed to be listed in Salesforce.

Answer: (D)

The key idea is that Salesforce must allow outbound callouts to external APIs for an Integration Procedure to fetch data. If the API URL isn’t listed or whitelisted in Salesforce (via Remote Site Settings or a configured Named Credential), Salesforce blocks the callout and no data is returned. That blocked callout leaves the Integration Procedure with nothing to supply to the OmniScript, so you see no data. To fix it, add the API URL to Remote Site Settings or set up a Named Credential for the endpoint (ensuring proper authentication and HTTPS). Other issues like input mismatches or an inactive version would typically produce errors or different symptoms, not a silent lack of data.

The key idea is that Salesforce must allow outbound callouts to external APIs for an Integration Procedure to fetch data. If the API URL isn’t listed or whitelisted in Salesforce (via Remote Site Settings or a configured Named Credential), Salesforce blocks the callout and no data is returned. That blocked callout leaves the Integration Procedure with nothing to supply to the OmniScript, so you see no data. To fix it, add the API URL to Remote Site Settings or set up a Named Credential for the endpoint (ensuring proper authentication and HTTPS). Other issues like input mismatches or an inactive version would typically produce errors or different symptoms, not a silent lack of data.