DocuGenerate simplifies document generation by converting Word templates and JSON data into professional PDF files with ease. It supports automation of contracts, invoices, letters, certificates, and more, catering to both developers and non-developers. With an intuitive REST API and no-code integrations, it ensures seamless functionality for any scale.
DocuGenerate simplifies document generation by converting Word templates and JSON data into professional PDF files with ease. It supports automation of contracts, invoices, letters, certificates, and more, catering to both developers and non-developers. With an intuitive REST API and no-code integrations, it ensures seamless functionality for any scale. On Nagent, Docugenerate is exposed as a fully-configurable documents integration that any agent can call — 9 actions, and API key authentication. No code is required to wire Docugenerate into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Docugenerate 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 Docugenerate 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 Docugenerate, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DOCUGENERATE_DELETE_DOCUMENTTool to delete a document by ID. Permanently removes the document from storage. Use when you need to clean up generated documents or remove outdated files from DocuGenerate.
Input parameters
The unique identifier of the document to delete. Obtain this from the document generation response or by listing documents.
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
DOCUGENERATE_DELETE_TEMPLATETool to permanently delete a template by ID. Removes the template and all associated versions from storage. Use when a template is no longer needed.
Input parameters
ID of the template 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
DOCUGENERATE_DOCUMENT_GENERATETool to generate document(s) from a template by merging JSON data or uploading a data file. Use when you need to programmatically produce one or more documents and receive metadata including a download URL.
Input parameters
Merge data as an object (single document) or list of objects for multiple documents
Binary file (CSV/Excel/TSV) for bulk merge when `data` is not provided
Logical document name; supports merge tags when generating a single document
PDF URL(s) or Base64 data URIs to embed as attachments in the PDF
PDF URL(s) or Base64 data URIs to append after generated content. Ignored if invalid or unreachable. Only for PDF/PDF-A formats.
Insert a page break between combined documents when `single_file` is true
Output file name without extension; extension added automatically
Combine multiple documents into one file (true) or return a ZIP (false)
ID of the template to use
Output format; defaults to .docx. PDF/A variants supported
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
DOCUGENERATE_DOCUMENT_UPDATEUpdate a document's name/title in DocuGenerate. Use this to rename an existing document after it has been generated. Requires a valid document ID (obtained from document generation or listing) and the new name. Returns the updated document metadata including the document_uri for downloading.
Input parameters
The unique identifier of the document to update. Obtain this from the document generation response or by listing documents.
The new name/title for the document. This updates the document's display name (not the filename).
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
DOCUGENERATE_GET_DOCUMENTTool to retrieve a specific document by ID. Returns document metadata including name, format, template_id, and download URL. Use when you need to fetch details about an existing generated document.
Input parameters
ID 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
DOCUGENERATE_GET_TEMPLATETool to retrieve a specific template by ID. Returns template metadata including name, format, region, and configuration settings.
Input parameters
ID 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
DOCUGENERATE_LIST_DOCUMENTSTool to list all documents generated from a template. Results are ordered by created time in descending order. Use when you need to retrieve a list of previously generated documents for a specific template.
Input parameters
ID of the template that was used to generate the documents
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
DOCUGENERATE_TEMPLATE_GET_OR_LISTTool to retrieve or list existing templates. Use when needing template IDs and metadata before making updates or generating documents.
Input parameters
Page number to retrieve (starting at 1)
Number of templates per page
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
DOCUGENERATE_TEMPLATE_UPDATETool to update a template’s file and settings. Use after confirming the template ID and desired inputs.
Input parameters
Template identifier to update
The template file to upload (form field 'file')
Optional new name for the template
Processing region for the template (e.g., 'us', 'eu', 'uk', 'au')
Enable version history for the template
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 34 agents privately built on Nagent that already use Docugenerate.
Build on Nagent
Connect Docugenerate 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 Docugenerate, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Docugenerate is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Docugenerate is connected, you configure its 9 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Docugenerate 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 Docugenerate event fires, the agent kicks off automatically.
Every Docugenerate 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 Docugenerate ships with 9 pre-built documents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Docugenerate together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Docugenerate-based workflows tailored to your business.