Short answer: Drop the "Remove.bg → Remove.bg Remove Background" 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 | url | Required | Image URL. e.g. "https://example.com/photo.jpg" |
Output Size size | options | Optional | Output Size. Options: Auto, Preview (up to 625x400), Full (up to 25MP) |
Background Color bg_color | string | Optional | Leave empty for transparent |
{"image_url": "https://example.com/photo.jpg","size": "{{trigger.size}}","bg_color": "#FFFFFF or transparent"}
{"type": "binary","content_type": "image/png"}
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.