How to Use Google Workspace Studio: 3 Steps to Full Automation Without Writing a Single Line of GAS Code

I have stopped writing even a single line of code to automate my tasks.

Right now, in my Workspace, the moment an email arrives, the content is extracted, recorded in a sheet, and a notification is sent to Chat. The number of lines of code written: zero. I only set one starting condition and three steps.

You search for "business automation," open an article on Google Apps Script—commonly known as GAS—and by the third line, code appears, and you quietly close the tab. That slight sense of defeat.

I understand that feeling very well. The idea that you can't automate because you can't write code.

However, automation has now changed from "something you write" to "something where you choose one starting condition."

Today, I will show you how to use Google Workspace Studio to automate tasks without writing a single line of GAS code. I will reveal everything from demonstrations and copy-paste prompts to the pitfalls explicitly stated by Google. Let's begin.

Chapter 1: Why Do People Stop at "I Can't Write GAS = Automation is Impossible"?

I'll say it clearly: the reason you stop isn't ability. It's just three misconceptions.

Misconception ①: Automation means writing code

When people think of Google Workspace automation, they think of GAS. This imprint is so strong that the moment you think "I want to automate," a programming wall rises in your mind. But the entrance has already moved to a place without code.

Misconception ②: No-code has its limits anyway

This is the part I want to overturn most in this article. GAS also has official limits. One execution is up to 6 minutes. Triggers are up to 20 per script. Total trigger execution time is up to 6 hours per day for a Workspace account.

The idea that you can do anything infinitely if you write code is an illusion. Limits exist for both. The only difference is where they are placed.

Misconception ③: It's only for me. It won't spread within the company

The automation you create can be distributed via a copy link. The recipient copies it to their own environment, so there's no worry about them seeing your execution history.

What's stopping you isn't a technical wall, but the design of the entrance. Next, I'll talk about that entrance.

Chapter 2: The Essence is "Choosing One Starting Condition," Not "Writing Code"

The answer is surprisingly simple. Stop writing and start choosing.

Google Workspace Studio is Google's no-code automation tool. Official rollout began in December 2025, and it supported the Japanese UI from May 7, 2026. If you have an eligible Business, Enterprise, or Education edition, it's included in your contract at no extra cost.

The structure consists of only two parts: "Starting Conditions" and "Steps."

A starting condition is the trigger that starts the flow. When an email is received, every Friday at 5:00 PM, or when a meeting transcript is generated. You set only one per flow.

Steps are the subsequent processes. Summarizing, extracting, determining true/false, or adding a row. You can stack up to 20 steps per flow.

You might think, "Can business really run on just that?" I'll show you in the next chapter.

Chapter 3: Demonstration. Comparing the Same Automation in GAS and Studio

Since words alone are hard to convey, I'll actually line them up. The subject is "When an invoice email arrives, record the amount and client in a sheet."

[When creating with GAS]

Open the script editor. Write code to fetch emails. Write logic to extract the amount and client name. Add a row to the sheet. Set a trigger. Clear permission approvals. If the volume increases, rewrite the code to split processing to avoid the 6-minute wall.

—This is correct. But before getting this far, most people close the tab at the third line.

[When creating with Workspace Studio]

Starting Condition: Upon receiving an email (filter by sender or subject)

Step 1: Extract (retrieve date, client name, and amount)

Step 2: Add row (record in Spreadsheet)

That's it. There is not a single line of code.

Same automation, same Google service. The only difference is whether you "wrote" the process or "chose" it.

You understand the mechanism. Next is the actual procedure.

Chapter 4: Practical Steps and Copy-Paste Prompts

No programming is required at all. Don't be intimidated. Your first flow will be running in 10 minutes.

