← Back to library

Get a weekday brief of only the Google Chat you missed

Mete Atamel built a Google Workspace Studio flow for catching up on Chat. A small Apps Script step gathers the unread posts that start conversations plus new replies in threads you follow, Gemini condenses them by space with a link to each, and the result lands in a private space every weekday morning or whenever you type a command.

  • OutcomeStart each weekday with one short summary of the Google Chat messages you have not read yet, grouped by space with a link to each, while your unread badges stay in place.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditMete Atamel
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?

  • Your team works across time zones and you open Google Chat each morning to a long list of unread spaces
  • You want a catch-up summary on a schedule, not only when you remember to ask
  • Your company already uses Google Workspace and has Workspace Studio turned on

Not for: Teams that work mainly in Slack or Microsoft Teams; Anyone who needs messages marked as read automatically; this setup leaves read state alone on purpose

What do you need, and what do you get?

You need

  • A Google Workspace account with access to Workspace Studio and Gemini
  • A private Chat space for the brief (only you in it)
  • The Apps Script project and manifest from the author's public repository
  • About an hour for the one-time setup

You get

  • A bulleted brief per space with a clickable link back to the conversation
  • An on-demand version you can trigger from the brief space during the day
  • Your unread badges left as they were, so nothing is silently cleared

How does it work, step by step?

  1. Make the brief spaceCreate a private Google Chat space just for yourself; the flow posts every summary there.
  2. Install the custom stepCreate an Apps Script project, paste in the manifest and code from the author's repository, run it once to approve the read-only Chat scopes, then install it as a test deployment so Workspace Studio can see it.
  3. Build the on-demand flowIn Workspace Studio, start the flow on a chat command in your brief space, call the custom step with a 24-hour look-back and your brief space excluded, pass its output to an Ask Gemini step with the prompt below, and post Gemini's answer back to the space.
  4. Add the morning scheduleCopy the flow, swap the starter for a weekday schedule at the time you want, drop the progress message, and turn both flows on.
  5. Test itMark a conversation as unread, trigger the on-demand version, and check that each space appears once with a working link and that your badges did not change.

The prompt

The original prompt by Mete Atamel, 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 Mete Atamel

Word for wordby Mete Atamel
Provide a high-level summary of my unread Google Chat messages below, formatted as a bulleted list grouped by Space.
- If the input says NO_UNREAD_MESSAGES, just reply: "🎉 You're all caught up! No unread Google Chat messages."
- Format each Space as a bullet point starting with the Space name in bold (* **Space Name**:) followed by an overall summary whose length is proportional to the discussion (keep it brief for 1–2 messages, and more detailed for longer discussions).
- Focus on the topic and outcome rather than listing who said what. Only mention a person's name (in bold, e.g. **Aaron**) when attribution is genuinely useful—such as a specific announcement, question, or action item—and omit names entirely for general group discussions or quick updates.
- At the end of each Space's bullet item, include a clickable chat icon linked to its exact Link from the input: [💬](https://chat.google.com/room/...).
- Do not add any concluding remarks or trailing blank lines after the last bullet item.

Unread Messages Data:

Exactly as published by Mete Atamel in Google Chat Unread Messages Brief with Workspace Studio and Gemini.

Our adapted version (optional)

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

Adapted prompt3 variables
Summarize the unread Google Chat messages below for {my_name}, one bullet per space, with the space name in bold.
If the input says NO_UNREAD_MESSAGES, reply only: You're all caught up.
For each space, say what was discussed and what was decided in proportion to how much was said. Mention a person only when they asked {my_name} something, announced something or took on a task.
End each bullet with the space's link from the input, exactly as given.
After the list, add one line headed Needs you that names any direct question to {my_name} or any deadline before {deadline_window}, with its space. If there is none, leave that line out.
Use only the messages provided. Do not add closing remarks.

Unread messages:
{unread_messages}

