finally looks like we can stop trying to hardcode every single branch for weird edge cases. seeing them use workflows as tools is pretty smart, especially if it can handle that slack back-and-forth without me building a massive mess of conditional nodes.
>The next step depends on the answer to the last one, so there's no way to lay out the process in advance.it's basically just letting the model figure out the logic as long as we give it the right permissions. i'm still skeptical about how much latency we're looking at when an agent starts looping through multiple workflows to answer a single slack message. might be too slow for anything real-time. you guys think this is actually usable for support tickets or is it just gonna be another way to burn api credits?
more here:
https://blog.n8n.io/introducing-n8n-agents/