TinyPNG uses smart lossy compression techniques to reduce the file size of your WebP, JPEG, and PNG files.
TinyPNG uses smart lossy compression techniques to reduce the file size of your WebP, JPEG, and PNG files. On Nagent, TinyPNG is exposed as a fully-configurable images & design integration that any agent can call — 5 actions, and API key authentication. No code is required to wire TinyPNG into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use TinyPNG 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 TinyPNG 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 TinyPNG, with input parameters and output schema. Drop these into any step of an agent built in Helix.
TINYPNG_GET_COMPRESSION_COUNTTool to retrieve the number of compressions made this month. Use when you need to monitor your TinyPNG API usage.
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
TINYPNG_SHRINK_AND_GET_IMAGE_IDTool to shrink an image and return its TinyPNG image ID. Use when you need only the compressed image identifier from the API response Location header.
Input parameters
Publicly accessible URL of the image to compress.
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
TINYPNG_TINIFY_COMPRESS_AND_STORE_IN_AZURECompress an image using the Tinify API and upload the optimized result directly to Azure Blob Storage in a single operation. The image is first compressed by Tinify, then uploaded to the specified Azure Blob URL using the provided SAS token. Use this when you need to optimize images and store them in Azure without intermediate steps. Supports JPEG, PNG, and WebP image formats.
Input parameters
Publicly accessible URL of the source image to compress. Supports JPEG, PNG, and WebP formats.
Full Azure Blob Storage URL with a valid SAS (Shared Access Signature) token that has write permissions. The URL should include the target container, blob path, and SAS query parameters (sv, se, sr, sp, sig). Required SAS permissions: Write (w) and Create (c).
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
TINYPNG_TINIFY_OUTPUTTool to retrieve a compressed image by its image ID. Use after compressing an image to download the result.
Input parameters
Identifier for the uploaded and compressed image (returned by the TinyPNG shrink API).
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
TINYPNG_TRANSFORM_IMAGETool to transform a compressed image by resizing, converting format, preserving metadata, or storing to cloud storage. Use when you have an image ID from a previous compression and need to apply transformations.
Input parameters
The unique identifier for the compressed image output, obtained from the Location header of the compress response.
Cloud storage options to save image directly to S3 or GCS. Each upload counts as additional compression.
Options for resizing the image.
Options for converting the image format.
Metadata to preserve: 'copyright', 'creation', 'location' (JPEG only). Does not count as additional compression.
Transformation options for stylistic changes.
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 53 agents privately built on Nagent that already use TinyPNG.
Build on Nagent
Connect TinyPNG 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 TinyPNG, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, TinyPNG is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once TinyPNG is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop TinyPNG 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 TinyPNG event fires, the agent kicks off automatically.
Every TinyPNG 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 TinyPNG ships with 5 pre-built images & design actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching TinyPNG together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build TinyPNG-based workflows tailored to your business.