Getting started
From nothing to a working setup. Five steps, about ten minutes, and one of them happens in Chrome rather than on this site.
1. Create your account
Sign up with an email address and a password. You get a 7-day trial with no card, and a workspace is created for you. A workspace is the billing and team boundary; everything else — profiles, automations, lead pages — belongs to it.
Prices are in euro, excluding VAT, and billed per connected LinkedIn profile. The seller on your invoice is Profectify LLC.
2. Install the extension
LeadAdapter does its LinkedIn work through a Chrome extension running in your own browser, under your own session. Nothing on LinkedIn happens without it, so this step is not optional.
It is not in the Chrome Web Store. Download it from Settings, then Extension, in your dashboard, and load it into Chrome yourself in developer mode — the extension page has the four steps and the reasoning behind distributing it this way.
3. Pair the extension
In LeadAdapter, open Settings and then Extension, and generate a pairing code. It is six digits and it is valid for 10 minutes.
Click the LeadAdapter icon in Chrome, type the code, and connect. The extension receives a device token of its own and stores it locally. That token is the only credential it ever holds — it is not your LinkedIn session and it is not your password.
4. Connect your LinkedIn profile
Straight after pairing, the extension reads your own LinkedIn profile in an open LinkedIn tab and reports the result. That creates the LinkedIn profile record in LeadAdapter — the thing caps, automations and jobs all hang off.
You need to be signed in to LinkedIn in the same Chrome profile, with a LinkedIn tab open. If nothing appears, that is almost always why.
5. Grant consent
Before anything runs, the profile's own owner has to grant consent explicitly. The screen states what LeadAdapter will do as you, and inside which caps. Until it is granted, every write is refused with a reason that says so.
This matters most on a team or in an agency: consent is granted by the person whose LinkedIn account it is, not by whoever administers the workspace.
What to do next
New profiles start in the least autonomous useful setting: anything that would land uninvited in a stranger's inbox waits for you to approve it, while public actions run inside the caps. Leave it there until you trust a template.
- Build a comment-to-DM automation on a post you are about to publish.
- Make a lead page for whatever the DM is going to send them to.
- Read the governance page, so the caps and the approval queue are not a surprise.
- Connect your agent, if you use one, through the MCP server.
If nothing is happening
Almost every "it did not send" is one of four things, and the dashboard's extension card tells you which.
- Chrome is closed, or there is no LinkedIn tab open. Nothing runs without both.
- The profile is outside its sending hours. The action is queued, not lost, and it carries the time it will run.
- The action is waiting in the approval queue because of the autonomy setting.
- A cap for that channel is spent for the day. It resets at midnight in the profile's own timezone.
Every cap, limit, timeout and tool name on this page is read from the running product when the page loads. If the software changes, this page changes with it.