Email marketing platform for creating campaigns, automating workflows, and tracking results
Email marketing platform for creating campaigns, automating workflows, and tracking results On Nagent, Sender is exposed as a fully-configurable email newsletters integration that any agent can call — 8 actions, and API key authentication. No code is required to wire Sender into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Sender to automate the kinds of tasks email newsletters 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 Sender 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 Sender, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SENDER_CREATE_FIELDTool to create a new custom subscriber field in Sender.net. Use when you need to add custom fields for email personalization, segmentation, or storing additional subscriber information like company name, birthday, job title, or other custom attributes.
Input parameters
The data type of the field. Common types include 'text' for string values, 'number' for numeric values, 'date' for dates, and 'money' for currency values.
The display name/title of the custom field. This will be visible when managing subscriber data.
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
SENDER_CREATE_OR_UPDATE_SUBSCRIBERTool to create a new subscriber or update an existing one in Sender.net. Use when you need to add new subscribers to your email list or update existing subscriber information. This performs an upsert operation - creates if the email doesn't exist, updates if it does.
Input parameters
Subscriber's email address. This is required and will be used to identify existing subscribers.
Subscriber's phone number.
Custom fields object for additional subscriber attributes such as birthday, gender, location, company, title, or other relevant data.
Array of group IDs to assign the subscriber to.
Subscriber's last name.
Subscriber's first name.
Whether to trigger email automations for this subscriber. Default is true when not specified.
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
SENDER_GET_ALL_FIELDSTool to retrieve a list of all custom subscriber fields configured in the Sender.net account. Use when you need to view available fields for email personalization, segmentation, or managing subscriber data.
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
SENDER_GET_ALL_WORKFLOWSTool to retrieve a list of all automation workflows in the Sender account. Use when you need to view or manage automation workflows.
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
SENDER_GET_CAMPAIGN_BY_IDTool to retrieve a specific campaign by its unique ID from Sender. Use when you need detailed information about a campaign including delivery metrics and engagement statistics.
Input parameters
The unique identifier of the campaign to retrieve. Example: '1'
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
SENDER_GET_GROUP_BY_IDTool to retrieve a specific subscriber group by its unique ID from Sender. Use when you need detailed information about a single group including subscriber counts.
Input parameters
The unique identifier of the group to retrieve. Example: 'dBEVzJ'
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
SENDER_GET_SUBSCRIBER_BY_IDTool to retrieve a specific subscriber by their unique ID from Sender. Use when you need to fetch detailed information about a single subscriber including their status, groups, and custom fields.
Input parameters
The unique identifier of the subscriber to retrieve. Example: 'MJABNBP'
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
SENDER_UPDATE_SUBSCRIBER_FIELDSTool to update custom fields and information for an existing subscriber in Sender.net. Use when you need to modify subscriber details such as email, first name, last name, groups, or custom fields for email personalization and segmentation.
Input parameters
The subscriber's email address
Array of group IDs to assign the subscriber to
The subscriber's last name
The subscriber's first name
The unique identifier of the subscriber to update
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 95 agents privately built on Nagent that already use Sender.
Build on Nagent
Connect Sender 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 Sender, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Sender is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Sender is connected, you configure its 8 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Sender 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 Sender event fires, the agent kicks off automatically.
Every Sender 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 Sender ships with 8 pre-built email newsletters actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Sender together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Sender-based workflows tailored to your business.