HTTP Action requests, responses and failure handling
What goes into and comes out of an Integration Procedure HTTP Action: methods, parameters, headers and body, Send and Response JSON paths, XML replies, timeouts, retries, Try-Catch Blocks and Failure Conditional Formulas, and how it differs from the Omniscript HTTP Action.
Explain, dependent upon customer use case, the configuration and management of HTTP Actions within an integration procedure to securely connect to and process data from external REST/SOAP endpoints, including authentication and request/response mapping.
~8 min read · 12 practice questions ·
What the exam expects
- Describe how a request is built: method, Request URL, REST Options params and headers (content-type and charset) and Request Body.
- Recommend a Transform plus Send JSON Path to send only what a partner needs, and Response JSON Path to keep only what later steps need.
- Handle XML replies with a Transform and Escape XML Response; the action makes REST calls only.
- Match failure symptoms to Timeout, Retry Count, a Try-Catch Block or a Failure Conditional Formula, and use Pre-Action logging in Preview.
- Compare the Integration Procedure HTTP Action with the Omniscript HTTP Action.
Key terms: Send JSON Path / Response JSON Path (trim the JSON going into, or coming out of, a step); Failure Response (key-value pairs added to the output when a step or block fails); Failure Conditional Formula (a custom failure test that runs after the step); Try-Catch Block (a block that catches a failing step and returns a response); Retry Count (number of times to retry a failed action).
Key facts
- Detail
- GET, POST, PUT, PATCH, DELETE
- Detail
- text/plain; charset=ISO-8859-1; key content-type is lowercase
- Detail
- Times to retry the action when it fails
- Detail
- Trims incoming JSON before the action runs
- Detail
- Trims output JSON after the action runs
- Detail
- TRUE marks the step failed and adds Failure Response pairs
- Detail
- Fail on Block Error on the block; Fail on Step Error on catching steps
- Detail
- Data Mappers take XML input; Escape XML Response removes escapes
- Detail
- Needs a trusted URL with all CSP directives
Sources for this section (5)
- HTTP Action for Integration Procedureshelp.salesforce.com (opens in a new tab)
- Integration Procedure Actionshelp.salesforce.com (opens in a new tab)
- Handle Errors by Using a Try-Catch Blockhelp.salesforce.com (opens in a new tab)
- XML and JSON in Omnistudio Data Mappershelp.salesforce.com (opens in a new tab)
- Calling Web Services with the Omniscripts HTTP Actionhelp.salesforce.com (opens in a new tab)
- Why does raising Retry Count not help a partner API that is consistently slow?
- When should a consultant add a Failure Conditional Formula to an HTTP Action?
- Why put a Data Mapper Transform after an HTTP Action whose partner replies in XML?
- Which property passes only one node of a large reply to later steps?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Omnistudio Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 31 lessons of the Omnistudio Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (12 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams