DocuPost is a print and mail service that enables users to send digital files as physical letters and postcards via the U.S. Postal Service.
DocuPost is a print and mail service that enables users to send digital files as physical letters and postcards via the U.S. Postal Service. On Nagent, Docupost is exposed as a fully-configurable documents integration that any agent can call — 3 actions, and API key authentication. No code is required to wire Docupost into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Docupost to automate the kinds of tasks documents 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 Docupost 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 Docupost, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DOCUPOST_GET_BALANCETool to check the current account balance in DocuPost. Use this before sending letters or postcards to verify sufficient funds are available.
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
DOCUPOST_SEND_LETTERSend a physical letter via U.S. mail using DocuPost. Requires recipient address (to_name, to_address1, to_city, to_state, to_zip), sender address (from_name, from_address1, from_city, from_state, from_zip), and a PDF document URL. Example: send_letter( to_name='John Doe', to_address1='123 Main St', to_city='Los Angeles', to_state='CA', to_zip='90210', from_name='Sender Corp', from_address1='456 Sender Rd', from_city='Los Angeles', from_state='CA', from_zip='90210', pdf='https://example.com/document.pdf' )
Input parameters
Public URL of the PDF document to mail (max 10MB, 8.5x11 recommended)
Test mode: letter will not actually be mailed. Default is false.
Print in color. Default is false (black and white).
Recipient's ZIP code (5 digits)
Recipient's city
Recipient's full name (max 40 characters)
Sender's ZIP code (5 digits)
Recipient's U.S. state abbreviation (2 letters)
Sender's city
Sender's full name or organization (max 40 characters)
Sender's U.S. state abbreviation (2 letters)
Mail service class. Options: 'usps_first_class' (default), 'usps_standard', 'usps_priority_mail', 'usps_priority_mail_express'.
Recipient's company or attention line (max 40 characters)
Optional internal note (max 40 characters). Visible in CSV exports and dashboard.
Double-sided printing. Default is true.
Recipient's street address
Recipient's secondary address line (apt, suite, etc.)
Service level for first class mail. Options: 'certified', 'certified_return_receipt'. Leave blank for standard delivery.
Sender's street address
Sender's secondary address line (apt, suite, etc.)
Include a prepaid return envelope. Default is false.
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
DOCUPOST_SEND_POSTCARDTool to send a postcard via U.S. mail with specified recipient, sender, and front/back images. Use after confirming recipient addresses and design URLs. Example: send_postcard(to_name='John Doe', ..., front_image='https://...', back_image='https://...')
Input parameters
Postcard size. Defaults to '4x6' if not specified.
Recipient's 5-digit ZIP code
Recipient's city
Recipient's full name (max 40 characters)
Sender's 5-digit ZIP code
Recipient's U.S. state (2-letter abbreviation)
Sender's city
Sender's full name or company name (max 40 characters)
Publicly accessible URL for the postcard's back-side image (recommended: 1875x1275 pixels, PNG format)
Sender's U.S. state (2-letter abbreviation)
Internal note for tracking purposes (not printed on postcard)
Publicly accessible URL for the postcard's front-side image (recommended: 1875x1275 pixels, PNG format)
Recipient's street address (line 1)
Recipient's street address (line 2, e.g., apt/suite number)
Sender's street address (line 1)
Sender's street address (line 2, e.g., apt/suite number)
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 47 agents privately built on Nagent that already use Docupost.
Build on Nagent
Connect Docupost 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 Docupost, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Docupost is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Docupost is connected, you configure its 3 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Docupost 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 Docupost event fires, the agent kicks off automatically.
Every Docupost 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 Docupost ships with 3 pre-built documents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Docupost together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Docupost-based workflows tailored to your business.