No-code email parser to extract and export valuable data from emails, PDFs and documents
No-code email parser to extract and export valuable data from emails, PDFs and documents On Nagent, Parsio.io is exposed as a fully-configurable ai document extraction integration that any agent can call — 24 actions, and API key authentication. No code is required to wire Parsio.io into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Parsio.io to automate the kinds of tasks ai document extraction 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 Parsio.io 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 Parsio.io, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PARSIO_IO_CREATE_HTML_TEXT_DOCUMENTTool to create and parse HTML or text documents via API. Use when you need to submit HTML or text content to a Parsio mailbox for data extraction. At least one of html or text must be provided.
Input parameters
Recipient's email address
Sender's email address
HTML content to parse. At least one of html or text must be provided. If both are provided, HTML takes precedence.
Additional payload data as key-value pairs
Document's name or subject line for emails
Text content to parse. At least one of html or text must be provided.
The unique identifier of the mailbox where the document will be processed
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
PARSIO_IO_CREATE_MAILBOXTool to create a new mailbox with a specified name. Use when you need to set up a new mailbox for email parsing in Parsio.
Input parameters
The name to assign to the new mailbox
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
PARSIO_IO_CREATE_WEBHOOKTool to create a new webhook for a mailbox with specified URL, event trigger, and settings. Use when you need to register a webhook endpoint to receive automated notifications for mailbox events.
Input parameters
The webhook URL where events will be sent. Must be a valid HTTPS URL.
Trigger event type for the webhook. Accepted values: 'doc.parsed' for parsed documents, 'doc.parsed.flat' for flat parsed data, 'doc.fail' for failed documents, 'doc.received' for received documents, 'table.parsed' for parsed tables (requires table_id).
Whether the webhook is active and should trigger on events.
Table ID identifier. Required only when event is 'table.parsed'. Leave empty or omit for other event types.
The unique identifier of the mailbox to attach the webhook to.
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
PARSIO_IO_DELETE_MAILBOXTool to delete a specific mailbox from your Parsio account. Use when you need to permanently remove a mailbox.
Input parameters
Unique identifier of the mailbox to delete
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
PARSIO_IO_DELETE_TEMPLATESTool to delete multiple templates by providing an array of template IDs. Use when you need to remove one or more templates from a mailbox.
Input parameters
Array of template IDs to delete. Collection of template identifiers to be removed from the mailbox.
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
PARSIO_IO_DELETE_WEBHOOKSTool to delete multiple webhooks from a mailbox. Use when you need to remove one or more webhook configurations by providing their IDs.
Input parameters
Array of webhook IDs to delete
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
PARSIO_IO_DISABLE_TEMPLATESTool to disable multiple templates by providing an array of template IDs. Use when you need to deactivate multiple templates in a mailbox.
Input parameters
Array of template identifiers to deactivate. Provide template IDs that need to be disabled.
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
PARSIO_IO_ENABLE_TEMPLATESTool to enable multiple templates by providing an array of template IDs. Use when you need to activate multiple templates for use in a mailbox.
Input parameters
Array of template identifiers to activate. Provide template IDs that need to be enabled.
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
PARSIO_IO_GET_DOCUMENTTool to retrieve a specific document with parsed data as JSON. Use when you need to fetch details of a document by its ID.
Input parameters
The unique identifier of the document to retrieve
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
PARSIO_IO_GET_MAILBOXTool to retrieve details of a specific mailbox. Use when you need to fetch configuration and settings for a particular mailbox.
Input parameters
The unique identifier of the mailbox to retrieve.
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
PARSIO_IO_GET_PARSED_DATATool to get parsed data from a mailbox with optional date range filters and pagination. Use when you need to retrieve extracted information from documents that have been processed through Parsio's parsing system.
Input parameters
End date filter in YYYY-MM-DD format to retrieve documents up to this date
Start date filter in YYYY-MM-DD format to retrieve documents from this date onwards
Page number for pagination. Use this to retrieve additional pages of results.
The unique identifier of the mailbox to retrieve parsed data from
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
PARSIO_IO_GET_TEMPLATETool to retrieve details of a specific parsing template by its ID. Use when you need to inspect a template's configuration, fields, or status.
Input parameters
Unique identifier of the template to retrieve
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
PARSIO_IO_GET_WEBHOOKTool to retrieve details of a specific webhook by its ID. Use when you need to inspect a webhook's configuration, status, or event type.
Input parameters
Unique identifier of the webhook to retrieve
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
PARSIO_IO_LIST_COLLECTED_EMAILSTool to list all collected email addresses from a specific mailbox. Use when you need to retrieve email addresses that have been automatically collected during document parsing. The mailbox must have the 'collect_emails' setting enabled.
Input parameters
Page number for pagination. Use this to retrieve additional pages of results.
Unique identifier of the mailbox to retrieve collected emails from
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
PARSIO_IO_LIST_DOCUMENTSTool to retrieve a list of documents from a specific mailbox. Use when you need to list documents with optional filtering by date range, search query, or processing status. Supports pagination for large result sets.
Input parameters
Search query string to filter documents. Searches within document content.
End date filter in YYYY-MM-DD format. Only documents up to this date will be returned.
Start date filter in YYYY-MM-DD format. Only documents from this date onwards will be returned.
Page number for pagination through results. Use to retrieve additional pages of documents.
Filter by document status. Multiple statuses can be specified. Accepted values: 'parsed', 'fail', 'skipped', 'new', 'quota', 'parsing', 'exception'.
The unique identifier of the mailbox to retrieve documents from.
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
PARSIO_IO_LIST_MAILBOXESTool to retrieve all mailboxes in the account. Use when you need to list all available mailboxes and their configurations.
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
PARSIO_IO_LIST_TABLE_FIELDSTool to list all table fields in a specific mailbox. Use when you need to view the structure of data fields available for a mailbox.
Input parameters
The unique identifier of the mailbox whose table fields you want to retrieve.
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
PARSIO_IO_LIST_TEMPLATESTool to list all parsing templates associated with a specific mailbox. Use when you need to retrieve all template configurations for a mailbox, including their enabled status and metadata. Supports pagination for mailboxes with many templates.
Input parameters
Page number for pagination. Use this to navigate through multiple pages of templates.
The unique identifier of the mailbox to list templates from
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
PARSIO_IO_LIST_WEBHOOKSTool to retrieve all webhooks configured for a specific mailbox. Use when you need to list webhooks associated with a mailbox.
Input parameters
The unique identifier for the mailbox whose webhooks you want to retrieve.
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
PARSIO_IO_PARSE_DOCUMENTTool to trigger parsing of a specific document. Use when you need to initiate parsing for a document that has already been uploaded or created in Parsio.
Input parameters
The unique identifier of the document to parse. This ID is returned when a document is created or uploaded.
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
PARSIO_IO_SKIP_DOCUMENTSTool to skip multiple documents in a mailbox by providing document IDs. Use when you need to mark documents as skipped rather than parsing them.
Input parameters
Array of document IDs to skip. Each ID must be a valid document identifier.
The unique identifier of the mailbox containing the documents to skip.
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
PARSIO_IO_UPDATE_MAILBOXTool to update mailbox settings including name, email prefix, and processing options. Use when you need to modify configuration settings for an existing mailbox.
Input parameters
Update the mailbox's display name.
The unique identifier of the mailbox to update.
Modify the email prefix associated with the mailbox.
Email alerts frequency in hours. Specifies how often to receive alerts.
Enable or disable automatic email address collection.
Store or ignore email attachments. Set to true to process attachments, false to ignore them.
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
PARSIO_IO_UPDATE_WEBHOOKTool to update an existing webhook's configuration. Use when you need to modify webhook settings like URL, event type, or activation status.
Input parameters
Unique identifier of the webhook to update
Webhook URL endpoint that will receive webhook payloads
Trigger event type for the webhook. Options: 'doc.parsed', 'doc.parsed.flat', 'doc.fail', 'doc.received', 'table.parsed'
Whether the webhook is active or disabled
Table identifier, required only for 'table.parsed' events. Leave empty for other event types.
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
PARSIO_IO_UPLOAD_FILETool to upload and parse PDF, HTML, CSV, TXT, DOCX, RTF or XML files (max 20MB) to a mailbox. Use when you need to submit a file to Parsio for automated data extraction.
Input parameters
File to upload and parse. Supported formats: PDF, HTML, CSV, TXT, DOCX, RTF, or XML. Maximum file size: 20MB.
Custom payload data that will be included in the parsed JSON output as __meta__ field. Useful for linking the document with external databases (e.g., {'order_id': '12345', 'customer': 'John Doe'}).
The unique identifier of the mailbox where the file will be uploaded
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 Parsio.io.
Build on Nagent
Connect Parsio.io 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 Parsio.io, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Parsio.io is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Parsio.io is connected, you configure its 24 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Parsio.io 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 Parsio.io event fires, the agent kicks off automatically.
Every Parsio.io 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 Parsio.io ships with 24 pre-built ai document extraction actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Parsio.io together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Parsio.io-based workflows tailored to your business.