Automation · via the API
Put the cut in your pipeline.
One call where the file arrives, one PNG where it leaves. No connector to install and nothing new to log into.
Not writing code? Workflows runs the same steps in your browser
Plainly
There are no connectors
This page used to show Dropbox, Drive and Zapier tiles. None of them were real, and finding that out after signing up is worse than reading it here.
- What exists
- An HTTP endpoint that takes an image and returns a transparent PNG, and a batch endpoint for a set.
- What that replaces
- The step in your process where a person downloads a file, cuts it, and uploads it again.
- Where it runs
- Wherever your files already land: an upload handler, a queue worker, or a nightly job.
- What it costs
- API access is on Pro and Enterprise. The browser tools stay free.
- If you would rather not
- Workflows does the same job without an integration: drop a folder, chain the steps once, get one archive back. See workflows
The pipeline
Four steps, two of them yours
Numbered because the order is the whole design: nothing downstream can start before the cut returns.
- 01 A file arrives in your app A seller uploads a product shot, a photographer syncs a folder, a form takes an avatar.
- 02 You POST it One request, bearer auth, multipart body. Seconds, not milliseconds, so put it behind a job.
- 03 A transparent PNG comes back With its alpha intact, ready to sit on whatever ground the destination needs.
- 04 You store and publish it Your bucket, your CDN, your listing. This step is yours and always was.
It is one call
Read the reference, wire it into the step where files already arrive, and stop cutting by hand.