Add one Node.js code step to your Pipedream 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 component to install. A short Node.js code step sends the upload with axios and form-data, then returns the live URL for the steps after it.
// Pipedream: add a Node.js code stepimport FormData from "form-data"import axios from "axios" export default defineComponent({ async run({ steps }) { const form = new FormData() form.append("file", steps.trigger.event.body, { filename: "report.html", contentType: "text/html", }) form.append("name", "weekly-report") const res = await axios.post( "https://upload.tf/api/v1/upload", form, { headers: { "x-api-key": process.env.UPLOADTF_KEY, ...form.getHeaders() } }, ) return res.data.data.url // => https://weekly-report.upload.tf },})Sign in, open the dashboard, and create a key. API access is included with paid plans, and your key works immediately.
Add a Node.js code step, build a FormData with the file from your trigger or a previous step, POST it with the x-api-key header, and return data.url from the step.
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 Pipedream 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 a plain Node.js code step, which every Pipedream workflow supports. 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.
Whatever the code step returns is available to later steps as its export. Return data.url and reference it from the next action, for example a Slack or email step.
See every workflow recipe, or, if you run a platform, the embed API.
