You can send an image uploaded through a Webflow form to Zapier, but Webflow’s native CMS does not support direct file uploads via forms. However, you can work around this limitation using third-party storage services and Zapier.
1. Understand Webflow File Upload Limitations
- Webflow forms can include File Upload fields, but they do not connect directly to Webflow CMS.
- File uploads are only available on Business plans and above, and the uploaded files are stored with a temporary link in submissions.
2. Use Zapier to Capture the File URL
- When a form is submitted, Webflow can send data to Zapier via Webhooks or the Form Trigger in the Webflow Zapier integration.
- The file upload field is included in the form data as a URL pointing to the uploaded file (hosted on Webflow’s CDN).
3. Store the File on External Storage (Optional but Recommended)
- Since Webflow-hosted file URLs may expire, it's a best practice to:
- Send the file URL to a service like Google Drive, Dropbox, or Cloudinary through Zapier.
- Save the permanent upload link generated by that service.
4. Create a CMS Item via Zapier
- Use a “Create Live Item” action in Zapier (Webflow app) to create a CMS item.
- Include fields such as title, description, and importantly, Image.
- For the Image field, use the permanent URL (from step 3). If using the Webflow-hosted file link directly and not saving elsewhere, note there’s a risk of broken images over time.
5. Ensure the CMS Collection Supports External Image URLs
- Your CMS collection should have at least one Image field or Rich Text field where an image URL can be added.
- Webflow processes image URLs into hosted versions, so the external image must be accessible to do this properly.
Summary
Yes, you can send an image uploaded through a form to Zapier and display it via Webflow CMS, but it requires a workaround. Webflow form uploads must be routed through Zapier, optionally stored elsewhere, and then linked when creating a CMS item.