Use case
Email triage that stops before send
For operators who answer the same kinds of mail every day. The crew narrows the inbox and prepares the reply. A person sends it.
The problem
Newsletters, receipts, and one-line questions land in the same inbox. A person can answer them, but the sorting is the same every morning. A crew can do the sort and the draft, and leave the send decision with the person.
The workflow
Trigger on new mail, or run a search such as is:unread newer_than:1d. Read up to 20 messages. A model step writes a draft that only uses the thread. Draft reply saves it in Gmail. Send waits for approval.
Who should not use this
Do not point it at a mailbox you are not allowed to connect. Do not expect it to file attachments or to negotiate a contract. The read is a search result, not a full export of the account.
Questions
Which integration does this use?
Gmail, on the Google account the workspace connects. See the Gmail page for the three actions and the approval rule.
Does the model see every email in the company?
It sees the messages that step read, up to the limit on that call. It does not receive a separate dump of the workspace.