Replying to routine email eats hours, but full automation feels risky because one wrong send goes straight to a customer. This agent reads each incoming thread, writes a draft in your tone, and waits for a person to approve it.
sonnet4 daysIMAPSMTPClaudePostgreSQL
Claude
65ROI
85Scale
$4.1k95Saved
ROI for
README.md
Why this subagent
Replying to routine email eats hours, but full automation feels risky because one wrong send goes straight to a customer. This agent reads each incoming thread, writes a draft in your tone, and waits for a person to approve it.
Drafts land in Slack with Approve and Edit buttons. Nothing leaves until a human says yes. Approved replies go out over SMTP and get logged, so you keep an audit trail of who sent what and when.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Pull prior thread history and any matching customer record to give the model context for the reply.
pending
Generate a draft response and post it to a Slack approval channel with Approve and Edit buttons.
pending
Send the approved draft over SMTP and log the final text against the thread in PostgreSQL.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
Draft a reply to the incoming email; return JSON with subject, body, and a confidence score from 0 to 1.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.