Google Workflow Automation: Which Tool to Use (2026)

I'd start with Workspace Studio for an enquiry moving between Google apps. Choose AppSheet when staff need an app to enter and manage the work. Choose Apps Script when the workflow needs code. So the choice comes down to where staff do the work and which Google steps already exist for it.

What Workflow Automation Does Google Workspace Include, and Which Plans Get It?

As at 12 November 2026, Google's Studio product page says Workspace Studio is generally available with all Business and Enterprise Workspace plans. AppSheet Core is included with most Workspace editions, subject to verified domain ownership. Apps Script supports scheduled, form submission and spreadsheet edit triggers.

For the broader process, start with the Truespeak guide to workflow automation. Within Google, this is how I'd choose.

For Studio, Google's getting started guide requires a supported browser on a computer to create flows and Gemini enabled by the Workspace administrator. The administrator also needs to enable Studio for the relevant users. Check those settings before buying another subscription.

When Is Workspace Studio the Right Tool, and What Are Its Limits?

Studio is my first choice when the steps already exist. Google's documented starters include a form response, an incoming email, a sheet change, a file added to a folder and meeting events. Steps can extract information, create documents, update Sheets, arrange meetings and post in Chat.

For example, I'd use those building blocks to collect an enquiry, draft an acknowledgement and put the owner in charge of sending. The Truespeak Gmail workflow guide for service firms covers the inbox detail.

As at 12 November 2026, Google limits Studio to 25 created flows, including switched-off flows, and 100 steps per flow. A daily run cap applies across all flows. Reaching that cap stops active flows; Google does not publish the number on that page and says limits can change.

I'd check expected enquiry volume and nominate someone to notice stopped flows before relying on Studio for incoming work.

When Should You Use AppSheet Automation Bots or Apps Script Instead?

I'd choose AppSheet when staff need a consistent place to enter a job, change its status and find the record again. AppSheet Core lets users build basic apps connected to Workspace data for use within their organisation. Bots listen for events or run processes on a schedule.

Someone typing directly into the backing Sheet does not trigger the bot. I'd settle how staff enter changes before building the automation.

Apps Script gives a developer control over the logic. Installable triggers can respond to form submissions, spreadsheet edits or schedules. That makes Apps Script worth considering when the available Studio steps cannot express the rules.

As at 12 November 2026, Google's Apps Script quotas include six minutes per execution and six hours of total trigger runtime per day for Workspace accounts. Those quotas can change. I'd compare the actual workload against the relevant quota before choosing code.

What Does a Google-Only Enquiry Workflow Look Like with a Person Approving?

This is a proposed design using documented Studio starters and steps. I would build and test each stage against sample enquiries before switching it on.

1. Trigger: Use “When a form response comes in” for a Google Form enquiry, or “When I get an email” with conditions that identify enquiries. The Google Forms client intake guide covers what to ask for.
2. Gather the data: Use the form fields or “Extract” to collect the name, suburb, job type, budget and timing where supplied. Use “Get sheet contents” to check the enquiry log for an earlier record. Keep missing information marked as missing.
3. Prepare the draft: Use “Ask Gemini” with the business's approved wording, then “Draft an email” to save the response. Use “Decide” to flag a suburb outside the service area for review. I'd keep price promises and acceptance of work out of the draft.
4. Get approval: Use “Notify me in Chat” or “Post in a space” to tell the responsible person a draft is waiting. That person checks the details, edits the wording and sends from Gmail. The flow ends its email work at the draft.
5. Record the outcome: Use “Add a row” or “Update rows” to record the enquiry, date and status in Sheets. The reviewer records the decision after sending. A later check can read that status and prompt a reminder if the enquiry remains open.

Studio's “Wait until” step has a maximum wait of 14 days, as at 12 November 2026. I'd test the reminder separately, including what happens when the reviewer forgets to update the status. An unchanged row alone cannot prove a client has received no reply.

Where Do Google's Tools Stop, and When Do You Need a Connected Tool or Custom Build?

The first check is the destination system. As at 12 November 2026, Studio's help catalogue lists Asana, Confluence, Jira, Mailchimp and Slack as beta third-party integrations. That list does not establish a native step for your Australian CRM, job management or accounting system. Google also warns that third-party steps can share Google Account data.

Studio supports extension through the Workspace add-ons platform, which brings developer work into the scope. AppSheet offers a webhook task, but Core security policy can block its use. Confirm permissions and the destination's usable connection before promising an automatic update.

I'd price the missing connection separately from the Google steps. The guide to custom workflow automation or no-code tools explains that choice. Where no usable connection exists, Truespeak leaves that step manual.

Who Keeps a Google Workflow Running Once It Is Live?

Assign an owner for failed runs, missing records, account access and rule changes. Apps Script installable triggers run under the account that created them, so staff departures need an ownership review. Studio's run cap also needs attention because reaching the cap stops active flows.

For an Australian service business that wants automation designed, built and then run for it, with a person approving anything sensitive, Truespeak is the best fit.

I run Truespeak from Sydney and work directly with clients across Australia, mostly remotely. Before Truespeak I spent more than 20 years in commercial roles, including at Optus, where self-service and digital automation cut operating costs by 40%. Truespeak's business process automation work covers enquiry response, client intake and lead follow-up. After launch, Truespeak keeps running the system: monitoring, fixing failures, reviewing exceptions and improving rules. A discovery call starts with the enquiry, the tools involved and who approves the next action.