> For the complete documentation index, see [llms.txt](https://docs.countercyclical.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.countercyclical.io/notifications/custom-alerts.md).

# Custom Alerts

Create permission-aware, event-driven monitors that evaluate governed workspace signals and deliver matched events to the destinations that matter to your workflow.

Custom Alerts let you define **what to monitor, what constitutes a match, when the alert should evaluate, and where the resulting notification or output should go**. Alerts are scoped to the active workspace and evaluated using your permissions.

See also [Channel Preferences](https://docs.countercyclical.io/notifications/channel-preferences) and [Slack Notifications](https://docs.countercyclical.io/notifications/slack-notifications).

### Creating a Custom Alert

Go to [**Settings › Notifications › Alerts**](https://dashboard.countercyclical.io/settings/account/notifications/alerts).

The Alerts page lists the alerts available to you and provides search and management controls. If no alerts have been created, select **Create Alert** to open the alert builder.

The builder separates alert creation into five stages:

1. **Alert Identity**
2. **Templates**
3. **Query Builder**
4. **Delivery Methods**
5. **Evaluation Schedule**

You can switch between **Configuration** and **Preview** while building the alert. Preview represents the alert as an execution flow from its trigger signature through evaluation cadence and delivery.

### Alert Identity

Start by defining what the alert represents.

#### Name

Give the alert a recognizable name that describes the monitored signal, such as:

`Material earnings variance`

Names make alerts identifiable when they are reviewed, delivered, or audited later.

#### Category

Choose the category of activity the alert should monitor. Categories determine the data and properties available to the alert's query builder.

Available categories shown include:

| Category                | Monitors                                                                         |
| ----------------------- | -------------------------------------------------------------------------------- |
| **Companies**           | Company fundamentals, classifications, price movements, and profile changes      |
| **Investments**         | Portfolio workflow, valuation, ownership, and diligence-state changes            |
| **Documents & Filings** | Public filings, diligence documents, connected storage, and material disclosures |
| **People & Ownership**  | Executive, insider, institutional-holder, and relationship activity              |
| **Markets & Economics** | Market- and economic-related signals where available                             |

Changing the category also changes the templates and category-specific query conditions available later in the builder.

#### Description

Use the description to explain **who should act and why the alert matters**.

A useful description captures the decision workflow rather than merely repeating the alert name. This makes the alert easier to understand when it appears in a notification or is reviewed later.

### Templates

Templates provide predefined starting points for common alert patterns.

Templates are category-aware. Selecting **Companies**, for example, exposes Company-specific templates such as:

* **Earnings & Guidance** — Track earnings, guidance, and material fundamental changes.
* **Material Price Move** — Surface companies with a material percentage price movement.
* **Profitability Inflection** — Identify companies crossing into profitability or reporting income changes.
* **Market Cap Change** — Track material changes to a company's market capitalization.
* **Sector Watch** — Monitor company activity within a selected sector or industry.
* **Fundraising & Transactions** — Follow capital raises, transactions, and diligence milestones.

Selecting a template provides a starting configuration that you can refine in the Query Builder.

Templates follow the selected category. If you change the alert category, the available templates refresh and category-specific query conditions are cleared as necessary.

You do not have to use a template. You can construct the alert signature directly.

### Query Builder

The **Query Builder** defines the event signature that determines when the alert matches.

Each condition consists of a property, an operator, and—where required—a comparison value.

For example:

`Ticker Symbol` → `equals` → `[value]`

Select **Add Condition** to add additional criteria.

#### Match Any vs. Match All

When an alert contains multiple conditions, use the matching control to determine how those conditions are combined.

**Any Filter** returns results matching at least one applied filter.

**All Filters** returns only results matching every applied filter.

Use **All Filters** when the conditions collectively define a narrow signal. Use **Any Filter** when several independent conditions should each be capable of producing a match.

#### Operators

Available operators depend on the selected property. The interface shown supports operators including:

| Operator           | Behavior                                      |
| ------------------ | --------------------------------------------- |
| **equals**         | Property must equal the specified value       |
| **does not equal** | Property must differ from the specified value |
| **contains**       | Property must contain the specified value     |
| **starts with**    | Property must begin with the specified value  |
| **is one of**      | Property must match one of several values     |
| **changes**        | Match when the monitored property changes     |

Property-specific operators may vary according to the selected alert category and field.

#### Recommended Filters

The builder can surface recommended filters appropriate to the selected category, such as **Material Price Move**, **Profitable Companies**, or **U.S. Companies**.

These provide shortcuts for constructing common event signatures while retaining the ability to refine the resulting conditions.

### Delivery Methods

Choose one or more destinations for events that match your alert.

The builder supports the following delivery destinations:

| Destination          | Purpose                                                                                                       |
| -------------------- | ------------------------------------------------------------------------------------------------------------- |
| **In-App**           | Deliver the alert to the workspace inbox                                                                      |
| **Email**            | Send the alert to your verified email address                                                                 |
| **Push**             | Notify supported desktop and mobile clients                                                                   |
| **Slack**            | Send the alert through your configured Slack notification channel                                             |
| **Webhook**          | Send a signed event to an external HTTPS endpoint                                                             |
| **Report Component** | Render matched alert data into reusable [Components](https://docs.countercyclical.io/relations/components.md) |

You can select multiple destinations for the same alert.

Some destinations require additional configuration before they can be used. The Preview flow identifies these destinations and can mark them as requiring additional configuration.

### Delivery Message Templates

For supported notification destinations, you can customize the content delivered when the alert fires.

Message templates can provide overrides for fields such as:

**Title / Subject**, **Body**, and **Supporting Description**.

These overrides let a single governed signal produce messaging tailored to its destination and decision workflow.

#### Dynamic Variables

Alert messages support an allowlisted set of dynamic variables. Select **Insert Variable** to insert one into a message field.

Variables shown include:

| Variable                | Value                      |
| ----------------------- | -------------------------- |
| `{{alert.name}}`        | Alert name                 |
| `{{alert.description}}` | Alert description          |
| `{{alert.category}}`    | Selected alert category    |
| `{{workspace.name}}`    | Workspace name             |
| `{{match_count}}`       | Number of matching results |
| `{{summary}}`           | Generated alert summary    |
| `{{evaluated_at}}`      | Evaluation timestamp       |

Templates are stored as plain text and rendered server-side. Executable expressions, partials, and unescaped blocks are rejected, keeping dynamic alert messaging constrained to the supported variables.

### Evaluation Schedule

The Evaluation Schedule controls **when the alert checks for matching events**.

Configure the recurrence using **Every**, then specify the evaluation time under **At**.

You can also configure:

**Start Date** — when scheduled evaluation should begin.

**End Date** — when scheduled evaluation should stop.

**Timezone** — the timezone used for the evaluation schedule.

For example, an alert configured for:

`Every Day → 8:00 AM → Chicago`

evaluates daily at 8:00 AM in the selected Chicago timezone.

Start and end dates are optional controls for bounding the alert to a specific monitoring period.

### Previewing an Alert

Select **Preview** to inspect the alert as a workflow before creating it.

The preview visualizes the complete execution path:

**Start → Alert → Trigger Signature → Evaluation Cadence → Delivery → End**

This provides a compact way to verify that the alert's identity, matching logic, schedule, and destinations represent the intended monitoring workflow.

The preview also surfaces incomplete configuration. For example, it can identify a missing alert name, incomplete trigger signature, or delivery destination requiring additional configuration.

Selecting a node exposes its configuration details in the side panel.

### Adding Delivery Methods from Preview

Delivery destinations can also be inspected and added from the Preview flow.

Select the add control beneath the delivery stage to see additional methods. Destinations such as **Slack**, **Webhook**, and **Report Component** can be marked **Requires Additional Configuration** when their required destination settings have not yet been supplied.

This makes Preview useful not only for visual inspection but also for identifying remaining setup work.

### Testing an Alert

Once the required configuration is complete, use **Test Alert** to validate the alert before creating it.

Testing is useful for checking that the trigger signature, delivery configuration, and other required settings behave as intended without relying on the next scheduled production evaluation.

### Creating the Alert

After the alert has a valid identity, query, delivery configuration, and schedule, select **Create Alert**.

The resulting alert becomes a governed workspace monitor and can subsequently be managed from the **Alerts** area.

### Workspace-Scoped Evaluation

Custom Alerts are workspace-scoped.

Alert signatures operate against the active workspace and are evaluated using the permissions available to you. An alert therefore does not provide a mechanism for monitoring records that you could not otherwise access.

This permission-aware model also applies to delivered results: Custom Alerts are intended to surface governed signals within the access boundaries of the workspace rather than bypass them.

### Recommended Configuration Pattern

For a maintainable alert, define the decision workflow before making the query increasingly complex. Give the alert a descriptive identity, select the narrowest appropriate category, use a template when it provides a useful baseline, and then refine the event signature with explicit conditions.

After defining the signal, configure only the delivery destinations needed by the workflow, set an evaluation cadence appropriate to how quickly the underlying information changes, and use **Preview** and **Test Alert** before creating the monitor.

#### Related Pages

{% content-ref url="/pages/LhVkzvuDsdjbaA1OjjvI" %}
[Channel Preferences](https://docs.countercyclical.io/notifications/channel-preferences.md)
{% endcontent-ref %}

{% content-ref url="/pages/k46Q39VGkcko4Ci0KvVX" %}
[Slack Notifications](https://docs.countercyclical.io/notifications/slack-notifications.md)
{% endcontent-ref %}

{% content-ref url="/pages/ZSy7vj4Xf2fHCXKXxKmk" %}
[Notifications Overview](https://docs.countercyclical.io/notifications/notifications-overview.md)
{% endcontent-ref %}
