Short answer: Drop the "ImageKit → Upload to ImageKit" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
File (URL or base64) file | string | Required | — |
File Name fileName | string | Required | — |
Folder Path folder | string | Optional | — |
Tags (comma-separated) tags | string | Optional | — |
{"file": "{{trigger.file}}","fileName": "{{trigger.fileName}}","folder": "{{trigger.folder}}","tags": "{{trigger.tags}}"}
{"url": "https://ik.imagekit.io/your_id/photo.jpg","name": "photo.jpg","size": 200000,"width": 1600,"fileId": "abc","height": 1200,"fileType": "image","thumbnailUrl": "https://ik.imagekit.io/.../tr:n-ik_ml_thumbnail/photo.jpg"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.