Triages Gmail, Outlook, or IMAP threads and writes tone-matched draft replies you send yourself.
Full install guide: Install an Eve agent.
Email Triage Assistant is an Eve agent that reads the inbox on a schedule or push, sorts threads into buckets, and leaves replies in Drafts only. It is for Eve developers answering product questions. Preview every file on this page, then install with npx shadcn@latest add @evex/email-triage-assistant.
Inbox triage that classifies threads and writes draft replies without sending.
Email Triage Assistant is an eve agent that connects to one mailbox you already own. On each cron tick or signed inbox push it lists threads, reads the ones that need a human, and writes replies into the provider Drafts folder. You review those drafts in Gmail, Outlook, or IMAP and hit send yourself.
You interact with it through the inbox-triage schedule, the /inbox/push channel, or an on-demand Eve chat that still reads the mailbox. Set EMAIL_TRIAGE_GOOGLE_CONNECT_UID, EMAIL_TRIAGE_MICROSOFT_CONNECT_UID, or IMAP, plus optional Slack Connect. The agent applies TRIAGE_BUCKETS labels and matches Sent-folder tone before it calls create_draft_reply.
It is useful when you want autonomous sorting without an auto-send. Code refuses SMTP ports and send URLs. create_draft_reply always returns sent false. Newsletter and FYI threads get a bucket and no draft unless a real question is waiting in the thread.
A customer asks about an annual-plan refund. The agent reads the thread, applies needs-reply, writes a Sent-matched draft, and leaves it in Drafts for you to send.
A weekly changelog lands in the IMAP inbox. apply_triage_bucket files it under newsletter. create_draft_reply is skipped because there is no question waiting in the thread.
Outlook posts a change notification to /inbox/push with EMAIL_PUSH_WEBHOOK_SECRET. The channel starts a mailbox run that drafts a reply without calling sendMail.
After a cron run writes three Drafts, notify_slack_drafts_ready posts to the Eve Slack Connect channel. The note says drafts are ready. Nothing is emailed.
Run npx shadcn@latest add @evex/email-triage-assistant in an Eve app, copy .env.example, set one mailbox provider, then POST /eve/v1/dev/schedules/inbox-triage while iterating.
No. create_draft_reply always returns sent false. Gmail stops at drafts.create, Graph uses createReply, and IMAP APPENDs to Drafts. SMTP and send URLs are refused in code.
Point the provider webhook at POST /inbox/push with EMAIL_PUSH_WEBHOOK_SECRET. Graph validationToken on GET or POST is echoed as plain text so the subscription can complete.
No. The inbox-triage skill reads the connected mailbox. A paste-and-copy-text flow is not this agent. Use support-reply-draft if you want a docs-cited paste draft.
No. EMAIL_TRIAGE_SLACK_CONNECT_UID and EMAIL_TRIAGE_SLACK_CHANNEL_ID are optional. When both are set, notify_slack_drafts_ready posts that drafts are waiting through the Eve Slack channel. That ping is not email delivery.
npx shadcn@latest add @evex/email-triage-assistant