Docparser is the most advanced cloud based document parsing and automation tool in the market today.
Docparser is the most advanced cloud based document parsing and automation tool in the market today. On Nagent, Docparser is exposed as a fully-configurable documents integration that any agent can call — 4 actions, and API key authentication. No code is required to wire Docparser into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Docparser 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 Docparser 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 Docparser, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DOCPARSER_GET_MULTIPLE_DOCUMENT_RESULTSTool to retrieve parsed data from multiple documents processed by a specific parser. Use when you need to fetch results for multiple documents at once. Returns up to 100 results by default, with a maximum of 10000.
Input parameters
ISO 8601 or Unix timestamp; required when using 'uploaded_after' or 'processed_after' list modes.
Filtering mode - 'last_uploaded', 'uploaded_after', or 'processed_after'.
Maximum number of documents to return. Default is 100, maximum is 10000.
Output format - 'object' for nested JSON or 'flat' for simplified key/value pairs.
Sort by timestamp field. Options: 'parsed_at', 'processed_at', 'uploaded_at', 'first_processed_at', 'imported_at', 'integrated_at', 'dispatched_webhook_at', or 'preprocessed_at'.
Unique identifier for the document parser. Can be obtained via the List Parsers endpoint or found in parser settings under 'Settings > API'.
Returns only documents with matching remote_id.
Sort direction - 'ASC' for ascending or 'DESC' for descending.
Include unprocessed documents when set to true.
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
DOCPARSER_GET_PARSER_MODELSTool to retrieve all model layouts for a specific parser. Use when you need to list different layout configurations within a parser that help handle document variations.
Input parameters
The unique identifier of the parser. Can be obtained from the List Parsers endpoint or found in the Document Parser settings under 'Settings > API' within the Docparser app.
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
DOCPARSER_LIST_PARSERSTool to retrieve all Document Parsers linked to your account. Use when you need to view available parsers or obtain parser IDs for subsequent 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
DOCPARSER_PINGTool to test API authentication and connection health check for Docparser API. Use when you need to verify that API credentials are valid and the connection is working.
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 73 agents privately built on Nagent that already use Docparser.
Build on Nagent
Connect Docparser 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 Docparser, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Docparser is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Docparser is connected, you configure its 4 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Docparser 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 Docparser event fires, the agent kicks off automatically.
Every Docparser 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 Docparser ships with 4 pre-built documents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Docparser together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Docparser-based workflows tailored to your business.