n8n Integration with ImageKit.io

n8n is a workflow automation platform with a visual, drag-and-drop interface that lets you connect apps and automate tasks without writing code. It runs in the cloud or on your own servers and connects to hundreds of other apps and services, as well as n8n's built-in AI features.

The official ImageKit community node @imagekit/n8n-nodes-imagekit brings your ImageKit media library into n8n. This lets you make ImageKit the single source of truth for your media and automate how files move between ImageKit and the rest of your tools, all from a single workflow. The node source code is available on GitHub.

The node connects your ImageKit media library to n8n so your team can automate everyday media tasks without writing code.

• Upload and import: Add images and videos to ImageKit from another app or directly from a URL.
• Organize files and folders: Move, copy, rename, and structure your media library automatically.
• Search: Find any asset using filters and Lucene-like search syntax.
• Tagging: Add tags and labels, including AI-generated tags, to keep your library easy to browse.
• Bulk operations: Update or clean up many files at once instead of one by one.
• Cache purge: Keep your delivered images up to date across the web.
• Usage monitoring: Track your storage and bandwidth consumption.
• Account operations: Manage origins, URL endpoints, custom metadata fields, and saved extensions.
• Event triggers: Start workflows automatically when something happens in your account, such as a new file upload.

Only owners can install community nodes. Once installed, every member of your n8n instance can use the node in their workflows. The node requires n8n 1.85.x or later; to discover and install it from the nodes panel as a verified community node, you need n8n 1.94.0 or later (both n8n Cloud and self-hosted instances).

You can also install community nodes from the command line or from environment variables. Refer to the n8n community nodes installation guide for more details.

In n8n, go to Settings > Credentials, create a new credential of type ImageKit API, paste your ImageKit private key, and save.

For webhook triggers, create a separate credential of type ImageKit Webhook API and enter your webhook signing secret. The trigger node uses this secret to verify that incoming webhook payloads are authentic.

The ImageKit node provides complete coverage of the ImageKit API. Select a Resource and Operation from the dropdowns in the node configuration panel.

• File. Upload, update, get details, delete, copy, move, rename, publish/unpublish, and bulk operations (bulk delete, bulk add/remove tags, bulk remove AI tags).
• Asset. List and search assets with filters, pagination, sorting, and Lucene-like search syntax.
• Folder. Create, delete, copy, move, rename folders and check bulk job status.
• File Version. List, get, delete, and restore file versions.
• Metadata. Get metadata by file ID or from a URL.
• Custom Metadata Fields. Create, list, update, and delete custom metadata field definitions.
• Purge Cache. Purge CDN cache and check purge status.
• Account. Get account usage statistics.
• Account Origin. Create, list, get, update, and delete origins.
• Account URL Endpoint. Create, list, get, update, and delete URL endpoints.
• Saved Extension. Create, list, get, update, and delete saved extensions.

Refer to the ImageKit API reference for detailed request parameters and response formats for each operation.

The ImageKit Trigger node starts workflows when events occur in your ImageKit account. Configure it to listen for specific event types such as file uploads, updates, and video processing completions.

To set up a webhook trigger, add the ImageKit Trigger node to your workflow and use the Events dropdown to choose which events you want to listen for. Configure the ImageKit Webhook API credential with your webhook signing secret, then activate the workflow to register the webhook URL. Finally, copy the generated webhook URL and add it in the Webhooks section of your ImageKit dashboard.

The trigger node automatically verifies incoming webhook signatures to ensure deliveries are authentic and haven't been tampered with. This is enabled by default, and we recommend keeping it on in production. You can disable it with the Verify Signature toggle during development if needed.

For more details on webhook events and payloads, refer to the ImageKit Webhooks documentation.

Ready-to-use n8n workflow templates to get started quickly. Import any template into your n8n instance by copying its JSON and pasting it into Workflows > Import from URL / JSON.

Browse all templates in the sample-workflows directory on GitHub.

Keep an eye on your ImageKit consumption before it affects your bill. On an hourly schedule, this workflow pulls your current billing-month usage (storage, bandwidth, video units, extension units, and original cache) and checks each metric against a threshold you configure. When any limit is breached, it posts a single consolidated Slack alert showing each metric's value with a progress bar; when everything is within limits, it exits quietly without sending anything. View template →

Automatically moderate every new upload so unsafe content never stays live. The workflow listens for the ImageKit file.created webhook, downloads the newly uploaded asset, and passes it to a GPT-4o vision model (via OpenRouter), which returns a structured verdict with is_nsfw, confidence, and reason fields. Flagged assets are unpublished in ImageKit right away, while clean assets pass through untouched. View template →

Keep your delivered images fresh whenever content changes in your CMS. Triggered by a Contentful Asset.publish webhook, the workflow recursively scans the event payload for every ik.imagekit.io URL and issues a cache purge request for each one. It posts a Slack message per URL with the purge request ID, then polls ImageKit until each purge finishes and updates the matching Slack message with the result. View template →

• ImageKit API documentation
• ImageKit Webhooks documentation
• n8n community nodes documentation
• n8n credentials documentation
• Node source code on GitHub
• npm package