> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/scout/connections/linkedin.md). # LinkedIn Scout looks people up on LinkedIn and, only when you approve it, messages them from your account. Connect LinkedIn and Scout can map who you already know at your accounts, look up the people behind a deal, and, only when you approve it, message them from your account. ## Connect Connect your own LinkedIn account from Scout's card, or from your [**Scout**](https://app.spara.co/scout) page under **Accounts**. If the connection stops working, reconnect it there. ## What Scout does with it * **Looks people up**: who they are, how they can be reached, and whether you're already connected. * **Finds warm paths**: the people you know at an account, and the past champions who have moved somewhere that fits. * **Messages people, only when you say so**: a message to a connection, an InMail, or a connection request. Scout sends only what you approved, to the people you approved, worded as you approved it. Research and drafting never send anything. ## Scout is careful on LinkedIn LinkedIn restricts accounts that look automated, and your LinkedIn account is your professional identity. Scout treats every LinkedIn action as spending a small allowance: it sends a handful at a time, proposes spreading a longer list over days, tells you before it uses an InMail credit or a connection request, and stops for the day if LinkedIn pushes back. Spara also sets its own limit, and Scout tells you when it resets. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spara.com/scout/connections/linkedin.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.