I know this is an older thread, but chiming in as I’ve dealt with something similar. Maybe it can help someone who stumbles across this thread
My experience with using a 3rd party image uploader on a Webflow form (not the built in image uploader under the Business account tier) is that it all works with Zapier and the CMS while using an “Image” type field in the Collection.
Here’s is a demo site I built awhile back that does just this: https://profile-directory.webflow.io
- Signup with a fake email address
- Upload a profile picture via the 3rd party service
- Then fill out the native Webflow form
- Submit the native Webflow form
So what happens, in this specific case, is that when you use a 3rd party service (in this case, I’m using Uploadcare), they handle uploading the image to their servers and then return to you a url of that uploaded image.
I then stuff that returned url (to the uploaded image) into a hidden form field.
Then…when you submit the form (after filling out the profile info) it also submits that hidden field with the url in it.
This all gets triggered in Zapier, which then creates a Webflow CMS entry in my Profiles Collection.
The CMS Collection has an “Image” field type that stores this url:
When I looked closely at this, it “appears” that the image shown within my Collection Item is really just a link to an uploaded image on Webflow.
My assumption is that if you create a live Webflow item from Zapier - and I’m assuming this applies to any API request, from any tool, into Webflow - and…
- one of those fields is an Image field
- and the data you pass into Zapier for that url is nothing more than plain text
Webflow will assume that’s a plain text url, download the image from that url, upload it to their servers, and put that url (to their servers) in the CMS field.
Not sure if this is how it works with a Webflow Business account and their native image uploader…