AgentMail provides AI agents with their own email inboxes, enabling them to send, receive, and act upon emails for communication with services, people, and other agents.
AgentMail provides AI agents with their own email inboxes, enabling them to send, receive, and act upon emails for communication with services, people, and other agents. On Nagent, Agent Mail is exposed as a fully-configurable ai agents integration that any agent can call — 5 actions, 1 trigger, and API key authentication. No code is required to wire Agent Mail into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Agent Mail to automate the kinds of tasks ai agents teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Agent Mail also supports 1 event trigger ("New Email Received"), which lets your Nagent agents react to Agent Mail activity in real time — for example, kicking off a downstream workflow the moment a relevant event fires.
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Agent Mail into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Triggers are the entry points of agents built on Nagent — pick one to fire your agent the moment a Agent Mail event happens. Webhook triggers run instantly; poll triggers check on an interval you configure. Each shows its configuration parameters and the payload your agent receives.
AGENT_MAIL_NEW_EMAIL_TRIGGERTrigger for new emails in an AgentMail inbox
Configuration
The inbox ID or email address to monitor for new emails
Periodic Interval to Check for Updates & Send a Trigger in Minutes
Filter messages by specific labels (e.g., 'unread', 'inbox')
Payload
Message attachments
BCC email addresses
CC email addresses
When the message was created
Sender's email address
HTML content
ID of message being replied to
ID of the inbox
Labels applied to the message
ID of the message
Text preview of the message
IDs of previous messages in thread
Reply-to email addresses
Email subject
Plain text content
ID of the thread
When the message was received
Recipient email addresses
When the message was last updated
Every operation an agent can call against Agent Mail, with input parameters and output schema. Drop these into any step of an agent built in Helix.
AGENT_MAIL_CREATE_INBOXCreate a new AgentMail inbox via API. Returns the inbox_id and email address for sending/receiving messages. Use when provisioning new inboxes for agents or workflows.
Input parameters
Domain for the inbox email address. Must be a verified domain in your AgentMail account. Defaults to 'agentmail.to' if not provided.
Username for the inbox. Used to create the email address (username@domain). If not provided, a random username will be generated.
Client-side identifier for idempotency or correlation. Can be used to prevent duplicate inbox creation or to associate the inbox with your internal systems.
Display name for the inbox (shown as the sender name in emails)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGENT_MAIL_GET_MESSAGERetrieve the complete details of a specific email message from an AgentMail inbox. This action returns the full message content including sender, recipients, subject, body (both text and HTML), attachments, labels, and metadata. Use this to read individual messages after discovering them via LIST_MESSAGES or webhooks.
Input parameters
MUST be a valid email address (e.g., agent@agentmail.to). This is NOT an ID or identifier - it must be a full email address of the inbox.
The unique message identifier (NOT an email address). Get this from the 'message_id' field returned by LIST_MESSAGES.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGENT_MAIL_LIST_INBOXESList all inboxes available to the authenticated AgentMail account. Use this to discover valid inbox_id values for message operations.
Input parameters
Maximum number of inboxes to return per page
Sort inboxes in ascending order by created_at timestamp (oldest first). Default is descending (newest first)
Token for pagination to get the next set of results
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGENT_MAIL_LIST_MESSAGESList messages from an AgentMail inbox. Returns a `messages` array; each message uses `message_id` and `timestamp` fields (not `id`, `date`, or `items`).
Input parameters
Return messages sent after this timestamp (ISO 8601 format)
Maximum number of messages to return (1-100)
Return messages sent before this timestamp (ISO 8601 format)
Filter messages by labels (e.g., 'sent', 'unread', 'important')
MUST be a valid email address (e.g., agent@agentmail.to). This is NOT an ID or identifier - it must be a full email address of the inbox.
Sort messages in ascending order by timestamp (oldest first). Default is descending (newest first)
Token for pagination to get the next set of results
Include messages marked as spam in the results
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
AGENT_MAIL_SEND_EMAILSend an email using AgentMail API
Input parameters
List of CC recipient email addresses
List of recipient email addresses
List of BCC recipient email addresses
HTML content of the email. Either text or html (or both) must be provided. If both are provided, email clients will typically prefer HTML with text as fallback.
Plain text content of the email. Either text or html (or both) must be provided.
Labels to apply to the sent message
Email subject line
The inbox identifier (typically the full email address, e.g., 'your-inbox@agentmail.to'). Use AGENT_MAIL_LIST_INBOXES to discover available inbox IDs, or AGENT_MAIL_CREATE_INBOX to create a new inbox.
Reply-to email addresses
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 31 agents privately built on Nagent that already use Agent Mail.
Build on Nagent
Connect Agent Mail to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Agent Mail, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Agent Mail is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Agent Mail is connected, you configure its 5 actions and 1 trigger directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Agent Mail steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Agent Mail event fires, the agent kicks off automatically.
Every Agent Mail action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Agent Mail ships with 5 pre-built ai agents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Agent Mail together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Agent Mail-based workflows tailored to your business.