a zap or an n8n flow enumerates its entire action set when you build it. every branch, every write, every field mapping is fixed before it runs once, so the authorization decision happens at design time and the runtime is just replay. that's why nobody asks who's accountable for a zap. whoever wired it is. an agent picks its action set at call time. there is no build-time moment where "write this to hubspot" or "send this from gmail" exists as an object you can approve. so ...