Workflow recipes for file to URL
Recipes show the working path: where the file starts, how upload happens, which JSON fields to map, and when to expire or delete the URL.
- Reviewed by
- GetFileURL technical team
- Updated
- Start
- file generated by app, API, or automation
- Middle
- upload and parse url, file_id, metadata
- End
- send onward, expire, or delete
What this page answers
Yes. Docs explain the endpoint. Recipes explain a specific workflow, source file, mapping step, and cleanup point.
- Reviewed by
- GetFileURL technical team
- Last updated
Start from the workflow failure you already have.
Each recipe is narrow on purpose. The copy should match the exact file, platform, and downstream job the builder is trying to fix.
Upload n8n binary data and get a public URL
Send n8n binary data to GetFileURL and return a direct public URL for OCR, AI, webhooks, or HTTP Request nodes.
Turn a Zapier form upload into a CDN URL
Convert Zapier form files and attachments into direct public CDN URLs that the next Zap action can send to an API.
Convert a Make webhook file into a URL
Use a Make HTTP module to upload a webhook file, buffer, attachment link, or decoded Base64 source and return a direct URL with file_id, content_type, and expires_at.
Host an AI-generated image long enough for the next API
Upload generated images, get a direct image URL, and keep it reachable for moderation, vision, editing, or publishing APIs.
Send a PDF to OCR with a direct public URL
Upload a PDF invoice, contract, or report and pass an OCR-ready public URL with application/pdf headers, file_id, expires_at, and delete_url.
Recipes also cover cleanup, not only upload.
The strongest automation content explains what happens after the URL is created.
Give social publishing APIs a direct media URL
Turn generated images, screenshots, or exports into direct media URLs that social publishing tools can fetch during async posting jobs.
Turn a Base64 image source into a direct URL
Decode a Base64 image payload into bytes, upload it as multipart form data, and return a public CDN URL with content type, expiry, and file ID for cleanup.
Expire a workflow file URL after 24 hours
Create a temporary public file URL that lasts long enough for OCR, AI, webhook, or publishing jobs and then expires automatically.
Delete a file URL after the workflow completes
Store the file ID from upload and call the delete API after the destination confirms it fetched the public URL and finished processing.
Common questions
Are recipes different from docs?
Yes. Docs explain the endpoint. Recipes explain a specific workflow, source file, mapping step, and cleanup point.
Why include cleanup recipes?
Public file URLs should have an end state. Expiry and deletion are part of the product value, not a footnote.
Can I use these recipes without a native integration?
Yes. Any platform that can send an HTTP multipart request and parse JSON can use the upload API.