What does FilePost do in a Zap?

FilePost accepts a file or public file URL and returns a durable public CDN URL plus file metadata for later Zap steps.

Do I need to write code to use FilePost with Zapier?

No. FilePost is a public Zapier app. Add its Upload File or Upload File From URL action and map the file from an earlier step.

Which FilePost Zapier action should I use?

Use Upload File when the previous app provides a Zapier file object. Use Upload File From URL when it provides a public or temporary file URL.

Zapier File Upload Integration — Turn Attachments into Public URLs

Published Zapier app Native file actions Permanent CDN URL output No code required

Start from the file you already have

Choose the source that matches your workflow. Each route ends the same way: FilePost returns a public URL that Sheets, Slack, Airtable, a CRM, or your own API can use immediately.

Upload new Gmail attachments to FilePost Archive invoices, resumes, reports, and inbound assets behind a durable URL. Upload new Google Drive files to FilePost Turn files added to a watched folder into CDN URLs for websites, tables, and downstream APIs. Upload new Slack files to FilePost Keep files shared in a workspace available to websites, tables, and downstream tools behind a durable URL.

Pick the action by input shape

Zapier apps expose files in two common shapes. FilePost supports both, so you do not need an intermediate download or formatter step.

Upload File: Use when the previous Zap step provides a file or attachment object.
Upload File From URL: Use when the previous step provides a public or temporary file URL.

Build, connect, and manage the workflow in Zapier

FilePost’s Zapier app also includes actions to list files, delete a file, and create a shareable intake link. One FilePost API key connects the account; the Zap editor handles field mapping and tests.

Build your FilePost workflow

Open the public FilePost app in Zapier to choose a trigger, add a FilePost action, and test the returned URL. Approved one-click templates will appear here as they are published by Zapier.

Build in Zapier

What comes back from FilePost

The FilePost step returns url, file_id, name, size, and content_type. Map url into the next Zap action. Keep file_id if the workflow may need to retrieve metadata or delete the file later.

Need the long-form setup instead? Follow the step-by-step Zapier file upload guide. Prefer code? Use the FilePost API reference.

Questions we actually get

Is FilePost publicly available in Zapier?

Yes. FilePost is a published Zapier app. You can find it in Zapier’s app directory and add its actions to new or existing Zaps.

Do I need Webhooks by Zapier?

No. Use the native FilePost app for normal file and URL uploads. Webhooks remain useful only when your workflow has a separate custom HTTP requirement.

Which field should I use after the upload?

Map the returned url field into the next action. It is the public CDN URL. Store file_id too if a later step needs to manage the uploaded file.

Do Zapier uploads count against my FilePost plan?

Yes. Each successful FilePost upload action counts as one upload against the connected account’s monthly quota.

The attachment is temporary. The URL doesn’t have to be.