CloudConvert is a file conversion service supporting over 200 formats, including audio, video, document, ebook, archive, image, spreadsheet, and presentation formats.
CloudConvert is a file conversion service supporting over 200 formats, including audio, video, document, ebook, archive, image, spreadsheet, and presentation formats. On Nagent, CloudConvert is exposed as a fully-configurable file management & storage integration that any agent can call — 9 actions, and API key authentication. No code is required to wire CloudConvert into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use CloudConvert to automate the kinds of tasks file management & storage 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 CloudConvert 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 CloudConvert, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CLOUDCONVERT_CREATE_EXPORT_GOOGLE_CLOUD_STORAGE_TASKTool to create a task to export files to a Google Cloud Storage bucket. Use after conversion when you need to store results directly into GCS. Ensure service account credentials have the proper permissions.
Input parameters
Filename/path for the exported file in the bucket.
The ID of the task to export. Multiple task IDs can be provided as a list.
The Google Cloud Storage bucket name.
The Google Cloud Project ID (`api-project-...`).
Prefix for exported files in the bucket when exporting multiple files.
The private key of the service account (PEM-encoded).
Service account client email (e.g., `my-sa@api-project-123456.iam.gserviceaccount.com`).
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
CLOUDCONVERT_CREATE_EXPORT_S3_TASKTool to create a task to export files to an Amazon S3 bucket. Use after conversion when you need to store results directly into S3. Ensure AWS credentials have s3:PutObject (and PutObjectAcl if using non-default ACL) permissions.
Input parameters
S3 ACL for stored objects. Defaults to 'private'.
S3 object key (filename and path) for storing the file. Supports printf-style placeholders for multiple files, e.g., 'file-%d.pdf'.
The ID of the task to export, or a list of task IDs.
The Amazon S3 bucket where to store the file(s).
S3 region identifier (e.g., 'us-west-2' or 'eu-west-1').
S3 object tags as key–value pairs.
Custom S3 API endpoint URL. Overrides default built from region. Use for S3-compatible services.
Additional S3 metadata as key–value pairs (e.g., 'x-amz-meta-*').
Prefix to prepend to the S3 object key when exporting multiple files.
Value for the 'Content-Type' header. Auto-detected if omitted.
AWS access key ID with `s3:PutObject` permission.
Value for the 'Cache-Control' header (e.g., 'max-age=172800').
AWS session token for temporary (STS) credentials.
AWS secret access key.
Value for the 'Content-Disposition' header (e.g., 'attachment' or 'inline').
Server-side encryption algorithm to use (AES256 or aws:kms).
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
CLOUDCONVERT_CREATE_WEBHOOKCreates a new webhook to receive CloudConvert event notifications. Use this when you need to be notified about job status changes (created, finished, or failed) via HTTP POST requests to your server.
Input parameters
The target URL where CloudConvert will send webhook notifications. Must be a publicly accessible HTTPS URL.
Event type to subscribe to. Valid values: 'job.created' (when a job is created), 'job.finished' (when a job completes successfully), 'job.failed' (when a job fails).
Optional custom payload object to include in each webhook notification. Useful for passing context like user IDs or request identifiers.
Optional secret used to sign webhook payloads via HMAC-SHA256. Use this to verify that webhook requests originate from CloudConvert.
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
CLOUDCONVERT_DELETE_WEBHOOKPermanently delete a webhook by its ID. Use this when you no longer need to receive event notifications for a specific webhook. The webhook ID can be obtained from the create_webhook or list_webhooks actions.
Input parameters
The numeric ID of the webhook to delete. Obtain this from the create_webhook or list_webhooks 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
CLOUDCONVERT_LIST_OPERATIONSTool to list all possible CloudConvert operations with their available options and engine details. Use when you need to discover what operations are available, check operation requirements, or filter by input/output formats before creating tasks.
Input parameters
Comma-separated list of additional data to include. Options: 'options' (operation parameters), 'engine_versions' (available engine versions).
Filter operations by input format. Only returns operations that accept this format as input.
Filter operations by output format. Only returns operations that produce this format as output.
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
CLOUDCONVERT_LIST_SUPPORTED_FORMATSTool to list all supported conversion formats, engines, and options. Use when you need to discover available conversions before creating tasks.
Input parameters
Include additional data: options and/or engine_versions.
Set to true to include alternative conversion types.
Filter to include only conversions with this engine name.
Filter to include only conversions with this input format.
Filter to include only conversions with this output format.
Filter to include only conversions with this engine version.
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
CLOUDCONVERT_LIST_TASKSList all CloudConvert tasks with their status, payload and results. Use this tool to: - Monitor conversion task progress and status - Find tasks by status (waiting, processing, finished, error) - Filter tasks by job ID to see all tasks in a specific job - Retrieve task results and output file URLs - Debug failed conversions by checking error codes and messages Tasks are automatically deleted 24 hours after completion.
Input parameters
Page number to retrieve (1-indexed). Use with per_page for pagination through large result sets.
Filter tasks by job ID. Only returns tasks belonging to the specified job.
Filter tasks by status: 'waiting' (queued), 'processing' (in progress), 'finished' (completed successfully), or 'error' (failed).
Comma-separated list of additional data to include in response. Options: 'retries' (retry tasks), 'depends_on_tasks' (task dependencies), 'payload' (submitted configuration).
Order results by a column with optional direction. Format: 'column_name \[asc\\ | desc\]'. Common columns: 'created_at', 'ended_at'.
Number of tasks per page. Default is 100, maximum is 500.
Filter tasks by operation type, e.g., 'convert', 'import/url', 'import/s3', 'export/url', 'export/s3'.
Filter tasks by creation datetime in ISO 8601 format. Supports comparison operators like \[gte\] for date ranges.
Filter tasks by completion datetime in ISO 8601 format. Only applies to finished or error status 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
CLOUDCONVERT_LIST_WEBHOOKSTool to list all webhooks. Use when you need to retrieve existing webhooks before managing or inspecting them.
Input parameters
Page number to return (default: 1)
Number of webhooks per page (default: 100)
Filter results to webhooks with this URL
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
CLOUDCONVERT_SHOW_USERRetrieves the current authenticated user's CloudConvert account information. Returns the user's ID, username, email, remaining conversion credits, and account creation date. Requires the 'user.read' scope. Useful for verifying authentication and checking available credits.
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 92 agents privately built on Nagent that already use CloudConvert.
Build on Nagent
Connect CloudConvert 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 CloudConvert, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, CloudConvert is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once CloudConvert 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 CloudConvert 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 CloudConvert event fires, the agent kicks off automatically.
Every CloudConvert 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 CloudConvert ships with 9 pre-built file management & storage actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching CloudConvert together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build CloudConvert-based workflows tailored to your business.