← Back to library

Draft follow-ups for new leads in your Google Sheet

Aryan Irani shows a no-code Google Workspace Studio flow that filters a lead-tracker sheet to rows marked New, loops over them, has Gemini write a short personal email for each, saves it as a Gmail draft, logs it, flips the status to Contacted and posts one neutral update to a team Chat space.

  • OutcomeEach weekday morning, every lead marked New in your sheet gets a personal email waiting in Gmail Drafts, a line in an outreach log and a status change, so no one is emailed twice.
  • SetupUnder an hour
  • LevelStarter
  • CreditAryan Irani
View original
Works with
Gemini

Published Oct 22, 2026Updated Oct 22, 2026AI dry run on sample input: passed Oct 22, 2026Source verified Oct 23, 2026

When should you use it?

  • Leads from forms, webinars or referrals land in a Google Sheet and someone writes the first follow-up by hand
  • You want every new lead answered the same morning without hiring help
  • You would rather review drafts than let a tool send email for you

Not for: Bulk cold outreach to purchased lists; Teams whose leads live in a CRM with its own sequences; use that tool instead

What do you need, and what do you get?

You need

  • A Google Sheet with a Leads tab (ID, first and last name, company, role, email, source, interest, status, notes, date added) and an Outreach Log tab
  • Google Workspace with Workspace Studio and Gemini
  • Your name and a one-line description of what you offer
  • A Google Chat space for the team update (optional)

You get

  • One Gmail draft per new lead with a fixed subject pattern you can search
  • A log row per draft with the lead ID and a timestamp
  • Each processed lead switched from New to Contacted
  • A single morning note in Chat that stays accurate even on days with no leads

How does it work, step by step?

  1. Set up the sheetAdd the two tabs and keep the status column to three fixed values so the filter can rely on it.
  2. Schedule and filterStart the flow on a weekday schedule and use Workspace Studio's sheet step to pull only rows whose status is New; let the filter do this, not Gemini.
  3. Loop and writeAdd a repeat-for-each step over the matching rows; inside it, an Ask Gemini step with the prompt below writes only the body of the email.
  4. Draft, log and markStill inside the loop, create a Gmail draft with a standard subject that includes the company, add a row to the log, and update that lead's status to Contacted by matching on the lead ID.
  5. Report and reviewAfter the loop, post one plainly worded message to the team space. Test-run it, read several drafts, then run it again to confirm nothing is drafted twice.

The prompt

The original prompt by Aryan Irani, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Gemini. Values in lime are placeholders.

Original prompt by Aryan Irani

Word for wordby Aryan Irani
You are writing a follow-up email on behalf of [YOUR NAME], an automation consultant who helps teams automate their work with Google Workspace Studio.
Write a short, personalized outreach email to this lead: - Name: {{First Name}} {{Last Name}} - Company: {{Company}} - Role: {{Role}} - What they're interested in: {{Interest}} - Context notes: {{Notes}}
Rules: - 90–120 words, plain conversational English, no buzzwords, no exclamation marks. - Begin with "Hi {{First Name}}," — first name only, never the full name, and never skip the greeting. - Then open by referencing their specific interest and context — never a generic "hope you're well." - Include exactly one concrete idea for how Workspace Studio could solve their problem, phrased in one sentence. - End with a low-pressure ask: a 20-minute call this week or next. - Write numbers as digits (20-minute, not twenty-minute). - After the last paragraph, leave one blank line, then sign off with "[YOUR NAME]" on its own line.
Return only the email body.

Exactly as published by Aryan Irani in Google Workspace Studio Tutorial: Batch Lead Outreach with the Repeat for Each Loop.

Our adapted version (optional)

Fill in the blanks (optional; the copied prompt uses your values)

Adapted prompt10 variables
Write the body of a first follow-up email from {your_name}, who {what_you_offer}, to this new lead.
Lead: {first_name} {last_name}, {role} at {company}. Interested in: {interest}. Notes: {notes}.
Rules: start with 'Hi {first_name},'. Keep it between {min_words} and {max_words} words, plain and friendly, with no hype and no exclamation marks. Open with their stated interest. Offer one specific idea for their situation in a single sentence. Close by suggesting a short call at a time that suits them.
Do not mention prices, dates, client names or results unless they appear in the notes. If the notes are too thin to personalize, keep it short and ask one question instead.
End with {your_name} as the final line, and output just the email body without a subject line.

What can go wrong?

  • If the status update matches on the wrong column it can change more than one row; check that each loop pass reports exactly one row updated.
  • Gemini only knows what is in the notes column, so thin notes produce generic emails; fill in a line of real context for each lead.
  • Switching the Gmail step from draft to send removes your review; the author suggests doing that only after several clean runs, and many teams should never do it.
  • Follow your local email and privacy rules, and only email people who asked to hear from you.

Our take

A good starter automation for any small team that keeps leads in a spreadsheet. Two design choices make it safe to leave running: a deterministic filter picks the rows, and the status flip after each draft makes the run idempotent, so a second run the same day does nothing. Keeping the output as drafts is the other guardrail we would insist on. We simulated the flow on a five-row synthetic tracker, one row already marked Contacted, and ran the author's prompt word for word on the four New leads, including one with a two-word notes field and one whose notes asked for a monthly price in the first email. Every draft opened with the first name only, referred to the stated interest, offered one idea in one sentence and a 20-minute call, used digits and signed off on its own line; three landed inside the word range and one came in a word short. The thin-notes lead produced the most generic email, as the author warns. The price request got a call invitation instead of an invented figure, but nothing in the prompt requires that, so our adapted version says plainly not to state prices, dates or results that are not in the notes, and to ask a question when the notes are thin. A second simulated run found no New rows and drafted nothing.

Where the time goes back: The flow does the reading, writing and bookkeeping for each lead, so your morning job shrinks to skimming and sending a short stack of drafts.

FAQ

Why not ask Gemini to find the new leads itself?
A built-in sheet filter is faster and never skips a row by accident. Gemini is used only for writing, where it adds value.
Why is the subject line not written by Gemini?
The author found that asking for a subject made Gemini put a subject line at the top of the body. A fixed subject in the Gmail step keeps every draft consistent and easy to find.
What happens on a morning with no new leads?
The loop runs zero times, nothing is drafted, and only the neutral team message posts, which is why it should not claim that follow-ups went out.

Source and credit

The original prompt on this page is by Aryan Irani, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.

Original
Google Workspace Studio Tutorial: Batch Lead Outreach with the Repeat for Each Loop
Creator
Aryan Irani
Published on
DEV Community (Google Developer Experts)
Original date
Oct 17, 2026
License
Not openly licensed; the original prompt is shown word for word with credit and a link to the original
Originally for
Gemini
AI dry run
Oct 22, 2026: passed. Dry-run tested by our AI test agent on sample input. Minor miss: one draft one word short of the range. Price guard added to our adapted prompt and pitfalls.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Sales

All 59 Sales playbooks →

Related playbooks

SalesPrompt✓ AI dry run

Draft cold emails to Lavender's reply rules

Get a short cold-email draft and subject line that follow Lavender's published length, clarity, subject and ask rules — held as a draft until you send it.

Credit: Chelsea Castle (Lavender)

Minutes
SalesWorkflow✓ AI dry run

Score a sales lead with two commands in Google's tools

Go from just a company's name to a rubric score, research notes and a tailored first message in under twenty minutes, with notes in one place.

Credit: Raghav Mehra

An afternoon+