Gorgos and n8n: which layer does what
The question n8n or Gorgos is the wrong one. The right one is: who executes the step, and who decides whether it may be executed.
What does n8n do?
It connects systems and runs a flow: fetch, transform, send. It has approval nodes that can hold a flow for a human decision. It is proven, widely used, and usually the default in Polish deployments.
Approval inside a flow works within that flow. Whoever designed it decides where the gate stands.
What does n8n not do, by design?
It does not answer the question asked across all flows: may this class of action execute without a signature at all, regardless of which flow triggered it.
With one flow that does not matter. With thirty, built by different people over a year, a rule written separately into each stops being a rule.
What does it look like together?
n8n executes the step and asks the gate whether it may. The gate reads one policy and answers yes, no, or only after a signature. The answer and its basis land in the decision ledger.
The practical effect: adding the thirty-first flow does not require remembering the rules from the previous thirty.
n8n does the work. The policy decides what may be done alone. Trading one for the other makes no sense.
When do you not need Gorgos?
When your automations are internal and reversible, and everything that leaves the company passes one person anyway. The gate already exists then, and it has that person's name.
Gorgos starts to earn its place when that person can no longer sit at every decision, and the list of things happening on their own no longer fits in one head.