Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

When creating a LinkedIn step with action event as “Create Share Update”, I am getting the below error:

The error "Cannot read properties of undefined (reading 'article')" suggests that the LinkedInCLIAPI step is trying to access a property called 'article' that doesn't exist in the input data. In your input data, there is no 'article' key, which is likely causing the issue. The error might be due to a misconfiguration in the Zap where the expected input fields do not match the actual data being passed from the previous step.

To resolve this, first, ensure that the fields in the LinkedInCLIAPI step are correctly mapped to the output of the previous step. Check if the 'article' field is required by LinkedInCLIAPI and if so, ensure that the previous step provides this data. You might need to modify the CodeCLIAPI step to include the necessary data or adjust the LinkedInCLIAPI step to use available data. Additionally, use Zapier's built-in "Test & Review" feature to verify that the data is being passed correctly between steps, and adjust the field mappings as needed.

What do I do?

Hi @mavillatamayo 

For us to have more info, post these screenshots:

  • how your Zap step is configured in EDIT mode showing the field mappings
  • the encountered error

 

@mavillatamayo 

Click the field labels to see tooltips that may provide more guidance.

Things to check.

  • Field: Content - Description
    • May have character limits
    • May have limits on special characters
  • Field: Content - Image URL

 

  • Field: Content - Description: How do I know the field has character limits? I’ve reduced the content to 50 words, and I still get same error.
  • Field: Content - Image URL: Image is already accessible.

@Troy Tessalone I’ve found that the error that Zapier is giving me is not about Content - Description. It is about Content - Image URL. The image is accessible and the url was correctly generated. Do you think this error could be related to LinkedIn API? Do I need to add a LinkedIn API action in the zap?

@mavillatamayo 

Post the image link you are testing with for us to check if it’s a properly formatted link.

You can check by copy/paste into a new/different private browser to see if it renders only the image.

@Troy Tessalone 

Yep, I have tried that, and it works. I am not sure why it doesn’t work in the zap.

Link1: https://drive.google.com/uc?export=view&id=1NK7zcEeh1yaZ_auafe2m-AyypB72vOEG

Link 2: https://drive.google.com/uc?export=download&id=1NK7zcEeh1yaZ_auafe2m-AyypB72vOEG

@mavillatamayo 

You can try turning the Zap ON and testing live.

Then check the Zap Runs history details to see the DATA IN/OUT for each step along with a LOGS tab that shows the underlying API request/response that may contain more info to help you troubleshoot: https://zapier.com/app/history/

Hi @mavillatamayo,

I just came across your post here and wanted to check in here to see how you’re getting on. Are you still running into the same issue here after publishing the Zap?

Please do let us know if you’re still in need of some help on this at all - happy to assist further! 🤗

Reply


Terms & Conditions