LinkedIn Oauth profile data

[cmarchan]

Got my answer!

Thank you!

[richard18]

I just can’t figure out why I’m not able to pull the email address… what am I doing wrong?

I’ve run authentication workflow - I’m able to pull name and profile photo - but not the email - I’ve followed all directions 100%

please, someone help - I’m going to throw my laptop out the window

[anevski85]

Hey @richard18 I have exactly the same problem
Did you solve this issue or you already thrown the laptop out the window

[ChefThomas]

I have no idea why, but now it’s working

[ChefThomas]

I think I found the problem, @anevski85

above, this is what @neerja has:

At the end of “3. Email - initializing call…” there is the "GET “LINK” that looks like it’s ending with only 1 " ) "

BUT - there are TWO ))

This is the full Link:
https://api.linkedin.com/v2/emailAddress?q=members&projection=(elements*(handle~))

[anevski85]

Thank you @ChefThomas, it works now

[NigelG]

Haven’t been able to get LinkedIn to work …

Turns out you HAVE to have the www in the redirect (even though it works without) for Bubble to be able to process it correctly according to “the rules”.

[tim4]

Hello,

I’m having a strange issue where I can sign in/login the user using social network workflow under accounts (Image 1), but I when trying to get the API working from the plugin workflow section (image 2) it shows 401 “Invalid access token” response. (image 3).

Have been tearing my hair out all day with this. I need to collect user’s info through a result of a previous action which is from the plugin workflow.

Here’s the API:

[LWeiLi]

Been getting this as well, I’ve got the same configurations and it has been working for the past couple of months.

Just noticed last week that the token kept expiring, every couple of hours. (Not sure how to reproduce the issue, seems to happen at random)

Checking Linkedin’s Token time to live duration, it says it’s fine, so not sure what this is.

[LWeiLi]

This thread seems to also reference this error

LinkedIn API Connector V2 Settings Not Working, Postman Works Though

Having recent issues with this too, used to work fine. Having just revalidated the token in run mode (debug_mode=true), the token seems to stay valid for only a few minutes before the error shows up again. [image] This is despite Linkedin dev portal showing that the access token is still valid. [image] The weird thing is that users still can authenticate successfully and even retreive emails via https://api.linkedin.com/v2/emailAddress?q=members&projection=(elements*(handle~)) The error s…

[openocean.tampa]

I am having this error as well. Has anyone else confronted this and figured out the solution?

[openocean.tampa]

Did you manage to work this out?

[openocean.tampa]

Nvm… This actually worked for me:

LinkedIn Oauth profile data

Yes ensure that when you are mapping the image from the API you select, The “profilePicture displayimage -elements’s identifiers, identiers’s identifier” [Screen Shot 2021-02-26 at 7.54.14 AM]

[ahmed.khodeir.87]

hi there, are you using the API coonector, or bubble plugin to add the email to the same user in the database?

[vyomforsava]

Facing the same issue…

[ali.adel]

So, for those of you guys who have already managed to set up the API connection using bubble connector and are facing the same problem, I’ve come up with a solution that may help you guys out. It may not be pretty but it does the job and would potentially make you avoid these awkward situations where you have duplicate users, one signed up locally and the other via LinkedIn.

So here it goes:

Step 1: Use the signup/login with social media and then choose your API that you’ve already set-up

Step2: This is where the magic happens. You just need to use the action “assign a temp password” found under account actions

Step 3: You then update the user credentials using the email address you collect from your API call and the temp password (result of step 2)

Step 4: You want to make sure that you make changes to the user to fill in the profile fields that you gathered from your API call, such as first name, last name, and profile pic.

Step 5: You simply redirect the user to your confirmation page or home page

And just like that, you’ll have your user signed up in your database once and for all via LinkedIn, without the need to create any additional email fields. And each time they choose to log in, they’ll be using the same account (it won’t sign up the user again).

Practically speaking, users can also merge their accounts if they ever decide to log in via email and reset their password. In that case, they’ll have the option to login in locally with the new password and also via Linkedin (it’s always going to be the same account)

I’ve been struggling with the same problem for days now, so I thought I should instantly share it with you guys. Let me know if it helps!

[menae]

I’m getting this error, even token is set

Please help me, if it’s possibel

[menae]

[shenalyo]

Hi everyone,

I have posted the required API configurations to obtain the LinkedIn email address here: How to create a sign-in via LinkedIn and collect the primary email address on Bubble | by Shenal Harakh | Nov, 2022 | Medium

Let me know how you go!