OtherReal-timeUpdated May 2026

ImageKit

ImageKit image CDN with on-the-fly resize

ImageKit is the image and video CDN focused on on-the-fly URL-based transformations — Cloudinary-class functionality at typically lower price, with simpler pricing model. Tiny Command exposes two actions, no triggers: Upload File (push an image or video from a URL or file with optional folder, tags, transformations), List Files (paginated browse of uploaded media with filters). The connection uses ImageKit public + private keys from the dashboard plus the URL endpoint. The on-the-fly URL transformations are the standout: ik.imagekit.io/{endpoint}/tr:w-300,h-200,fo-auto/{path} resizes to 300x200 with auto focal point. For workflows that need image-CDN with transformations at a friendlier price than Cloudinary, ImageKit is the right pick.

Connect ImageKit

0triggers

2actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything ImageKit can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
List ImageKit Files	Returns paginated uploaded media with filters by folder, tag, type. Useful for media-inventory or "find all images uploaded last week" cleanup workflows.	2 fields	View →
Upload to ImageKit	Uploads an image or video from URL or base64 with optional folder, tags, on-upload transformations. For "AI-generated image → upload to ImageKit for URL-based transformations + CDN delivery" workflows.	4 fields	View →

Recipes

Pre-built ImageKit workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

ImageKit → Slack alerts

AI-triage every ImageKit event, ping the right channel only when it matters.

ImageKit → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

ImageKit → Notion database

Turn ImageKit into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect ImageKit once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every ImageKit field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the ImageKit integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect ImageKit to Tiny Command?

Open the Tiny Command workflow builder, drop in a ImageKit node, and click Connect. Authorize ImageKit once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What ImageKit triggers does Tiny Command support?

Tiny Command focuses on outbound actions for ImageKit today. Use Tiny Command's universal Webhook or Schedule trigger to start ImageKit workflows, then run any ImageKit action you need.

What ImageKit actions can I run from a workflow?

2 ImageKit actions are available out of the box, covering other operations like "List ImageKit Files". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the ImageKit integration real-time?

ImageKit actions execute synchronously inside your workflow. Tiny Command waits for ImageKit's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use ImageKit with Tiny Command?

No. Every ImageKit trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any ImageKit API endpoint directly.

How much does the ImageKit integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The ImageKit integration itself has no per-app surcharge.