Add one Webhooks by Zapier action to your Zapier flow: POST the file with your API key and the response hands the next step a live, shareable URL.
Any supported file works. Code: HTML · ZIP · JSON · JSONL · YAML · TOML · XML · SQL · MD · INI · ENV · PROPERTIES · LOG · WASM
There is no app to install from the Zapier directory. The built-in Webhooks by Zapier action sends the request: configure it like this and later steps read the URL from the response.
# Zapier: add a "Webhooks by Zapier" action, event "Custom Request"Method: POSTURL: https://upload.tf/api/v1/uploadHeaders: x-api-key: YOUR_UPLOADTF_KEYData Pass-Through: noFile: (file object mapped from an earlier step; Zapier sends it as the multipart part named file)Data: name=weekly-report # Later steps read Data Url from the response.Sign in, open the dashboard, and create a key. API access is included with paid plans, and your key works immediately.
Add a Webhooks by Zapier action with the Custom Request event, set the method to POST, build a multipart body with the file from an earlier step, and add the x-api-key header.
The response body carries data.url, the live link. Map it into the next step: a Slack message, a spreadsheet row, an email, a CRM field.
The file your Zapier flow just produced becomes a URL in the same run, with no manual upload step in the middle.
Downstream apps rarely take file attachments, but every one of them takes a link. One stable https URL fits any field.
Send a PUT with the same name and the page updates at the same URL, so a recurring job keeps one permanent link.
Not yet. This page uses the built-in Webhooks by Zapier action, available on plans that include webhooks. Everything shown runs against the documented public API.
The upload endpoint accepts an HTML page or a ZIP of a static site and publishes it at its own URL. That covers the reports, dashboards, and generated pages most flows produce; other file types work through the browser uploader.
Create an API key in your dashboard and send it in the x-api-key header of the HTTP step. Keep the key in your workspace credentials or environment variables, never in the URL.
The API is included with paid plans, which also raise size limits and keep links live longer. You can try the flow manually first with the free uploader on this page, no account needed.
Map the file object from the trigger or an earlier action into the request body. Zapier passes hydrated file objects to webhook actions, and the upload endpoint reads the multipart part named file.
See every workflow recipe, or, if you run a platform, the embed API.
