Response Actions are interceptors that allow you to customise the way responses are handled.
By default, a successful request is determined by the response HTTP Code being in the info (1xx) or success (2xx) ranges and anything outside of these is treated as a request failure.
Sometimes, an API will return a response that needs to be treated differently to how it would normally be handled. For example, an API might return a 400 error to indicate a part of the request contains invalid data. We can use a response action to catch that error and do something about it.
The Response Action executes the following steps:
- 1.Run retry logic. Retry logic takes precedence and will cancel the Response Action if possible. If no more retries can be made (or no retry is required), the Response Action is executed.
- 2.If no retry error has occurred, the request and transaction states are updated according to the Response Action.
- 3.Notify the user by adding an integration note. A note will only be added according to the notification script on the Integration.
- 4.If a script is specified, execute the script.
The Details fields that can be configured for the Response Action record are as follows:
The Settings fields that can be configured for the Response Action record are as follows:
The Active field can be configured for the Response Action record as follows: