Skip to main content

Anyone know what's going on here? Why am I getting "Security Check Required".

Capture.jpg


Hi @Desirea

This doesn't appear to be related to Zapier. Can you clarify?



Sure, I have a zap that takes my Facebook posts and pins them onto a Pinterest board. They are coming through with "Security Check Required" on Pinterest. I cannot figure out why things I pin using Zapier are showing "Security Check Required" instead of the title of the post (or video) or nothing (which would be better).



@Desirea

Ok, let's try get this fixed.

Can you show us a screenshot of how you have the step that posts to Pinterest setup.



Here's the screenshot of the Pinterest setup.

image.png

image.png

image.png

image.png


I really appreciate the help!



@Desirea

Hmm, everything looks to be setup correctly there so what I’m going to do is flag this for someone on the Zapier Community team to look at. They might have a clue what’s going on and can escalate to the support team if needed.

Someone should be in contact with you soon.



Thanks David! I appreciate it.




Any follow up on this? It looks to me like when Pinterest is trying to crawl the URL you are passing to it (in this case a FB URL?) the URL is passing this "Security Check Required" as the title via opengraph etc.

This would not be a Zapier thing then, and instead a FB/Pinterest thing. However, the URL you are passing is it supposed to be a facebook URL or is facebook hijacking the link and running it through their servers? If it's the later you might be able to use a formatter step to trim the facebook server from the URL and maybe unencode the link URL to pass it to pinterest cleanly.




@Desirea it looks like our support team responded to the email you sent in about this but that you have yet to reply. Any updates here? Were you able to get this resolved? Let us know!



Hi, I’m having the same issue.  I set up a Zap where my Facebook posts (from my FB business page) automatically push to my LinkedIn Business page.  The post on LinkedIn says “Security Check Required”.  I’ve attached screenshots of my setup, but everything seems to look right?

 


Hello! I’ve got the same setup as Dgordon, and am getting the same result. Here’s my result screenshot attached. I’m going to poke around in facebook settings, makes me wonder if it’s some facebook security thing. And I may try the inverse zap, if there is an inverse zap that goes from linkedin to facebook


Hi folks! We’ve seen a few users with a similar issue though we haven’t yet confirmed a solution. There are a couple of things that that have solved the issue for other users. 

 

The first is that in the Zap action (eg post to LinkedIn), make sure that as many fields as possible are completed. So, for LinkedIn, make sure that you are completing  fields such as Content Title, Description, Image URL and Content URL.

 

 

The second possibility is that it’s a security check that’s related to Facebook specifically. In the context of Facebook, a security check is a pop-up Captcha image (random words or letters) that you see when you attempt to add new friends or communicate with friends who aren't on your Friends list. You should be able to remove this check by doing the following:

  1. Log in to your Facebook account
  2. Complete a task that causes the Captcha to appear, such as sending a friend request to a new friend.
  3. Click the "Verify your account" link that appears in the Captcha box. This will open another pop-up window. This window will ask you to confirm your account by mobile phone number.
  4. Select your country from the "Country Code" pull-down menu. Enter your mobile phone number in the "Phone Number" field and then click "Confirm." A code will be instantly sent to your mobile phone and the pop-up window will navigate to the "Confirm" window.
  5. Enter the code you received via text message in the "Confirm" window's "Code" field. Click the "Confirm" button to save your changes. Your Facebook account has now been confirmed and the security check will be turned off.

As I said, we’re still working to nail down the exact cause of this issue, so I can’t guarantee that these will work, but we know that it’s fixed the issue for some users. If you do have success with either method, please let us know!