> 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/build/workflows/steps/notify.md).

# Notify Step

Send an internal notification via email, Slack, Teams, or Webex.

The **Notify** step sends an internal notification via email, Slack, Microsoft Teams, or Webex — to a channel or room, to specific email addresses, or directly to the lead's assigned sales rep. Use it to alert your sales team when a lead takes a specific action — for example, when an assigned lead schedules a meeting, a high-value lead completes a form, or a lead replies to a workflow email.

<figure><img src="https://4072969777-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FreCGkFdsmuPJzGP9ZgGA%2Fuploads%2Fgit-blob-c0a25c45a3f05ebadbb4878ba6be0ba018db25f6%2FWorkflow%20Notify%20Step.png?alt=media" alt=""><figcaption><p>The Notify step configuration panel with Slack channel and message.</p></figcaption></figure>

## Configuration

### Platform

Choose **Slack**, **Microsoft Teams**, **Webex**, or **Email**. Slack, Teams, and Webex require the corresponding integration enabled under [**Settings > Integrations**](https://app.spara.co/settings/integrations); email notifications need no integration and are sent from Spara.

### Channel / Room (Slack, Teams, and Webex)

Select the channel, team, or Webex room to post the notification to. The available options are loaded from your connected workspace. Optional when **Direct Message** is enabled.

### To and Subject (Email)

Enter one or more recipient email addresses, separated by commas. The subject line is optional and supports variables (see [How to Use Spara's Text Editor](https://docs.spara.com/guides/best-practices/how-to-use-sparas-text-editor.md)), just like the message.

### Direct Message / Assigned sales rep

Check **Assigned sales rep** to notify the lead's assigned sales rep directly — a direct message on Slack, Teams, or Webex, or an additional recipient on email. The assigned rep comes from your connected CRM (Salesforce or HubSpot); for direct messages, the rep must have an account in your workspace that uses the same email address as their CRM user. You can combine this with a channel or other recipients — the notification is sent to all of them.

Webex direct messages are sent from the Webex account that connected the integration, so the rep sees them in their one-on-one space with that account. Webex can't deliver a message from an account to itself: when a lead's assigned rep is the account that connected Webex, that direct message is skipped and the rep is listed under **Not reached**. Connect Webex from a shared or admin account if every rep needs these messages.

At least one destination — a channel or room, an email recipient, or the assigned sales rep — must be selected.

### When a notification can't be delivered

A step that reaches only some of its destinations still completes, and the Activity tab names the ones it skipped under **Not reached**.

A step that reaches nobody is marked **Not delivered** with the reason. What happens to the lead depends on the reason:

* **A problem with this lead**, such as no assigned sales rep in your CRM, or a rep who is not in your Slack, Teams, or Webex workspace: the lead continues to the later steps. Only this lead's notification is affected, so the workflow keeps running for everyone else.
* **A problem with your setup**, such as an unfinished step, no connected CRM, or no connected Slack, Teams, or Webex workspace: the lead stops there. The step cannot reach anyone for any lead until you fix it, and the leads resume once you do.

To make sure a notification always reaches someone, add a channel or another recipient alongside **Assigned sales rep**.

### Message

Write the notification message. Supports variables: use the **Insert menu** (⚡) to insert lead data.

Use the **Preview** button to see how the message renders with sample data.

## Global notification settings

The Notify step is best for targeted, conditional alerts: notifications that should only fire when leads match specific workflow criteria. For account-wide alerts that fire every time a lead event occurs (such as deanonymization, enrichment, or emails sent), use the global [Notifications](https://docs.spara.com/platform/settings/notifications.md) settings instead.


---

# 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/build/workflows/steps/notify.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.
