RenderForm is a user-friendly automation and design tool that enables the creation of templates and images with custom content such as images, texts, and QR codes.
RenderForm is a user-friendly automation and design tool that enables the creation of templates and images with custom content such as images, texts, and QR codes. On Nagent, Renderform is exposed as a fully-configurable images & design integration that any agent can call — 7 actions, and API key authentication. No code is required to wire Renderform into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Renderform to automate the kinds of tasks images & design 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 Renderform 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 Renderform, with input parameters and output schema. Drop these into any step of an agent built in Helix.
RENDERFORM_CREATE_PDF_FROM_URLTool to create a PDF from any website URL with customizable page format and auto-expiration. Use when you need to generate a PDF snapshot of a webpage.
Input parameters
URL of the website to convert to PDF; must include http:// or https://
Output format of the PDF
Automatically delete the PDF after this many seconds (1–604800, max 7 days)
Wait time in milliseconds before capturing the PDF (0–5000)
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
RENDERFORM_DELETE_RESULTTool to delete a render result (image/PDF) by its identifier. Use when you need to remove a previously generated image or PDF from the system.
Input parameters
Unique identifier of the result to delete (e.g., req-b71ba6dc-0bfc-40ed-8fe6-7b84e880691a)
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
RENDERFORM_GET_RESULTTool to retrieve detailed information about a specific render result by its identifier. Use when you need to check the status or get the full details of a previously generated image or PDF.
Input parameters
Unique identifier for the render result 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
RENDERFORM_LIST_FONTSTool to retrieve all available fonts including Google Fonts and custom uploaded fonts. Use when you need to list fonts for text rendering.
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
RENDERFORM_LIST_RESULTS_V2Tool to list all rendered images and PDFs with pagination support. Use when retrieving results from the v2 API with filtering by template or batch.
Input parameters
Page number to retrieve (0-indexed). Use 0 for the first page.
Number of results per page (1-50). Maximum allowed is 50.
Filter results by batch identifier. Returns only results from the specified batch render request.
Filter results by template identifier. Returns only results generated from the specified 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
RENDERFORM_LIST_TEMPLATES_V2Tool to get a list of all your templates with metadata and preview links. Supports pagination and filtering by name and tags.
Input parameters
Filter by template name
The page number for pagination (0-indexed)
The number of results per page (max 50)
Filter by tags (array of strings)
Identifier of the source template used to create a 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
RENDERFORM_TAKE_SCREENSHOTTool to capture a screenshot of a website with given dimensions. Use when you need a visual snapshot of a page with optional wait time before capture.
Input parameters
Complete URL of the website to capture; must include http:// or https://
Width of the screenshot in pixels
Height of the screenshot in pixels
Optional wait time before capture, in milliseconds (500–5000)
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 50 agents privately built on Nagent that already use Renderform.
Build on Nagent
Connect Renderform 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 Renderform, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Renderform is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Renderform is connected, you configure its 7 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Renderform 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 Renderform event fires, the agent kicks off automatically.
Every Renderform 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 Renderform ships with 7 pre-built images & design actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Renderform together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Renderform-based workflows tailored to your business.