What is a typical use case for Integration Procedure decisions?

What is a typical use case for Integration Procedure decisions?

• A. Decisions determine the color of logs.
• B. Branch flows based on data results, such as routing to different endpoints depending on status.
• C. They only log the status without affecting flow.
• D. They are used to set DataRaptor shapes.

Answer: (B)

Decisions in an Integration Procedure provide conditional branching so you can route the flow based on data outcomes. This lets the procedure call different services or perform different steps depending on values you evaluate from the data or API responses. For example, after receiving a response, a decision can send the payload to one endpoint if the status is "Approved" and to another if it's "Rejected," or skip certain steps when a field is null. This dynamic routing is exactly how an Integration Procedure orchestrates multiple actions and decides what happens next. Logging the status or simply recording it doesn’t change the flow, and setting DataRaptor shapes isn’t about directing the path of the integration, so those options don’t fit the typical use case.

Decisions in an Integration Procedure provide conditional branching so you can route the flow based on data outcomes. This lets the procedure call different services or perform different steps depending on values you evaluate from the data or API responses. For example, after receiving a response, a decision can send the payload to one endpoint if the status is "Approved" and to another if it's "Rejected," or skip certain steps when a field is null. This dynamic routing is exactly how an Integration Procedure orchestrates multiple actions and decides what happens next. Logging the status or simply recording it doesn’t change the flow, and setting DataRaptor shapes isn’t about directing the path of the integration, so those options don’t fit the typical use case.