> 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/getting-started/connect-your-tools.md).

# Connect your tools

Scout learns how you sell from your inbox, your CRM and LinkedIn, and shows you real work from each one as you connect it.

Scout learns how you sell from the tools you already use. On your first day it asks for them one at a time, and after each one it shows you the single most valuable thing it found there, so you can act on it right away or keep going.

Each connection arrives as a card in your Slack or text conversation. Tap **Connect** and sign in. You can also connect everything from your [**Scout**](https://app.spara.co/scout) page in Spara, under **Accounts**.

## The order

1. **Your inbox**, Gmail or Outlook, with its calendar. This is the one that matters most: it's where Scout sees your deals, learns your writing voice, and puts its drafts. See [Gmail and Outlook](/scout/connections/gmail-and-outlook.md).
2. **Your CRM**, HubSpot or Salesforce. Your pipeline, and what you've won and lost, so Scout can tell which deals need you. See [HubSpot](/scout/connections/hubspot.md) and [Salesforce](/scout/connections/salesforce.md).
3. **LinkedIn**, so Scout can map who you already know at your accounts. See [LinkedIn](/scout/connections/linkedin.md).

After the last one, Scout points you to your Integrations page for everything else it can read: call recorders, prospecting data, product usage and more. See [Integrations](/scout/connections/integrations.md).

## What you see after each connection

Scout doesn't just confirm the connection. It goes through what it can now see, and the one thing worth your attention jumps out: a deal that went quiet after a pricing call, a champion who just changed jobs, a thread that's waiting on you. Scout tells you what it found, why it matters now, and what it did about it, often with a draft already in your Drafts. Act on it now, or keep going and come back to it.

## Skipping or saying no

You can say no to any connection, and Scout moves on. If you skip your inbox, Scout skips the CRM too and goes on to LinkedIn, then does what it can from public information. You can connect anything later from your Scout page, or by asking Scout.

{% hint style="info" %}
Scout can only read what you connect, and only as you: your own mailbox, your own CRM login, your own LinkedIn account.
{% endhint %}


---

# 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/getting-started/connect-your-tools.md?ask=<question>&goal=<user_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.