Conversion Tools is an online service that offers a fast and easy way to convert documents between different formats, like XML, Excel, PDF, Word, Text, CSV, and others.
Conversion Tools is an online service that offers a fast and easy way to convert documents between different formats, like XML, Excel, PDF, Word, Text, CSV, and others. On Nagent, Conversion Tools is exposed as a fully-configurable documents integration that any agent can call — 11 actions, and API key authentication. No code is required to wire Conversion Tools into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Conversion Tools 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 Conversion Tools 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 Conversion Tools, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CONVERSION_TOOLS_CONVERT_EXCEL_TO_HTMLConvert an Excel (.xlsx) file to HTML table format. Use when you need to transform spreadsheet data into an HTML representation. Provide either a file upload or a public URL to the Excel file. Returns a task_id that can be used to check the conversion status and download the result once complete.
Input parameters
Excel file to upload for conversion. Required if file_url is not provided.
Optional conversion settings. Example: {'sheet': 'Sheet1'} to convert a specific sheet.
Public URL to the Excel file to convert (e.g., 'https://example.com/data.xlsx'). Required if file is not provided.
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
CONVERSION_TOOLS_CONVERT_WORD_TO_TEXTConvert Word documents (.doc/.docx) to plain text (.txt). The action uploads the document, waits for conversion to complete (up to ~60 seconds), and returns the task status with a URL to download the converted text file. Use when you need to extract text content from Word documents for further processing.
Input parameters
Binary content of the Word document (.doc/.docx) to convert. Mutually exclusive with 'file_url'.
Publicly accessible URL of the Word document (.doc/.docx) to convert. Mutually exclusive with 'file'.
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
CONVERSION_TOOLS_CREATE_TASKTool to create a new conversion task. This is the main endpoint for performing conversions across 100+ conversion types including XML, JSON, Excel, PDF, CSV, images, audio/video, and more. Use when you need to convert any supported file format or website. Counts against quota unless sandbox mode is enabled.
Input parameters
Public URL of the file or website to convert. Required for website conversions or when converting a file from the internet. Mutually exclusive with file_id.
Conversion type identifier in format convert.{source}_to_{target}. Choose from 59 supported conversion types including XML, JSON, Excel, PDF, CSV, images, audio/video, and more.
File ID returned by POST /files endpoint. Required when converting an uploaded file. Mutually exclusive with url.
Enable sandbox mode for unlimited testing without counting against quota. Returns mock data in 2-5 seconds. Useful for testing workflows before production use.
Webhook URL to receive task completion notification. The API will POST to this URL when conversion finishes.
Additional conversion-specific options. Examples: filename (output name), pages (page ranges like '1-5,7'), delimiter (CSV separator), quality (image quality), etc. Varies by conversion type.
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
CONVERSION_TOOLS_DOWNLOAD_FILEDownload a converted file from the Conversion Tools API using its file ID. Use this action after a conversion task completes successfully. The file_id is obtained from the task status response when status is 'SUCCESS'. Converted files are automatically deleted after 24 hours. Workflow: 1. Run a conversion task (e.g., convert_website_to_pdf) 2. Check task status until status is 'SUCCESS' 3. Use the file_id from the task response to download the result
Input parameters
Unique identifier (32-character hex string) of the converted file to download. Obtain this ID from a completed conversion task's response.
Optional filename for the downloaded file. If not provided, the filename will be extracted from the API response headers or derived from the file_id.
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
CONVERSION_TOOLS_GET_AUTH_INFOTool to get information about the authenticated user including email address. Use when you need to verify API credentials or retrieve the user's email.
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
CONVERSION_TOOLS_GET_CONFIGTool to get available conversion types and their configuration. Returns the list of all supported conversions with their options. Use this to discover what conversions are available and what parameters they accept.
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
CONVERSION_TOOLS_GET_FILE_INFOTool to get metadata about a file including size, name, and preview (for text files). Use when you need to retrieve information about a previously uploaded file. This does NOT count against your quota.
Input parameters
Unique identifier (32-character hex string) of the file to retrieve information about.
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
CONVERSION_TOOLS_GET_TASK_STATUSTool to get the status of a conversion task. Poll this endpoint until status is SUCCESS or ERROR. On SUCCESS, the response includes file_id which can be used to download the result file.
Input parameters
The task ID returned from task creation. A 32-character hexadecimal string uniquely identifying the conversion task.
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
CONVERSION_TOOLS_LIST_TASKSGet all tasks for the authenticated user (up to 50 most recent tasks). Use this action to retrieve conversion task history, check task statuses, or find completed tasks for downloading results. This does NOT count against your API quota. Filter by status to retrieve only tasks in a specific state (PENDING, RUNNING, SUCCESS, or ERROR).
Input parameters
Task status enumeration for filtering tasks.
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
CONVERSION_TOOLS_UPDATE_TASK_RETENTIONTool to update the retention mode for a task. Use when you need to change how long task files are kept before automatic deletion. Standard mode (standard_24h) retains files for 24 hours. TTL mode (ttl_15m) is for paid users only and deletes files after 15 minutes.
Input parameters
Unique identifier (32-character hex string) of the task to update. Obtain this ID from a conversion task response.
Retention mode for task files. 'standard_24h' (default) retains files for 24 hours. 'ttl_15m' (paid users only) retains files for 15 minutes and automatically deletes them afterward.
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
CONVERSION_TOOLS_UPLOAD_FILEUpload a file to the ConversionTools API for subsequent conversion operations. This action uploads a file and returns a file_id that can be used with other conversion actions such as convert_word_to_text, convert_excel_to_csv, convert_oxps_to_pdf, etc. Supported formats include: documents (DOC, DOCX, PDF, TXT, RTF), spreadsheets (XLS, XLSX, CSV), images (PNG, JPG, GIF, BMP), and various other file types.
Input parameters
Binary content of the file to upload. Can be provided as base64-encoded string or raw bytes.
Name of the file including extension (e.g., 'document.docx', 'spreadsheet.xlsx', 'image.png'). The extension determines how the file 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
No publicly available marketplace agent is found using this tool yet. There are 34 agents privately built on Nagent that already use Conversion Tools.
Build on Nagent
Connect Conversion Tools 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 Conversion Tools, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Conversion Tools is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Conversion Tools is connected, you configure its 11 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Conversion Tools 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 Conversion Tools event fires, the agent kicks off automatically.
Every Conversion Tools 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 Conversion Tools ships with 11 pre-built documents actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Conversion Tools together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Conversion Tools-based workflows tailored to your business.