DPD is a digital product delivery platform for selling ebooks, software, music, and other digital goods.
DPD is a digital product delivery platform for selling ebooks, software, music, and other digital goods. On Nagent, Dpd2 is exposed as a fully-configurable ecommerce integration that any agent can call — 8 actions, and API key authentication. No code is required to wire Dpd2 into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Dpd2 to automate the kinds of tasks ecommerce 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 Dpd2 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 Dpd2, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DPD2_GET_STOREFRONTRetrieves detailed information about a specific DPD storefront by its ID. Returns storefront configuration including name, URL, contact details, currency, type, and subdomain. Use this after obtaining a storefront ID from DPD2_LIST_STOREFRONTS or when you need to fetch current metadata for a known storefront.
Input parameters
The numeric storefront ID to retrieve. Obtain this from DPD2_LIST_STOREFRONTS or use a known storefront ID.
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
DPD2_LIST_CUSTOMERS2Tool to list customers in your DPD account with advanced filtering. Use when you need to find customers by email, name, product purchases, newsletter subscription status, or creation date range.
Input parameters
Page number for paginated results (starts at 1).
Customer email (startswith match, not case sensitive). Use to find customers by email prefix.
Customer created before this date (PHP strtotime format, e.g., 'YYYY-MM-DD', '1 week ago', 'yesterday'). Use to filter customers created before a specific date.
Customer created after this date (PHP strtotime format, e.g., 'YYYY-MM-DD', '2 weeks ago', 'last Monday'). Use to filter customers created after a specific date.
Number of customers to return per page (max 100).
Customer last name (startswith match). Use to find customers by last name prefix.
Customer first name (startswith match). Use to find customers by first name prefix.
Product ID that the customer has purchased. Use to find customers who bought a specific product.
Whether customer receives email from product updates. Use true to find subscribed customers, false for unsubscribed.
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
DPD2_LIST_PURCHASESTool to list all purchases made through your DPD account. Use when you need to retrieve purchase records with optional date filters and pagination for reporting or analysis.
Input parameters
Page number for results pagination (default 1)
Number of purchases to return (max 1000)
Only include purchases made on or after this date (YYYY-MM-DD)
Only include purchases made on or before this date (YYYY-MM-DD)
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
DPD2_LIST_STOREFRONTSTool to list all storefronts in your DPD account. Use after authenticating to fetch storefront details before managing products or purchases.
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
DPD2_LIST_SUBSCRIBERSTool to list subscribers for a given storefront. Use when you need a paginated and filtered list of subscribers after storefront setup.
Input parameters
Page number to retrieve (>=1).
Filter by subscriber email address.
Only return subscribers added or updated since this ISO8601 timestamp.
Additional filter expression.
Number of subscribers per page.
Storefront ID.
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
DPD2_PINGTool to ping the API to check its status. Use when verifying API connectivity before further operations.
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
DPD2_VERIFY_NOTIFICATION2Tool to verify a POST from the URL integration (IPN/webhook). POST all parameters that were POSTed to your site to confirm authenticity. Use after receiving an IPN notification to validate it came from DPD.
Input parameters
Total tax amount
Unique identifier for the purchase/transaction
The discount (coupon) amount applied to the order
Total amount of payment
The coupon code used on the order, if any
Currency of the total amount
Total shipping cost
Verification signature from the original notification
Shipping method used
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
DPD2_VERIFY_SUBSCRIBERTool to verify a subscriber's subscription status. Use when you need to check if a subscriber is active and receiving service. Either username (email) or subscriber ID must be provided.
Input parameters
Subscriber ID. Either username or subscriber_id must be provided.
Username (the subscriber's email address). Either username or subscriber_id must be provided.
The numeric storefront ID.
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 42 agents privately built on Nagent that already use Dpd2.
Build on Nagent
Connect Dpd2 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 Dpd2, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Dpd2 is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Dpd2 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 Dpd2 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 Dpd2 event fires, the agent kicks off automatically.
Every Dpd2 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 Dpd2 ships with 8 pre-built ecommerce actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Dpd2 together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Dpd2-based workflows tailored to your business.