1. REST vs SOAP — which one do you pick, and why?
“The upstream vendor supports both REST and SOAP. Which do you wire into IntegrationHub, and how do you justify it in the review?”
How to answer
- REST is stateless, uses JSON, and maps cleanly to IntegrationHub REST Steps — lower payload, easier to debug in the outbound REST message logs.
- SOAP is contract-first (WSDL), heavier payload, and better when the vendor mandates WS-Security or strict schemas.
- In ServiceNow, prefer REST for modern SaaS integrations (Jira, Slack, GitHub) and reserve SOAP for legacy on-prem (SAP, Oracle EBS, older ITSM).
- Either way, wrap the call in a Subflow with an Action step so error handling and retries live outside the raw HTTP step.
Reference script
// REST Message — outbound to Jira
var r = new sn_ws.RESTMessageV2('Jira Cloud', 'createIssue');
r.setStringParameterNoEscape('summary', current.short_description);
r.setRequestHeader('Content-Type','application/json');
var resp = r.execute();
var status = resp.getStatusCode(); // 201 = created
var body = resp.getBody(); // { "id":"10231", "key":"OPS-42" }
if (status !== 201) {
gs.error('[Jira] create failed ' + status + ' ' + body);
}Pitfall
Don't call RESTMessageV2 straight from a Business Rule — a slow vendor blocks the transaction. Push the call into an async Subflow or an Event so the record save returns instantly.