Short answer: Drop the "ImgBB → Upload to ImgBB" 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 |
|---|---|---|---|
Image URL image | url | Required | Image URL |
Image Name name | string | Optional | Image Name |
Expiration (seconds) expiration | number | Optional | Auto-delete after N seconds (min 60). Leave empty for permanent. |
{"image": "{{trigger.image}}","name": "{{trigger.name}}","expiration": "{{trigger.expiration}}"}
{"data": {"id": "abc123","url": "https://i.ibb.co/abc123/image.png","size": 524288,"delete_url": "https://ibb.co/abc123/delete","display_url": "https://i.ibb.co/abc123/image.png"},"success": true}
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.