Curated is a platform that enables users to collect, curate, and publish newsletters, integrating with various services through its API.
Curated is a platform that enables users to collect, curate, and publish newsletters, integrating with various services through its API. On Nagent, Curated is exposed as a fully-configurable email newsletters integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Curated into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Curated 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 Curated 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 Curated, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CURATED_CREATE_DRAFT_ISSUETool to create a draft issue for a publication. Use after confirming the publication ID. Applies default settings if optional fields are omitted.
Input parameters
Title of the new draft issue
Optional note from the editor
Sequential number for the issue; if omitted, the next available number is used
The numeric ID of the publication where the draft issue will be created. Obtain this from the List Publications action.
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
CURATED_CREATE_LINKTool to create a collected link for a publication. Use when you want to add a new link (with URL, title, etc.) to a publication's collection.
Input parameters
URL for the collected link
Optional image URL for the collected link
Optional title of the collected link
Optional category for the collected link, e.g., 'code'
Optional description for the collected link
ID of the publication to which the link will be added
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
CURATED_LIST_CATEGORIESTool to list all categories for a publication. Use after you have the publication ID and need to fetch its categories.
Input parameters
The numeric ID of the publication (as a string) for which to retrieve categories. Use the 'List Publications' action first to get a list of available publication IDs.
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
CURATED_LIST_EMAIL_SUBSCRIBERSTool to list all email subscribers for a publication. Use after confirming the publication ID.
Input parameters
Page number of results to return. Starts at 1 (default: 1).
Number of subscribers per page. Valid range: 1-500 (default: 100).
The unique ID of the publication whose subscribers are being listed. Obtain this ID by calling the List Publications action first.
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
CURATED_LIST_ISSUESLists all issues (newsletters) for a Curated publication with pagination support. Use this tool to retrieve issues from a publication. You must first obtain the publication_id by calling the List Publications action. Supports filtering by state (published/draft) and optionally includes email performance stats (open/click rates).
Input parameters
Page number for pagination (1-indexed). Defaults to 1 if not specified.
Filter issues by state: 'published' returns only published issues, 'draft' returns only draft issues. If omitted, returns all issues.
If set to true, results will include open and click rates for issues.
Number of results per page. Defaults to 10, maximum is 250.
The numeric ID of the publication for which to list issues. Obtain this from the List Publications action.
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
CURATED_LIST_PUBLICATIONSTool to list all publications accessible by the API key. Use when you need to retrieve your publication IDs for further API calls. Example prompt: "List my publications".
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 98 agents privately built on Nagent that already use Curated.
Build on Nagent
Connect Curated 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 Curated, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Curated is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Curated is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Curated 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 Curated event fires, the agent kicks off automatically.
Every Curated 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 Curated ships with 6 pre-built email newsletters actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Curated together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Curated-based workflows tailored to your business.