LinkedIn Lead Enrichment files a lead into HubSpot, Monday or Slack.
You are on a profile in your own browser. One click files that person into the CRM your team already runs, under the properties they already maintain.
The app is not released yet, and we will write to you on the day it goes live.
What the app does.
It turns a profile you are already reading into a CRM record, in one click, with no retyping.
The app runs in your browser and stays asleep until you press the control on the page. When you press it, we read the profile in front of you, check the CRM for a record that already matches, and show every field before anything is saved.
We write through the platform's own API, under the permissions granted at install. We map each value onto a property the team already maintains, so a lead lands in the record the reports are built on rather than in a list nobody opens.
- Reads the profile page you already have open
- Matches against the contact records the CRM already holds
- Writes through the HubSpot, Monday and Slack APIs
- Shows every value before anything is saved
What one run looks like.
Every moment below waits for a person, and we are building it that way so nothing can run while you are away from the desk.
You open a profile
You are signed in as yourself, in your own session, reading a page you were going to read anyway.
You press the control
The control sits on the profile page, nothing happens until you press it, and nothing is sent anywhere before that.
We read the page
We read the fields on the profile in front of you: the name, the headline, the current role, the current employer and the profile address.
We check for a match
We look in the CRM for a contact carrying that name or that profile address, so a second run updates a record instead of creating a twin.
You see the fields
Every value is shown beside the property it is about to fill. You can edit any of them, and you can close the tab without writing anything.
You approve the write
We write the approved values through the platform API, and we record what was written and when.
Which fields it writes.
We write to the standard objects, using the property names your team already sees in the CRM. The list below is what the first release writes, and nothing outside it.
Contact record
Created when the CRM holds nobody matching, and updated when it does.
- full_name
- the name as it reads on the profile
- job_title
- the current role, written out rather than abbreviated
- company_name
- the current employer
- linkedin_url
- the address of the profile you had open
- lifecycle_stage
- Lead, unless the CRM already holds a later stage
- contact_owner
- you
Company record
Written only when the profile names a current employer.
- company_name
- the employer named on the profile
- company_domain
- the domain the CRM already holds for that company
- association
- the contact, linked to the company record
Audit trail
Written on every run, so a colleague can reconstruct what happened.
- source_url
- the profile you had open
- written_by
- the person who approved the write
- written_at
- the moment the write was approved
This is the field map we are building to, and we will update this page if it changes before launch.
What this does not do.
We wrote the list below as commitments rather than as a feature list. If one of them ever stops being true, we change this page before we change the app.
- No database of people.
- We hold no store of profiles, no shared pool of contacts and nothing to sell on. The only copy of a record is the one that lands in the CRM you already run.
- No background process.
- Nothing runs on a schedule and nothing runs while the tab is closed. We are building it to act when a person presses the control, and to be idle for the rest of the day.
- It reads one page.
- We read the profile already open in the session you are already signed into. We do not walk a connection list, we do not open other pages, and we do not touch an inbox.
- No write without approval.
- We show every field before it is saved, and a run nobody approves writes nothing at all. Closing the tab is a valid way to cancel.
- No invented numbers.
- The app has no install count, no rating and no launch date, because it has no users yet. We will publish each of those on the day it becomes true.
- No lookup behind the click.
- What lands in the CRM is what was on the page in front of you, plus what the CRM already held. Nothing is fetched to fill a gap.
Get early access.
Two fields, and we will write to you when the app is live. We do not send anything else, and we do not pass the address on.