> 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/platform/settings/notifications.md). # Notifications Configure when and how your team gets notified about lead activity. Spara can notify your team in real time when key lead events occur — like a new visitor being identified, lead information being enriched, or an email being sent. Notifications help your sales team respond faster and stay on top of pipeline activity without constantly monitoring the platform. There are two ways to set up notifications about lead activity: * [**Settings > Notifications**](https://app.spara.co/settings/notifications) — automatically notify your team when specific lead events happen across all leads. Best for organization-wide alerts that should fire every time an event occurs. * **Workflow Notify step** — send targeted notifications as part of a [Workflows](/build/workflows.md), with custom messages and lead-specific data. Best for conditional alerts that should only fire when leads match specific criteria. See [Notify Step](/build/workflows/steps/notify.md) for setup instructions. ## Notification Settings Navigate to [**Settings > Notifications**](https://app.spara.co/settings/notifications) to configure automatic notifications for your organization. Each notification event can be independently enabled and routed to one or more channels.

The Notifications tab in Settings, showing configurable events.

### Notification events Notifications share their event catalog with [Workflows](/build/workflows.md) triggers, so any event a workflow can start from can also send your team a notification. Events are grouped by where they come from: **Lead activity events** fire based on lead identification and status changes: | Event | What triggers it | | ----------------------------------- | ------------------------------------------------------------------ | | **Website visitor deanonymization** | A previously anonymous website visitor is identified by IP address | | **Lead enrichment** | Spara learns new information about a lead through enrichment | | **Blocked** | A lead is blocked or marked as malicious | | **Webform submitted** | A lead submits a webform | | **Unsubscribed** | A lead unsubscribes from your emails | **Email events** fire when emails are sent, received, or engaged with: | Event | What triggers it | | ------------------------------- | ---------------------------------------------------------------- | | **Workflow email sent to lead** | A [Workflows](/build/workflows.md) step sends an email to a lead | | **Reply email sent to lead** | A reply email is sent to a lead | | **Lead sent an email** | A lead sends your team an email | | **Email opened** | A lead opens an email from Spara | | **Email link clicked** | A lead clicks a link in a Spara email | | **Email reply received** | A lead replies to an email | **Text events** fire when a lead texts your team: | Event | What triggers it | | ----------------- | --------------------------- | | **Text received** | A lead sends a text message | **Chat events** fire during live conversations with a lead: | Event | What triggers it | | ----------------------------- | --------------------------------------------------------- | | **Chat conversation started** | A lead starts a chat conversation | | **Chat conversation ended** | A lead finishes a chat conversation | | **Email captured** | A lead provides their email address | | **Agent condition met** | A lead meets a condition configured in an agent's trigger | **Phone and product demo events** fire when calls complete: | Event | What triggers it | | ------------------------ | -------------------------------------------- | | **Incoming call ended** | An incoming phone call with a lead completes | | **Outgoing call ended** | An outgoing phone call to a lead completes | | **Navigator call ended** | A Spara Navigator web call completes | | **Product demo ended** | A product demo session completes | **Meeting events** fire around scheduling: | Event | What triggers it | | --------------------- | ---------------------------------- | | **Calendar shown** | A lead is shown a booking calendar | | **Meeting scheduled** | A lead books a meeting | {% hint style="info" %} Call-ended notifications fire only for calls that connect. Dials that go unanswered or fail do not notify your team. **Email opened** and **Email link clicked** require email tracking to be enabled for your account. {% endhint %} {% hint style="info" %} For **Agent condition met**, the message content is defined by your agent's trigger configuration; here you only choose where to send it. If you previously subscribed to "A voice call has ended", your subscription was split into the per-call-type events above, based on the call types your account has had. {% endhint %} ### Notification channels Each event can be routed to one or more of these channels: * **Email** — Send to a specific email address. When a sales rep is assigned to the lead, you can also enable **Notify sales rep** to send a copy to them automatically. * **Slack** — Post to a specific Slack channel. Also supports **Notify sales rep** to DM the assigned rep. * **Microsoft Teams** — Post to a specific Teams channel. * **Webex** — Post to a specific Webex room. Slack, Teams, and Webex must be connected under [**Settings > Integrations**](https://app.spara.co/settings/integrations) before they appear as notification options. See [Communications Integrations](/integrations/communications-integrations.md) for setup instructions.

Connect Slack, Microsoft Teams, or Webex under Settings > Integrations to unlock messaging channels.

### Enabling a notification To enable a notification for an event: 1. Check the **Send to email address** box next to the event 2. Enter the email address that should receive the notification 3. Click **Save Changes**

Enabling an email notification reveals the email address field.

{% hint style="info" %} If your organization has connected [Slack](/integrations/communications-integrations/slack.md), [Microsoft Teams](/integrations/communications-integrations/microsoft-teams.md), or [Webex](/integrations/communications-integrations/webex.md), additional channel options appear for each event. You can route the same event to multiple channels simultaneously. {% endhint %} ## FAQ ### Do notification settings and workflow Notify steps overlap? They serve different purposes. Notification settings send automatic alerts for every lead that triggers an event. Workflow Notify steps send alerts only for leads that enter a specific workflow and reach the Notify step. You can use both together. ### Can I notify the assigned sales rep? Yes, for Email and Slack notification channels. Enable the **Notify sales rep** toggle next to the event. Spara looks up the rep's email from your connected CRM (e.g., Salesforce) and sends them a notification when their assigned lead triggers the event. ### What if I don't see Slack or Teams options? You need to connect the integration first. Go to [**Settings > Integrations**](https://app.spara.co/settings/integrations) and authorize Slack, Microsoft Teams, or Webex. Once connected, those channels appear as options in both notification settings and the workflow Notify step. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.spara.com/platform/settings/notifications.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.