n8n
HTTP Request nodeTurn n8n binary data into public CDN URLs for HTTP Request nodes, OCR APIs, AI steps, and webhooks.
Upload workbench ready for a file.
Send binary files, attachments, exports, and Drive links from n8n, Make, Zapier, Pipedream, Airtable, or Google Drive. Get back a direct URL, content type, file size, expiry, and JSON metadata.
Turn n8n binary data into public CDN URLs for HTTP Request nodes, OCR APIs, AI steps, and webhooks.
Convert scenario-generated files into direct URLs the next Make module or external API can read.
Return clean file URLs from Zaps without temporary attachment links or redirect pages.
Pass hosted files through code steps, webhooks, and API actions with stable HTTPS URLs.
Replace expiring attachment URLs with stable public links for downstream APIs and automations.
Avoid Google Drive share-link redirects when APIs require direct file access and correct headers.
Each recipe starts with a file trapped inside a workflow and ends with an API-safe URL plus metadata the next step can trust.
Private, binary, or redirecting workflow-generated files become direct public links with JSON metadata, expiry, and deletion controls.
No redirect page. No app-only attachment. No guessing whether the next API can fetch it.
Files start inside apps, automations, and APIs. GetFileURL turns them into a stable handoff.
GetFileURL sits between workflow files and APIs that require public file access, correct headers, and predictable cleanup.
The returned URL is checked against the next API before the workflow moves on.
Accept files from apps, APIs, forms, webhooks, Base64 payloads, and automation builders without configuring S3, IAM, CORS, or CDN behavior.
Every upload returns a clean HTTPS file URL, content type, file size, expiry, and metadata that downstream tools can parse without redirect pages.
Set expiry, delete files by API, inspect delivery problems, and keep workflow-generated files from becoming unmanaged public storage.
Use the upload file to URL API with multipart or Base64 inputs. The response returns the URL, file ID, filename, size, content type, and expiry in automation-ready JSON.
curl -X POST https://api.getfileurl.com/v1/files \ -H 'Authorization: Bearer $GETFILEURL_KEY' \ -F 'file=@invoice.pdf' \ -F 'expires_in=7d'{ "file_id": "file_8ks41p", "url": "https://cdn.getfileurl.com/f/file_8ks41p/invoice.pdf", "name": "invoice.pdf", "size": 482193, "content_type": "application/pdf"}Use it for AI-generated images, PDFs, OCR, invoices, social publishing, support screenshots, and any downstream API that rejects temporary Drive links, private attachments, or redirect pages.
Work inside one tool, then fail when an external API tries to fetch them.
Drive, form, and app links often return an HTML page instead of the file bytes.
OCR, AI, and document APIs need content type, length, and range behavior to be predictable.
Workflow-generated files need expiry and deletion so public links do not live forever.
Check reachability, redirects, content type, content length, range request support, expiry, and public access before files move through brittle automation chains.
Default expiry, per-upload expiry, delete-by-API, upload webhooks, usage alerts, and abuse handling turn generated files into governed infrastructure.