Skip to article

Does Every Line of an AI Agent's Daily Summary Email Name a Decision?

What a daily summary email from your AI agent should hold: lines that name a decision, a cap, the count in the subject, and a send that waits for you.

By Jacqueline V. TwillieNovember 9, 20266 min readGuide
Quick answer

Every line names a decision or it's cut, in a fixed order: what needs you today, what changed since the last summary, what's waiting on someone else. You set the cap, the subject carries the count, and a quiet day says so. The block names your address, and with approvals on, a scheduled send should wait for you.

The subject line is all you see before you decide whether to open the email. "Daily summary" doesn't say what to do with it.

A summary from your AI agent can do part of its job before you open it: "3 need you today", or "Nothing needs you today".

How Do I Schedule an AI Agent to Run on Its Own? covers the trigger, and How Do I Make an AI Agent Wait for My Go-Ahead Before It Sends Anything? covers restricting what a connector can send.

What does the summary hold, line by line?

Three parts, in a fixed order: what needs a decision from you today, what changed since the last summary, and what's waiting on someone else. You set a cap on lines in all, and a line over it stays in the task. The subject carries the count of the first part.

What do you paste into the instructions for the daily summary?

Copy and fill in
You are the daily summary for my work as [YOUR ROLE]. Each morning you write one email to me, [YOUR EMAIL ADDRESS], and to nobody else. Never send, copy or forward anything to any other address.
Build it from [WHAT THE AI AGENT ALREADY READS FOR ITS JOB] and from the last summary you sent, which you can look for in earlier tasks.
Use this order, and leave out a heading that has no lines.
Needs a decision from you today: each line names the decision, what it hinges on and who is waiting.
What changed since the last summary: each line names the decision it affects. A change that affects no decision is left out.
Waiting on someone else: each line names who, since when, and what I decide if they haven't answered in [NUMBER OF DAYS] days.
Every line names a decision or it's cut. Use no more than [LINE CAP] lines in all. A line that doesn't fit stays in this task.
The subject says how many lines sit under the first heading, for example "3 need you today". If there are none, the subject is "Nothing needs you today" and the body is that sentence alone. Never pad.
If you can't find the last summary, write "no earlier summary found" and list no changes.

What happens to a scheduled email when approvals are on?

A tool that sends mail should sit with the write tools. Gumloop's page uses sending email as its approval card example, titled Approve Send Email with the Gmail icon, with To, Subject and Body as fields.

The pages don't walk through a scheduled run that reaches a card, so this part follows from three lines on them. A trigger's prompt is processed as if you'd typed it in chat, a gated call pauses, and a trigger's Task history has an Approval Required filter. With Gmail set to Ask for writes/deletes, expect the run to write the summary and wait at the card. No waiting time is given, so check your first send the next day. Checked on 2026-11-11 against Gumloop's page on approvals and Gumloop's page on AI agent triggers.

There are three ways to meet the card.

Approve it from the Approval Required filter on the Tasks page, or from the notification bell. When you approve it, the AI agent carries on and sends it. Before you approve, read the task and check that the card's key details, such as To, show your address.

Tick "Don't ask again for this tool" on the card to remember your decision for that tool on the AI agent. You give up looking at To and Body before each send and rely on the line in the block.

Or skip the email and read the summary in the task. Unanswered sends show as pending approvals under Approval Required.

Take the first. That's this page's judgment: it delivers the email and checks every send, for one approval a day.

How do you build the daily summary in Gumloop?

  1. 01

    Paste the block into the AI agent whose work you want summarized.

    Open Gumloop and that AI agent, then paste the block, with your cap and address, into the instructions box in the tab named Agent and press Save. Checked on 2026-11-09 against Gumloop's AI agent builder page.

  2. 02

    Stop chat remarks from changing the recipient.

    Switch off Edit Own Instructions under the box. Otherwise a remark such as "copy my team too" could be written in beside the line that names your address. If Reflections is on, set Apply Suggestions to Review Queue on the Performance page so instruction changes wait for you. Checked on 2026-11-11 against the self-improving instructions section of Gumloop's AI agent builder page and Gumloop's page on Reflections.

  3. 03

    Add Gmail as the connector that sends.

    In the Connectors section choose + Add and pick Gmail. Click the approval icon beside it and choose Ask for writes/deletes, since Gumloop's default is Always allow. Gumloop's pages don't list Gmail's tools, so find the sending one in Tool Management, which should sit under Write/delete tools. If there isn't one, you'll read the summary in the task. Checked on 2026-11-11 against Gumloop's AI agent builder page and Gumloop's page on approvals.

  4. 04

    Choose how the send gets past the card.

    For the first way, open Tasks in the left sidebar and filter by Approval Required once. On the second, tick the box only on a card whose key details show your address.

  5. 05

    Schedule it for the hour you'd read it.

    In the Triggers section choose Add trigger, then Scheduled Trigger. Describe the time in plain language, such as "every weekday at [YOUR TIME]", and make the prompt "Write today's summary." Checked on 2026-11-09 against Gumloop's page on AI agent triggers.

  6. 06

    Run it once and judge the subject line alone.

    Start a task with that prompt. Read the subject before the body and ask what you'd do today from that line alone. Then count the lines under the first heading and compare.

I am an ambassador for Gumloop. Code 1STAGENT takes 20% off your first month.

Is every line in the first week's summaries a decision?

Mark each line "acted" or "did nothing" for a week, and say in the block what the "did nothing" lines have in common. A subject count that differs from yours means the cap or the order isn't holding. On a quiet day, anything after "Nothing needs you today" is padding. If "no earlier summary found" appears, ask the AI agent for yesterday's subject line, since Gumloop's pages say only that Search Past Tasks retrieves earlier tasks for context. Change the cap before anything else.

Frequently asked questions

Can the summary go to my team as well?

Not as built. It names one address and nobody else; confirm it in the card's key details, such as To.

What if I miss an approval for a day?

The email doesn't go out until you approve it, and the request shows under Approval Required. Check that filter the next morning.

More on Real Workflows for Mid-Career Professionals