Delete a file after the workflow completesURL
The file starts as uploaded file ID. DELETE /v1/files/:file_id. Map public access removed to the next step and keep the file ID beside the run for cleanup.
- Reviewed by
- GetFileURL technical team
- Updated
- Input
- uploaded file ID
- Action
- DELETE /v1/files/:file_id
- Output
- Public access removed
What this page answers
It turns a file already inside a workflow into a direct public URL that another API can fetch.
- Reviewed by
- GetFileURL technical team
- Last updated
Make the file handoff visible.
A useful recipe shows four things: file in, upload request, returned URL, and cleanup handle.
Capture the file
Start from uploaded file ID and keep the original content type when possible.
Upload and parse JSON
Keep the upload response visible as workflow data, not hidden inside a side effect.
Send onward
Pass the returned URL to public access removed and store the file ID for cleanup.
Validate the URL before the destination retries.
Most automation file issues are caused by a URL that looks fine in a browser but fails from a server-side API call.
Direct response
The URL should return file bytes, not an app preview, permission page, or redirect loop.
Useful headers
Content type, size, and disposition should match what the destination expects.
Enough retention
Expiry should account for queue delays, async processing, and retry branches.
Copy the same upload shape into code
curl -X DELETE https://api.getfileurl.com/v1/files/file_8ks41p \
-H 'Authorization: Bearer $GETFILEURL_KEY'Common questions
What does this recipe solve?
It turns a file already inside a workflow into a direct public URL that another API can fetch.
Should the URL be permanent?
Not by default. Use the shortest retention window that gives the destination enough time to fetch the file.
What should I log?
Log the returned URL, file ID, content type, size, expiry, and destination response status.