Sequential AgentOperationsintermediate

Inbox Triage Assistant

Acts as · Executive Assistant

Triages a pasted batch of emails into act-now, reply-today, delegate, read-later, and ignore buckets against your stated priorities, then drafts the urgent replies for you. Returns a triage table with one-line reasons, flagged commitments and deadlines, ready-to-send reply drafts, and delegation notes. Pure standalone, no inbox connection required.

A single-purpose agent that runs an ordered list of tasks against your tools, knowledge and tables, the same way every run.

Official~2 min setupby Akshay Gupta
How it works

Inputs in, an ordered run, a result out.

A Sequential Agent takes typed inputs, runs its tasks top to bottom against your tools and tables, and returns a structured result, the same way on every run.

Typed inputs
Values you pass in, validated before the run spends anything.
2 tasks
Each task runs in order, passing its output to the next.
Runs standalone
No external tools or tables needed.
Result + trace
A structured output, with every step recorded.
The run loop
ReadPlanActCheckWriteTracerepeats until done

What's inside

Everything this template installs, by name.

Tools & tables
Runs standalone, no external tools or tables required
Tasks
2 ordered tasks

What it takes in

The inputs you provide on each run, validated before anything executes.

InputTypeRequired
Email BatchemailBatchLong textRequired
Your PrioritiesprioritiesLong textOptional
The work, step by step

2 tasks, run in order.

Each task passes its result to the next. Here's what each does and what it produces.

  1. 01
    Triage the batch. Read every email in {{emailBatch}} and classify each one as Act Now, Reply Today, Delegate, Read Later, or Ignore. Judge urgency and importance against {{priorities}} if provided; if no priorities are given, use sensible executive defaults (revenue, customers, existing commitments, hard deadlines, direct asks from senior people). Give each email a one-line reason tied to the stated priorities. Separately flag anything that smells like a commitment or a deadline: explicit or implied: even in emails classified Read Later or Ignore. Do not skip any email, and do not invent emails, senders, or deadlines that are not in the batch. Present readably, never JSON.
    Expected output
    A readable triage with no JSON and no code blocks: a table with columns Sender, Subject, Category (Act Now / Reply Today / Delegate / Read Later / Ignore), and Reason (one line tied to the stated priorities), covering every email in the batch; followed by a Commitments & Deadlines section listing each detected commitment or deadline with its source email and the date if stated.
  2. 02
    Draft the responses. For every email classified Act Now or Reply Today in Task 1, write a complete, ready-to-send reply draft in a tone appropriate to the sender and context (formal for external senior contacts, direct and warm for teammates). Each draft must resolve or advance the thread: answer the question, confirm or decline the ask, or propose a concrete next step: in under 120 words. For every email classified Delegate, write a one-line suggested delegation note naming what needs doing and by when if a deadline exists. Never fabricate facts, numbers, or availability; where information is missing, use a clearly marked placeholder in square brackets like [YOUR AVAILABILITY]. Present readably, never JSON.
    Expected output
    A readable drafts pack with no JSON and no code blocks containing two sections: Reply Drafts (one heading per Act Now or Reply Today email showing the sender and subject, followed by the complete draft reply under 120 words, with any missing information as square-bracket placeholders) and Delegation Notes (a one-line note per Delegate item naming what needs doing and any deadline).

Related templates