> 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/integrations.md). # Integrations Beyond your inbox, CRM and LinkedIn, Scout reads your other tools through integrations: call recorders, prospecting data, product usage and more. Your buyers leave signals everywhere: in call notes, product usage, intent data, community activity. Scout reads them through integrations, so every signal ends up in one place. Open the **Integrations** tab of your [**Scout**](https://app.spara.co/scout/integrations) page in Spara to see what's connected and what's available. In Slack or by text, just ask Scout to connect a tool, and it sends you a card. ## What's in the catalog Each tool below connects with a sign-in. Some connect once for your whole team; others each rep connects for themselves. * **CRM**: Attio, Pipedrive, Close, HighLevel. HubSpot and Salesforce have their own setup; see [HubSpot](/scout/connections/hubspot.md) and [Salesforce](/scout/connections/salesforce.md). * **Prospecting and enrichment**: Clay, Apollo.io, ZoomInfo, Lusha, Harmonic, Crustdata, Wiza, Deepline. * **Signals and intent**: Common Room, Crossbeam, PostHog, Mixpanel, Leadfeeder, HG Insights, D\&B Hoovers, Meltwater. * **Sales engagement**: Outreach, Salesloft, lemlist, Smartlead, FirstTouch. * **Meetings and calls**: Granola, Attention, Fireflies, Fathom, Circleback, Otter.ai, Read AI, Calendly, Cal.com, Luma. * **Docs and projects**: Google Drive, Notion, Linear, monday.com, ClickUp, Atlassian, Airtable. * **Support, contracts and compliance**: Intercom, Pylon, Vanta, Stripe, PandaDoc, ChartMogul. * **Marketing**: Klaviyo, Webflow, beehiiv. * **Automation**: Zapier. * **Research and web**: Firecrawl, Parallel, Similarweb. ## Connecting for you or for your team On each tool's tile, choose **My user** to connect your own account, or **Organization** to connect it once for everyone. Connecting for the team needs permission to manage integrations in Spara. If you don't have it, connect your own account, or ask whoever manages your Spara integrations. ## Any other tool, through MCP Any tool with a hosted MCP server can connect. Under **Custom MCP server** on the Integrations tab, someone who manages integrations pastes the server's URL and signs in or pastes a token. Once it's added, each rep can connect their own account to it. Looking for a tool that isn't here? Ask Scout. It can flag what you want to the Spara team. ## What Scout does with a connection Once a tool is connected, Scout reads it like anything else you've connected: to prep you before a call, to spot a signal worth acting on, and to back up a draft with what the tool knows. Scout only reads from integrations on its own; anything that would change a tool, it asks you first. --- # 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/integrations.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.