What can go wrong?

  • The custom step reads every space you belong to, so the summary can surface private or sensitive threads; keep the brief space private and do not add anyone else to it.
  • Workspace Studio and Gemini features depend on your Google Workspace edition and admin settings; check that your admin allows them before you start.
  • A summary can drop nuance; open the linked conversation before you act on anything that involves a decision, a deadline or money.
  • The author keeps the setup read-only to avoid creating a Google Cloud project; adding a mark-as-read action needs write access and more setup, so think twice before widening the scopes.

Our take

This is a tidy example of a small, useful agent built on tools a Google Workspace team already pays for. The clever part is not the summary but the filter in front of it: the Apps Script step asks Chat's read-state API which messages are actually new to you and skips threads you never joined, so Gemini only sees what you missed. Keeping it read-only is a good default as well, since the brief never touches your unread markers and needs no Google Cloud project. We ran the author's Gemini prompt word for word on a synthetic export of unread messages from four spaces, including a space where one person posted three quick updates and another where a teammate asked the reader a direct question. The output grouped by space, kept short spaces short, named a person only where an ask or announcement needed it, ended each item with its link and added nothing after the last bullet. With an empty input it returned the all-caught-up line exactly. Our adapted prompt adds a short 'needs you' line for direct questions and deadlines, which the original leaves to the reader.

Where the time goes back: Instead of opening each space and scrolling through overnight threads, you read one list in a couple of minutes and jump straight to the few conversations that need you.

FAQ

Why not just use the built-in Ask Gemini panel in Chat?
The author found it included background threads he does not follow and could not run on a schedule. This flow filters to messages that are new to you and posts on its own each morning.
Does it mark my messages as read?
No, it only reads the read state, so every unread badge in your sidebar stays until you open the conversation yourself.
Do I need to write code?
You do not write new code. You copy two files from the author's repository into Apps Script, approve the permissions once and build the rest by clicking through Workspace Studio.

Source and credit

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

Original
Google Chat Unread Messages Brief with Workspace Studio and Gemini
Creator
Mete Atamel
Published on
Atamel.Dev
Original date
Oct 20, 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. Original and adapted prompts followed every formatting rule; nothing invented; read state is untouched by design (not exercised).
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.

Also see: google-chat-unread-brief repository (code for the custom step) by Mete Atamel. A related version of the same idea; credited and linked only, nothing from it is reproduced here.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminPrompt✓ AI dry run

Rewrite a task prompt to go deeper, not bigger

Before handing an AI an important piece of work, have it explain how a leading practitioner would approach the job, which raw inputs and methods they would use, and what independent check would prove the answer right, then rewrite your request around those answers before any work starts.

Credit: Felix Rieseberg

Minutes
Operations & AdminSkill✓ AI dry run

Stress-test an idea with an honest devil's advocate

Get an AI to argue against your plan one serious objection at a time, offer real alternatives with tradeoffs, and openly mark each concern as resolved, narrowed or still open, so you end with a stronger plan or a better one.

Credit: u/wtfzambo on r/ChatGPTPromptGenius

Minutes
Operations & AdminPrompt✓ AI dry run

Draft client documents from records with no guessed facts

Have an AI draft deal reviews, timelines, requirements docs and similar client-facing documents only from your CRM, estimates, contracts and call notes, with every line traceable, conflicts between sources flagged to you, unconfirmed items labeled as open, and a person signing off before anything goes out.

Credit: Antonio Perrone

Minutes
Operations & AdminWorkflow✓ AI dry run

Map the onboarding process before building an AI agent

A clear picture of where onboarding time actually goes, and the simplest fix, which may be plain automation rather than AI.

Credit: u/Actual-Struggle9480 on r/u_Actual-Struggle9480

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Run an overnight research team with handoff notes

Split research work into five agent roles that read, reproduce, reanalyze, scout and write, with one shared brief and human approval for anything outward-facing.

Credit: flash (@flasssh_ai)

An afternoon+