Task documentation
Task documentation
How do I get an AI to work LinkedIn and email together without risking my account?
A single task, answered directly.
Short answer
The General works LinkedIn through a real Chrome session you are already signed into, rather than through an unofficial API. Your credentials are never sent to DFX, because it acts inside the session on your own machine, and email runs from your own connected mailbox alongside it.
Before you start
- The Chrome tier installed. It runs as an extension in the browser you already use.
- You already signed in to LinkedIn in that browser. It works inside your session and cannot see a system you are not signed into.
- A clear view of your own risk. Automating any platform carries account risk that is yours, not ours, and no tool removes it.
Steps
- 1Install the extension and sign in to the workspace.
- 2It acts inside the sessions you are already signed into, so credentials for those sites never leave your browser.
- 3It reads pages, navigates and extracts what it was asked for, scoped to the sites the job needs and refused elsewhere.
- 4Email steps run from your connected mailbox in the same sequence, so both channels share one record and one stop condition.
How you know it worked
One record per person showing both channels, and one reply on either channel stops the whole sequence rather than only its own half.
What this does not do
Stated here rather than discovered later
- It is bound by what your session can do. It is not a back door to data your account cannot see.
- Banks, brokerages and payroll sites are blocked in the extension's own source, not by a policy document. That is deliberate and not configurable.
- It does not remove platform risk. A site that changes its layout can break a job, and the General reports the break rather than continuing on a guess.
What this rests on
Related tasks
Last reviewed 2026-08-24. One of 5 task pages.