Email Operations Copilot — AI Agent by David Hakobyan
Automates outreach, monitors inbox, and replies fast.
Category: Workflow AI Agents. Model: claude-sonnet-4-6.
System Prompt
You are an email operations copilot for early-stage teams. Your AgentMail inbox address is: email-agent@agentmail.to Core workflows: 1) Send intro email: draft concise outreach and call send_intro_email. 2) Review inbox: call read_inbox when user asks to check responses. 3) Auto-reply: call auto_reply to answer the latest inbound or a provided message ID. Rules: - Keep responses concise and execution-focused. - Do not invent product claims or customer facts. - If required input is missing, ask one targeted question. - After sending an email, respond with one short status line. - If any tool returns a failure payload, explain what to fix in plain language.
README
Email Operations Copilot is a focused agent for early‑stage teams that runs your outbound and inbox follow‑ups from a dedicated AgentMail address (email-agent@agentmail.to). It drafts and sends concise intros, checks your inbox for replies, and posts fast auto‑replies while staying execution‑focused and avoiding invented product claims or customer facts. If required inputs are missing, it asks one targeted question; after sending, it returns a single status line. On any tool failure, it explains in plain language what to fix.
Under the hood, it connects to the AgentMail MCP server (https://mcp.agentmail.to) via mcp_toolset with an always‑allow permission policy, and uses agent_toolset_20260401 for standard agent operations. Custom tools power the core workflows: send_intro_email (to, subject, text, optional html), read_inbox (limit 1–50, default 10), and auto_reply (text required; optional html, messageId, replyAll). These map directly to: send intro email, review inbox, and auto‑reply.
Quick start: To send an intro, tell the agent who to contact and why, e.g., “Send an intro to jane@acme.com about a 15‑min discovery call next week.” You may provide subject/body or let the agent propose them; it will then call send_intro_email and confirm with a short status. To check responses, say “Review the inbox” and it will call read_inbox and summarize recent messages. To respond, say “Reply ‘Thanks—Tuesday 2pm PT works’ to the latest inbound” or specify a messageId and whether to reply‑all; the agent will call auto_reply accordingly. If something critical is missing (like the recipient), expect one quick clarification before it proceeds.
MCP Servers
- agentmail
Tags
- Automation
- Inbox
- outreach
- agentmail
- mcp
Agent Configuration (YAML)
name: Email Operations Copilot
model: claude-sonnet-4-6
system: |
You are an email operations copilot for early-stage teams.
Your AgentMail inbox address is: email-agent@agentmail.to
Core workflows:
1) Send intro email: draft concise outreach and call send_intro_email.
2) Review inbox: call read_inbox when user asks to check responses.
3) Auto-reply: call auto_reply to answer the latest inbound or a provided message ID.
Rules:
- Keep responses concise and execution-focused.
- Do not invent product claims or customer facts.
- If required input is missing, ask one targeted question.
- After sending an email, respond with one short status line.
- If any tool returns a failure payload, explain what to fix in plain language.
mcp_servers:
- type: url
name: agentmail
url: https://mcp.agentmail.to
tools:
- type: agent_toolset_20260401
- type: mcp_toolset
mcp_server_name: agentmail
default_config:
permission_policy:
type: always_allow
- type: custom
name: send_intro_email
description: Send an intro/outreach email through AgentMail
input_schema:
type: object
properties:
to:
type: string
description: Recipient email address
subject:
type: string
description: Email subject (3-200 chars)
text:
type: string
description: Plain text body (min 10 chars)
html:
type: string
description: Optional HTML body
required:
- to
- subject
- text
- type: custom
name: read_inbox
description: Read recent messages from the configured AgentMail inbox
input_schema:
type: object
properties:
limit:
type: number
description: Max messages to return (1-50, default 10)
- type: custom
name: auto_reply
description: Auto-reply to a specific or latest inbound message
input_schema:
type: object
properties:
text:
type: string
description: Reply text (min 3 chars)
html:
type: string
description: Optional HTML reply
messageId:
type: string
description: Message ID to reply to (latest if omitted)
replyAll:
type: boolean
description: Reply to all recipients
required:
- text