Changelog

Follow up on the latest improvements and updates.

RSS

Fixed changes in LinkedIn's website
This version fixes the auto-capture of
  • Company name
  • Job title
  • Location
that was broken on certain profiles by a recent change in Linkedin's website.
Fixed changes in LinkedIn's website
This version fixes the auto-capture of
  • Company name
  • Job title
that was broken on certain profiles by a recent change in Linkedin's website.
NEW - Twitter to Notion
Peopletonotion has arrived in Twitterland! You are now able to capture from any Twitter profile:
  • Name
  • Profile picture
  • Location
  • Bio
  • Bio Link
  • Twitter profile link
NEW - Bio & BioURL fields
For Linkedin Profiles:
  • The Linkedin
    About
    section can now be captured with Peopletonotion under the new field
    Bio
    .
  • The new Personal Link field in Linkedin, which more and more people, are starting to use can be captured with Peopletonotion under the new field
    BioURL
    .
Minor improvements
  • Improved capturing of the
    Company
    field on Linkedin profiles. This field wasn't being captured for a very small number of profiles, this has been fixed.
Fix bug where the "Add to Notion" button was appearing multiple times in MacOS
Extra credits for the free plan
  • 15 credits is not enough to test PeopleToNotion? You can now get additional free credits by referring PeopleToNotion to your friends or colleagues.
2-way sync: know when a contact is already in your Notion CRM
  • Now if a Linkedin profile is already in your Notion CRM, or as soon as you add it, a button "Open in Notion" will appear. Click on it to go directly to that contact's Notion page in a new tab.
  • For this to work you need to set up the
    URL
    field in your extension settings.
Contact pages titles are now hyperlinks to Linkedin
  • You can now simply click on any Notion contact page title to open their LinkedIn profile in a new tab
Improved onboarding
  • users are now directly prompted to use the provided template while logging in, without having to manually set page-level permissions)