Send files in Zaps

Sometimes, you may need to send a file in an action step of your Zap, like adding an attachment to an email or uploading a file to your cloud storage app. To send a file in Zap, you must use:

• A file object.
• A URL link that supports files.
• If an app supports it, you can create a text (.txt) file directly in the field.

If your field is a file field, you will see a file icon in the input box.

Note

Some apps have multiple fields with similar names, such as Attachments and Attachments File. If your Zap fails with an error when sending a file, check that you are mapping to the field that contains the actual file data, not a field that contains metadata like file names or IDs. Try remapping to a different attachment-related field if available.

File formats

File objects

File objects are the bundles of data that represent the actual file. This is different from the name of the file or other file attributes. For example, the actual image of an apple is the file object, while the file name might be "apple.jpg".

URL links

If you're using a URL link to a file, it must be:

• Publicly accessible: it cannot require a login to access it.
• A direct download link: the URL must point directly to the file, not to a webpage that displays or previews it.

You can test your URL link by opening it in a private or incognito browser window. If it prompts you to download a file, the link can be used. If it prompts you to log in to an app, loads directly in the web browser instead of downloading, or results in an error code, the link cannot be used.

Note

Common URLs that do not work in file fields:

• Google Drive sharing links (e.g., drive.google.com/file/d/.../view): Use the Web Content Link field from a Google Drive step instead, or convert the sharing URL to a direct download format.
• Slack file URLs: These require authentication and are not publicly accessible.
• Cloud storage preview links: Used by apps like Dropbox or OneDrive. They open a preview page instead of downloading the file directly.

If your Zap fails with a 403 error or the file arrives empty, check that your URL is a direct download link and does not require authentication.

Text files

Some apps may create a text (.txt) file if you enter text values into a field that accepts files.

Check if a previous step provides a file

If a previous step has a File field with an "(Exists but not shown)" value, that is a file object. Zapier displays this message because file data is downloaded on demand when your Zap runs, rather than stored in the editor. If a previous step has an Attachments field, it may have a file object or a URL link to a file that you can use.

Send a file in your action step

Limitations

• Some file fields may not accept text.
• Files larger than 100 MB may result in a timeout error. Zapier also has a 150 MB limit for downloading (hydrating) files from connected apps.
  • If a file exceeds these limits, your Zap may fail with errors such as "ENOSPC: no space left on device" or a 400 Bad Request, rather than a clear file size message.
  • For large files, consider using a direct integration between apps or splitting the file into smaller parts.
• File references from test or sample data can expire. If your Zap was working during testing but fails with "Access Denied," "object not found," or missing file errors in production, re-test the trigger step to refresh the sample data.
• Some apps may uselist fields to send multiple files.
  • You must map each attachment to a separate list field.
• If you enter multiple file objects or URLs as comma separated values in each field, Zapier will only send the first in each field. Additional files are silently ignored.
  • This is different from regular file fields, where comma-separated files are bundled into a .zip archive. If your Zap is missing attachments, check whether the action step uses list fields.