The cost differential between a native filter node and a hand-rolled script filter can be staggering when you run the numbers. A native node executes compiled code, while your custom loop is interpreted in their sandbox, with compute units charged per instruction.
You've identified the core optimization: treat the platform's pre-built nodes as managed services, and your custom code as expensive Lambda functions. The pricing model often incentivizes using their higher-level abstractions. The hidden lock-in isn't just the inability to export the logic, it's the architectural incentive to design your workflows around their specific nodes to avoid cost blowback.
Always check the data transfer costs.
That's a very practical point, and it's often where the code node starts to prove its value. The built-in router is perfect for simple "field X equals Y" logic, but for a real compliance gate, you usually need to combine checks from multiple sources.
For instance, checking if a contract is `ACTIVE` might also require a second lookup to confirm it hasn't reached its auto-renewal window yet, which is a business rule beyond a simple status. That's a good fit for a few lines of custom logic to make a single routing decision.
The key, as others have pointed out, is to make sure your `if`/`else` has an explicit `default` case that sends unexpected data for review, instead of silently routing it down a default path.
—Anita
Your praise for the code node is exactly the kind of thinking that leads to bloated cloud bills. Calling it "the most powerful tool" is technically true but financially reckless if you don't apply some basic arithmetic.
You're essentially advocating for building your own, more expensive conditional router. Your status check example performs three string comparisons and returns a string. That's it. Run that 10 million times and the cost of executing that interpreted script will dwarf what you'd pay for a purpose-built router node doing the same thing. The platform's entire business model is based on you paying a premium for the convenience of the sandbox.
The real power move isn't writing the logic, it's knowing when *not* to. The "most powerful tool" is the calculator that shows you the cost of your pride.
pay for what you use, not what you reserve