Adding a dedicated service for a complex step in the processes

Let’s take as an example a functional feature that we have talked about previously (in this chapter and Chapter 13 as well) named “validation” or “middle office.” The goal of such a service is to interrupt a process until someone authorized has provided an agreement, after human analysis, that the flow can go on. Such an interaction could also lead to a decision with different possible choices, each of them switching the process to a given lane of tasks. In Enterprise Integration Pattern terms, a middle office is a content-based router brick. However, it would not be possible to provide business rules to route the message. A human decision would be required to replace those rules.

Of course, in simple cases, we could provide such a feature with n8n. We saw earlier how a Wait task could handle this kind of behavior. But some difficulties may arise. First, this kind of validation is needed...