PDF4me provides robust, secure, and scalable APIs for document generation, manipulation, and management, enabling easy integration and automation across various applications.
PDF4me provides robust, secure, and scalable APIs for document generation, manipulation, and management, enabling easy integration and automation across various applications. On Nagent, Pdf4me 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 Pdf4me into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Pdf4me 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 Pdf4me 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 Pdf4me, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PDF4ME_CONVERT_TO_PDFTool to convert various document and image formats to PDF. Handles one file per call; multi-file PDFs require multiple calls followed by a separate merge step. Conversion permanently removes interactive form field editability — retain the original file as backup, and ensure all form fields are populated before converting. Use when you need to transform base64-encoded files into PDFs before further processing.
Input parameters
Document object with base64 data and optional filename. Must include `docData` field containing base64-encoded file bytes — URLs and file paths will fail validation.
List of conversion option sets. If omitted, default conversion is applied.
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
PDF4ME_EXTRACT_TEXTTool to extract embedded text from text-based PDFs using PDF4me's ExtractResources endpoint. Use when you need to retrieve searchable text content from PDFs for analysis or processing. This tool does not perform OCR; for scanned or image-only PDFs, use OCR endpoints instead.
Input parameters
Base64-encoded PDF file content from which to extract text.
PDF file name with .pdf extension for document identification.
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
PDF4ME_FILL_PDF_FORMTool to fill PDF form fields programmatically using JSON or XML data. Use when you need to generate reports or populate forms from various data sources with mail merge functionality. Supports filling multiple documents from a list of data collection items.
Input parameters
Additional metadata string for the form filling operation.
Stringified JSON array of field data objects to fill. Must be a JSON string, not a JSON array object. Example: '\[{"Name":"John Doe","Email":"john@example.com"}\]'
Output format specification. Typically 'PDF' for PDF output.
Metadata in JSON string format for advanced configuration.
Array of form data objects with field name-value pairs matching PDF form fields. Each object contains key-value pairs where keys are form field names and values are the data to fill. Example: \[{"Name":"John Doe","Email":"john@example.com"}\]
Data type for input data. Use 'JSON' for JSON data or 'XML' for XML data.
PDF template filename with .pdf extension to be filled.
Base64-encoded PDF form template content.
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
PDF4ME_READ_BARCODES_FROM_IMAGETool to read and extract barcode or QR code data from image files (JPG/PNG). Use when you need to decode barcodes from images for data extraction or verification. Supports various barcode types including QR codes, Code128, DataMatrix, and more.
Input parameters
Image file name with extension (e.g., 'barcode.png', 'scan.jpg').
Image file format: jpg or png.
Base64-encoded image file content containing barcodes to be read.
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 30 agents privately built on Nagent that already use Pdf4me.
Build on Nagent
Connect Pdf4me 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 Pdf4me, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Pdf4me is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Pdf4me 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 Pdf4me 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 Pdf4me event fires, the agent kicks off automatically.
Every Pdf4me 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 Pdf4me 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 Pdf4me together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Pdf4me-based workflows tailored to your business.