> 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/integrations/communications-integrations.md).

# Communications Integrations

How to configure Spara to send notifications to your communication platform.

Spara integrates with messaging platforms to send real-time notifications about lead activity. Connect your team's preferred platform under [**Settings > Integrations**](https://app.spara.co/settings/integrations), then configure which events trigger notifications in [**Settings > Notifications**](https://app.spara.co/settings/notifications) or via [Notify Step](/build/workflows/steps/notify.md).

| Platform                                                                        | Notification channels     | Notify sales rep    |
| ------------------------------------------------------------------------------- | ------------------------- | ------------------- |
| [Slack](/integrations/communications-integrations/slack.md)                     | Post to any Slack channel | DM the assigned rep |
| [Microsoft Teams](/integrations/communications-integrations/microsoft-teams.md) | Post to any Teams channel | *Not supported*     |
| [Webex](/integrations/communications-integrations/webex.md)                     | Post to any Webex room    | *Not supported*     |

## What Spara can and cannot access

Spara's communications integrations are designed for one purpose: posting outgoing notifications into channels you've connected. Spara does not read your team's conversations, store message history, or sync data out of your messaging platform back into Spara.

Because Slack and Microsoft Teams grant access through their standard OAuth scopes, the consent screen during install may list broad permissions (for example, read access to channels and messages) so that the underlying functionality — looking up a channel by name to post into it, surfacing the channel picker in Spara's settings — works correctly. Spara does not exercise those read permissions to ingest your messages, and no channel or message content from your Slack or Teams workspace is stored on Spara's side.

In practice, the only data flowing between Spara and your messaging platform is the notification content Spara generates (lead alerts, workflow updates, sales rep DMs) being posted into the specific channels you've selected.

If your security team needs a written attestation of this, contact your Spara customer success representative.


---

# 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/integrations/communications-integrations.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.