Google Forms To Queue Item

Very good question, thank you.

This is a design decision mainly motivated by security: when the component was developed a year ago, the only configuration possible was to pass on all the permissions of the Orchestrator user to the integration. This was way too much power stored on the "client" end (app scripts) so instead we interface with a dedicated, specialized, and secure endpoint. It also helps that a serverless function is just stateful enough to cache its access token and be able to handle many requests per seconds (if need be)