Available integrations
Start with the verified n8n node or public Zapier app. For Make and other tools, the guide shows the exact built-in HTTP module settings—no imaginary custom app required.
n8n — verified node
Upload binary or base64 data, set optional expiry, and return a public CDN URL.
Zapier — public app
Upload files, create intake links, list files, and delete files from Zaps. Start with a workflow built around your file source.
Make — HTTP module
Use the exact multipart/form-data recipe and map the returned public URL into the next module.
Pipedream
Use a Node.js or Python step to turn buffers, base64, or webhook files into public URLs.
Airtable
Permanent URLs for Airtable attachments — fixes the expiring-URL problem.
ClickUp
Public, permanent URLs for ClickUp file attachments.
Google Sheets
Pipe upload URLs into Sheets via Apps Script or Zapier.
Webhooks
Turn multipart attachments, temporary source URLs, or base64 payloads into durable CDN links.
Why integrate via API rather than build into each tool
The FilePost API is small enough that any tool with an HTTP request block can talk to it — that's literally every automation platform that exists. We publish dedicated apps where the platform supports them (Zapier, Pipedream) and tutorials where it doesn't.
Best Zap templates to start with
The most useful Zap templates are the ones that turn temporary attachments into permanent URLs and then store or notify with that URL.
- Gmail attachment to FilePost to Google Sheets: archive inbound documents, invoices, resumes, or assets and store the permanent CDN URL in a spreadsheet.
- Typeform upload to FilePost to Slack: collect files from forms and post a clean, permanent link to a team channel.
- Google Drive new file to FilePost to Airtable: create CDN-backed public URLs for files added to a folder and save them on Airtable records.
- New Airtable attachment to FilePost: replace expiring Airtable attachment URLs with permanent FilePost links.
- Webhook file URL to FilePost to CRM: receive a file URL from any app, upload it to FilePost, then attach the permanent URL to HubSpot, Pipedrive, or another CRM.
Don't see your tool?
If it can fire an HTTP request, it can call FilePost. Pattern: POST multipart form data to https://upload.filepost.dev/v1/upload with X-API-Key header, get JSON back with the permanent URL. Full API docs.
Choose the shortest working path
Use the route that matches the file you already have. Start a real upload when you want proof, use n8n or Zapier when the workflow already lives there, or follow the Make recipe when an HTTP module is the simplest fit.
Try one real upload
Get a public URL first, then decide whether the API or an integration belongs in your workflow.
Copy the REST request
Use cURL, Python, Node.js, or any HTTP client with the same upload contract.
Upload base64 JSON
Send base64 content from an AI, webhook, or low-code step and receive the same public URL response.