Comment on page
Let users log in with their LinkedIn accounts and fetch their profile details.
This workflow step allows you to integrate a LinkedIn authentication event when registering a new user, or logging in an existing user.
Allows the Bubble editor to verify the correct social platform to login/signup the user.
When adding dynamic data, this operator allows you to fetch and display content from a user’s connected LinkedIn account.
The unique ID of a users LinkedIn profile.
The first name of a user per their LinkedIn account.
The last name of a user per their LinkedIn account.
A user’s LinkedIn profile picture.
Add both your client ID and client secret key into the corresponding fields of your LinkedIn plugin.
After connecting your plugin, you’ll now need to add a redirect URL under the ‘OAuth 2.0 settings’ in your LinkedIn developer portal. This URL should be the same page in your app where the user originally selected to connect an account. Once a user has authenticated their account through LinkedIn, this is the page they’ll be redirected to.
After configuring your API and app settings, you can now use the ‘signup/login with social network’ step within a workflow. From the event dropdown menu, you’ll see an option to select the LinkedIn OAuth provider. This event can be added to an element like a login button.
After a user clicks this button, they’ll be redirected to a LinkedIn portal where they can verify their account, then be redirected back to the destination URL of your application.
Now, you can choose to display data from a user’s LinkedIn profile by selecting the ‘current user’s LinkedIn’ operator.
When signing a user up through LinkedIn OAuth, it’s possible to add an additional step to your workflow that makes changes to the current user account.
Within this workflow step, connect your database fields with the ‘current user’s LinkedIn’s’ operator.
Note: If a user is to revoke access between your app and their LinkedIn account, the link to each connected data field can break. It can be considered best practice to pull this data in dynamically rather than save it to your database.