ProxiedMail offers privacy-focused email services, including automatic creation of proxy emails and receiving emails via webhooks.
ProxiedMail offers privacy-focused email services, including automatic creation of proxy emails and receiving emails via webhooks. On Nagent, Proxiedmail is exposed as a fully-configurable email integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Proxiedmail into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Proxiedmail to automate the kinds of tasks email teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Proxiedmail into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Proxiedmail, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PROXIEDMAIL_CREATE_WEBHOOK_RECEIVERTool to create a webhook receiver for incoming email callbacks. Use when you need a unique endpoint to capture proxiedmail webhook events.
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
PROXIEDMAIL_GET_API_TOKENTool to retrieve a permanent API token. Use after obtaining a Bearer token from the auth endpoint (POST /api/v1/auth).
Input parameters
Bearer token obtained from POST /api/v1/auth. Omit leading 'Bearer ' prefix if present.
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
PROXIEDMAIL_GET_WEBHOOK_DATATool to retrieve data from a webhook receiver. Returns the payload sent to the webhook's call_url, status info about whether a callback was received, and the HTTP method used.
Input parameters
Callback hash identifier for the webhook receiver
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
PROXIEDMAIL_LIST_PROXY_BINDINGSTool to fetch a list of proxy bindings. Use after authentication to list all proxy bindings associated with the user.
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
PROXIEDMAIL_UPDATE_PROXY_BINDINGTool to update an existing proxy binding. Use after obtaining the binding ID to modify its addresses or settings.
Input parameters
Top-level JSON:API data object.
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 62 agents privately built on Nagent that already use Proxiedmail.
Build on Nagent
Connect Proxiedmail 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 Proxiedmail, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Proxiedmail is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Proxiedmail is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Proxiedmail 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 Proxiedmail event fires, the agent kicks off automatically.
Every Proxiedmail 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 Proxiedmail ships with 5 pre-built email actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Proxiedmail together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Proxiedmail-based workflows tailored to your business.