LinkedIn Login without signup

I’m trying to get people to login Via LinkedIn but every time the button is clicked bubble tries to sign the user up for my site. Any ideas how I can log someone in and NOT sign them up every time they click the button? If someone could provide screenshots/examples - that would be awesome!


You could connect to the LinkedIn API directly and set it up to log the user in. Once you’re comfortable with APIs, that’s a pretty quick solution. Of course, there might be a pre-built plugin for this too - I haven’t investigated.

@martinsd it’s been a while, but I’ve been able to set up LinkedIn successfully in the past without this issue.

Perhaps you can share a few screenshots or a video recording (Screencastify works well) of your current setup? That’d help to pinpoint things.

Thanks for your help Dan!

I’ve attached an image of the workflow. My thought from this workflow is that the user clicks the button and then bubble goes to create the user based on the information from LinkedIn. If the user already exists, bubble returns the User element and then it should go to the portal page. What happens in reality is that the user clicks the button, bubble goes to create the account but stops when it realizes the user already exists - it does not log the person in and it does not pass them to the portal page.

Thanks again for your help!!

Got it. When you have the signup with the social network action (in this case, LinkedIn), that effectively creates a user account and logs them in. You have a “Create an account for someone else” action, which is not necessary here. The example below should help:

Let’s say our current user is Jane.

In this case, Jane wants to sign up/log in using a social network, specifically LinkedIn. By having a button on the page that utilizes that action, it will do one of the following:

  1. If Jane already exists in your system (with a Bubble created account) and is logged in but she has never logged in using LinkedIn, she will then “pair” her LinkedIn with her Bubble account. In the future, she will be able to log into the same account using either her Bubble credentials or her LinkedIn.
  2. If Jane does not have an account in your Bubble database but triggers the log in with a social network action, that will create a new account in Bubble, which she can access in the future using her login with LinkedIn account. (In theory, she could also login using Bubble credentials, but you would need to do a password reset).
  3. If Jane has already created an account and authenticated with LinkedIn, she will be logged in to her account that exists in your Bubble account by using her LinkedIn credentials.

All of these actions effectively log the user in.

Remember: the create a user account for someone else action you have creates an account independent of the Signup/Login with LinkedIn action. Bubble will not let you have two uses with the same email address, since that is the primary login identifier.

1 Like

Hi Dan,

Would you have time to answer a couple of questions about this?

  1. I want to have a User login via normal email address but have a ‘Connect LinkedIn’ button on their logged in dashboard which pairs with their Linkedin account - would this be possible using this plugin? It sounds like this would work given your notes above even though I would never allow them to login with Linkedin.

  2. Emmanual’s notes on this are: “create an ‘app’ with linkedin, being careful with the redirect URL so that it matches well the page where you put the action” - What is the meaning of this? Is this just ensuring that if a development URL then the linkedin app also has the development URL?

1 Like

Quick responses since I’m on the road.

  1. Yes, it’s possible to have a login via normal email address and LinkedIn. Though I’d recommend having a few validation steps (ex. ensuring the user isn’t creating a duplicate account by Doing a search for users = email).
  2. For the redirect URL reference, this is a common part of the structure for sign on via an API workflow. It’s essentially to ensure that users come from a valid origin and that they are sent back to the proper place in your app as well. You’ll want to save both the development URL and the live URL within LinkedIn (since both environments have different URLs).

Ok, that makes sense. Thanks!

1 Like