From inbox to table: a triage flow

The shape of triage

Every triage process is the same five steps: something arrives, judgment classifies it, rules score it, a record is filed, and a human catches the exceptions. That maps one-to-one onto Lemma: surface → agent → function → table → approval.

Build it

1. 1
   Prepare the pieces: a tickets table (Data), a triage agent that classifies one message (see the first-agent guide), and optionally a scoring function if you have exact priority rules.
2. 2
   Open Workflows and create one. First step: the triage agent, taking the inbound message as input.
3. 3
   Second step: a function if your priority rules are exact ("enterprise customers are always P1"), or skip — the agent’s judgment may be enough to start.
4. 4
   Third step: a decision — P1 goes one way, everything else goes the other.
5. 5
   On the P1 branch, add an approval routed to the on-call person. On the other branch, the flow just files the record and ends.
6. 6
   Run it by hand with a real message and read the run step by step. Then connect the surface (Surfaces → your inbox) so it triggers on arrival.