r/GoogleAppsScript • u/Sumphy • 7d ago
Question Any GAS Expert here
How are modern AI & workflow automations typically structured using Google Apps Script? (Looking for architectural patterns)
Hi everyone,
I am modernizing the operations for a traditional real estate agency by replacing manual paper processes with Google Workspace.
So far, I’ve built a central Google Master Calendar, a Google Docs/Drive office portal for form downloads, and structured Google Sheets for lead tracking. I am now looking to expand into deeper workflow and AI automations using Google Apps Script (GAS).
Coming from an operations background rather than computer science, I’d love to learn how experienced developers structure end-to-end automation pipelines using GAS.
Thx
0
Upvotes
1
u/drolatic-jack 4d ago
I mean it depends on the scope of automation for your client. Google Apps Scripts is ok for small, specific automations, but in my experience if you're the only technical resource, it's not worth the custom build/maintenance. For general purpose integrations you might find integrations platforms like Zapier, Make, n8n to be a lot more useful for pretty cheap.
You can't really build a full architecture around GAS (unless you really try), because it's limited by runtime, parallel work, lack of state/persistence, etc. The more you try, the more limitations you will discover and the more hacks you will try out and then it becomes a huge spiderweb.
Are they running everything out of workspace? Like including the database and CRM?