STEP 1: Open [studio.workspace.google.com](https://studio.workspace.google.com/) in a PC browser

A computer is required to create flows (running them on a smartphone is fine). If you can't open it, check with your administrator to see if Gemini is enabled.

STEP 2: Write what you want to do in plain Japanese (or English)

Studio has an entry point where Gemini builds the flow if you explain it in text. Paste this there:

1Please create a flow that executes the following steps in order when an email is received from "(sender's email address)":
2① Extract candidates for date, client name, amount, and account item from the email body and attachments.
3② Add the extracted content as a single row to the spreadsheet "Expense Records."
4③ If there are items that cannot be read, write "Requires Confirmation."

Please replace "(sender's email address)" with the actual address. Once the skeleton is out, just make fine adjustments on the screen.

STEP 3: Use the "Decision" step to let AI handle one human judgment

Studio has a "Decision" step where Gemini determines true or false. By writing conditions, you can branch the flow based on the result.

1Is this email regarding an invoice or receipt that requires accounting processing?
2If it contains an amount and requests payment or billing, judge as true; otherwise, judge as false.
3If unsure, judge as false so a human can check in the subsequent notification step.

If in doubt, false. This one sentence significantly reduces erroneous records that you'd regret later.

With this, your first flow is running. Next is the honest truth.

Chapter 5: To Be Honest, Studio Has Its Limits

I won't end by writing only the good parts. I'll share the limits explicitly stated by Google.

Limit ①: The flow will fail unless the file is "Private"

This is the biggest pitfall. If you use shared drives, shared folders, or sheets containing the IMPORTRANGE function, the flow will fail. Even if a sheet worked at first, it will stop the moment you share it later. A design that "collects data in a sheet shared by everyone" currently won't pass.

Limit ②: Up to 25 flows, up to 20 steps

You can create a maximum of 25 flows. Active flows triggered by Gmail reception must also be within 25. There is also a limit on the number of daily executions.

Limit ③: Cannot filter by custom Gmail labels

Only default Gmail labels can be used for starting condition filters. You cannot specify labels you created yourself.

Therefore, GAS is not dead. Tasks involving shared drives, complex conditional branching, or full-scale integration with external services remain the domain of code.

However, what most people really want to automate isn't that. Sorting morning emails. Turning meeting notes into tasks. Preparing routine reports. These kinds of repetitive tasks can be handled with one starting condition and three steps.

Summary: Not being able to write code is no longer an excuse

This time, I explained how to automate tasks without writing a single line of GAS code, from the structure of misconceptions to demonstrations and limits. What I want to convey at the end is simple.

Automation is no longer a privilege only for those who can program. What you need is not code, but the judgment to decide "from which moment do I want this to start moving."

I believe AI is a weapon for those who don't have much to stage a comeback. Regardless of educational background or skills, you can hold the same weapon starting today. There's no reason not to get on board.

That said, you don't need to make 25 flows all at once. Just do one thing.

Choose the one routine task you find most tedious right now and set its starting condition.

You don't need to learn everything from 1 to 10 before starting. Once you experience the feeling of "it moved on its own just because I set it up," you'll never be able to go back to manual work.

Google Workspace Studio and Gemini are evolving incredibly fast. Rather than trying to keep up with the latest on your own, it's overwhelmingly faster to learn from those who are practicing it.

Thank you for watching until the end.

[📣 Notice 📣]

I will be holding a seminar demonstrating how to write "X Articles" that changed my life.

I started X operations in April 2025, and for the first four months, my follower count only increased by 139. After that, I struggled for 11 months without much growth.

However, in the 12th month, starting from March 15, 2026, when I began publishing "X Articles," my follower count increased by 6,609 in just two weeks from March 15 to March 31.

From there, my life changed completely:

❶ X creator revenue over 300,000 yen every month

❷ Multiple requests for X operation consulting

❸ Multiple requests for AI consulting

❹ Requests to appear on TV programs

❺ Requests for book publishing... etc.

Various jobs came pouring in, and my life was transformed by "X Articles."

I will conduct a seminar on how to write such "X Articles" in a demonstration format. I will share my computer screen and explain exactly how I write them.

Also, I have prepared a huge limited gift for the seminar.

📣 July 17, 20:00–22:00 Held on Google Meet 📣

Even if it's difficult to adjust your schedule, there will be an archive, so please join us.

Date: July 17 (Friday) 20:00–22:00 Venue: Google Meet (with archive)

Apply here.

[Seminar Application]

https://aisalon-260717.peatix.com/

*Please make sure to use the official LINE limited coupon below.

On the official LINE, we will distribute limited information and benefits in the future.

[Official LINE]

https://lin.ee/O3GM1P1

[Official LINE ID]

@691cuilm

[note]

https://note.com/hoshino0614/n/n4b3a9dedfa5f?sub_rt=share_pw