Documint is a document generation platform that allows you to create dynamic documents from templates.
Documint is a document generation platform that allows you to create dynamic documents from templates. On Nagent, Documint is exposed as a fully-configurable documents integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Documint into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Documint 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 Documint 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 Documint, with input parameters and output schema. Drop these into any step of an agent built in Helix.
DOCUMINT_CREATE_DOCUMENTTool to merge data into a template to create a document (PDF generation). Send JSON data with template variables in the request body to generate a PDF document. Returns a URL to the generated PDF (valid for 24 hours).
Input parameters
Key-value pairs where keys are token names in the template (e.g., {{name}}, {{email}}) and values are the data to merge. The structure depends on your specific template requirements. Values can be strings, numbers, booleans, or null.
Use the active version of the template. Set to false to use the draft version. Default is true.
Generate a preview document (watermarked). Set to true for testing without consuming API credits. Default is false.
The unique identifier of the template to use for document generation. This is a 24-character hexadecimal string that can be obtained from the List Templates action.
Comma-separated list of template field names to watch for changes. Use this to track which fields are being updated.
Comma-separated list of template field names to ignore during the merge process. Fields listed here will not be replaced in the generated document.
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
DOCUMINT_DELETE_TEMPLATETool to permanently delete a single template by its ID. Use when you need to remove an outdated or unused template; ensure the template ID is correct before calling.
Input parameters
The unique identifier (MongoDB ObjectId) of the template to delete. Obtain this from list_templates or get_template actions.
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
DOCUMINT_GET_TEMPLATETool to retrieve a single template by its ID. Use when you need to fetch details of a specific template before generating documents.
Input parameters
The unique identifier of the template to retrieve. This is a 24-character hexadecimal string returned by the List Templates action.
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
DOCUMINT_LIST_DOCUMENTSRetrieves documents from the authenticated user's Documint account with optional pagination. Returns a list of documents with their IDs, names, associated templates, and timestamps. Use this to view previously generated documents or to find document IDs for further operations. Supports page and limit parameters for paginated results.
Input parameters
Page number to retrieve (1-indexed). Defaults to 1 if not specified.
Maximum number of documents to return per page (max 200). Defaults to the API's default if not specified.
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
DOCUMINT_LIST_TEMPLATESTool to list all templates in the authenticated user's account. Use after obtaining a valid API key.
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
DOCUMINT_UPDATE_TEMPLATETool to update a single template by its ID. Use when you need to modify an existing template's settings or layout after fetching its current details.
Input parameters
CSS styles for the template.
HTML content/body of the template. Supports Handlebars syntax for dynamic content.
New name for the template.
PDF rendering options for the template.
Unique identifier of the template to update. Obtain from list_templates or get_template.
HTML template for the page footer.
HTML template for the page header.
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 93 agents privately built on Nagent that already use Documint.
Build on Nagent
Connect Documint 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 Documint, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Documint is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Documint is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Documint 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 Documint event fires, the agent kicks off automatically.
Every Documint 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 Documint ships with 6 pre-built documents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Documint together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Documint-based workflows tailored to your business.