Solutions

Email & follow-ups

The overnight mail, at half past seven, and nothing else.

@attest_tagdirect message3 tool calls

A weekday routine that reads the mail which arrived since the end of the previous working day, keeps what came from outside the company, and DMs one list — and says nothing at all on a morning with nothing in it.

attest_tag

Mei7:30 AM

every weekday at 7:30 send me anything that landed overnight from a customer, and nothing else

attest_tagApp7:31 AM

  • create_routine · weekdays 07:30 Europe/London · as Mei
  • http_request · GET gmail.googleapis.com/gmail/v1/users/me/messages?q=after:… · 9 messages
  • http_request · GET …/messages/{id}?format=metadata · 9 header reads

Overnight — 3 from customers.

  • 22:40 · Dan Ellis, Northwind — “can we move Tuesday?”
  • 06:05 · [email protected] — remittance advice, £8,400.
  • 06:52 · Priya Raman — forwarded a security questionnaire from their legal team.

Six others were internal or automated and are not listed. Ask me to draft a reply to any of them.

google/gemini-flash7.2k in300 out$0.0038Configure

Names, figures, repositories and customers are changed; token counts and cost are illustrative. The ask, and the shape of the answer, are as they were.

How the turn went

A cron line, a window that knows about weekends, and permission to be silent.

  1. 01

    The window, not the last 24 hours

    “Overnight” on a Monday means since Friday evening. The routine works out the previous working day in the scope’s timezone rather than subtracting a fixed number of hours, which is the difference between a useful Monday digest and one that hides two thirds of the weekend.

  2. 02

    Outside the company is the filter

    Mail from a colleague or from a machine is left out, and the count of what was left out is printed. The point of the digest is the mail that came from someone who is paying you.

  3. 03

    Silence is a valid run

    On a morning with nothing, it posts nothing. The run is still recorded in the console with its cost, so a silent routine and a broken one are told apart by looking rather than by guessing.

  4. 04

    It runs as you, and only reads

    The routine holds the creator’s own Google sign-in, so it reads exactly the mailbox they could read themselves. It has no writes, so there is nothing for it to pre-approve.

What it needs

The setup, in the console.

Connection
The Google Workspace preset: an OAuth client an admin registers once, with the parts you mean to use ticked — Gmail, Calendar, Drive, Contacts — attached to the channel.
Credential
Each person's own sign-in, from a Connect button the bot DMs them, held per user. No shared token exists for a channel to spend.
Routine
Cron, timezone and prompt, editable in the console. Every run is listed with its tokens and cost, including the runs that posted nothing.

What it will not do

Enforced outside the model.

  • It will not post a “nothing to report” message. An empty run is silent.

  • It cannot survive the creator disconnecting their Google account: the routine fails visibly in the console rather than running with somebody else's token.

Try it

Say it in a channel it is in.

The sentence as it was typed. It works in any channel the bot has been invited to that carries the connection above — no command syntax, no form, and follow-ups in the thread need no mention.

every weekday at 7:30 send me anything that landed overnight from a customer, and nothing else

  • Gmail
  • create_routine
  • http_request

Bring the channel this would live in.

Sign up, connect the service above in one channel, and type this sentence yourself — or run the same binary on your own infrastructure.

All solutions