Inbox Triage Agent with Codex
Classification is one sharply defined decision repeated all day: a label from your list, an owner, occasionally a Slack line. Codex is built for concrete work like that, and speed genuinely matters here, because triage is only useful if it happens before a human opens the inbox. Teams already on OpenAI tooling get it running without learning anything new.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
All 34 stores offline since 09:40
Our tills stopped syncing at 09:40 this morning and all 34 stores are taking cash only. We restarted the local gateway in two stores with no change, so it looks like the problem is on your side. Saturday is our busiest day and we are losing roughly 40,000 kroner an hour. Please call my mobile, I am reachable all day.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Gmail
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Routing rules
Your categories, the exact Gmail label for each one, who owns it, and the fallback label and owner for mail that fits nothing. The agent never invents a label or sends to anyone outside this list.
Urgent criteria
What genuinely cannot wait, such as the senders, deadlines, amounts, or phrases that should interrupt someone, plus the channel that has to hear about it. Everything else is labeled and forwarded without a Slack ping.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Codex for this agent
Built for repetition at speed
Each run is the same shape and finishes in seconds, so mail gets labeled and forwarded about as fast as it lands.
Clean with Gmail's details
Labels, thread ids and forward addresses are fiddly API mechanics rather than judgment calls. This harness is dependable at that layer, which is most of what triage physically does.
Before you fork
What do I need from OpenAI to run this?
Your own account, connected during setup by signing in with ChatGPT or with an OpenAI API key. NoClick does not resell model access, so token spend lands on your OpenAI bill and NoClick charges only for hosted sandbox time. Nothing else about the agent changes depending on which of the two you use.
Run it with a different agent
Put Inbox Triage Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.