Hey ​@Jos,
 

Can you post screenshots of Data In and Data Out, the error as well as how each Zap step is configured for us to have more context?

Hi there,

Thanks for the reply. Laura here picking this one up, I would be happy to help further!

 From what’s visible, it’s not completely clear whether the LinkedIn step in your Zap is using an uploaded image file or a direct image URL — both options can affect how Zapier processes the request, so I’ll cover both possibilities below.

The error message you’re seeing (You passed {raw: true} in request – the response.content property is not available) typically indicates that Zapier switched into a raw or streaming mode when sending data to LinkedIn. This usually happens when the step includes a media file or a link that Zapier treats as binary data, which prevents the normal response parsing.

Here’s how this relates to your setup and how to fix it:

1. If an image file is being passed
   When Zapier tries to upload a file directly (for example, from Google Drive or another app’s “File” output), it handles the data as a binary stream. That’s what triggers the {raw: true} mode and causes the LinkedIn action to fail.

2. If an image URL is being passed
   LinkedIn requires a publicly accessible image URL — one that anyone can open in a browser without logging in. If the URL points to a restricted file or a temporary blob, Zapier can’t fetch it properly, which can lead to the same error.

3. Next steps to try

   • Test the LinkedIn action without an image first. If the post goes through successfully, the issue is with how the image is being handled.

   • If you’re using an image URL, make sure it’s a direct, public URL (e.g., an image hosted on an open server, or a Drive file with “Anyone with the link” sharing enabled).

Once Zapier can access the image as a standard URL, the LinkedIn post should go through and the {raw: true} error will stop appearing.

Please give that a try and let us know which setup you’re using (file vs. URL) — that will help us confirm the next steps more precisely.

Hi 

When I remove the images url it works. I have the zapier woocommerce plugin. The image url gives multiple image urls. Probable that causes the problem. How do I change that?

Hey ​@Jos,

Try using Formatter → Text → Split Text action to split by comma. Put comma(,) in the Separator.

Hope it helps.

Hi It  splits the image url's but still the error. When a product has only one image the zap works correct.

Hi ​@Jos 👋

Just came across this and it seems the Content - Image URL field is expecting to receive a single URL. Are you wanting to include all the images in the post, or just the first one? 

If you only want one image then, in the LinkedIn action you’d need to map the field containing the first image url output by that Formatter action. That should ensure that only one image is supplied and help avoid the error.

And if you’re wanting to include multiple images in a single post, I’d suggest first reaching out to our Support team to submit a feature request for that functionality. Then try exploring an API Request action to publish the update with all the images. It looks like their UGC Post API endpoint may be the one you’d need to use for that. 

Happy to lend a hand if you give the above a try and get stuck, just let me know! 🙂