# Ecosystem Events Alerts

{% hint style="info" %}
Event alerts are set up conversationally through Nova — just tell Nova what you want to be notified about. Available on Discord and Telegram.
{% endhint %}

***

### What You'll Get Notified About

| Event                | Description                                                          |
| -------------------- | -------------------------------------------------------------------- |
| **New Event Posted** | A new event was added to the Stacks ecosystem calendar               |
| **Starting Soon**    | An event is starting within the next hour                            |
| **Status Change**    | An event's status changed (e.g., upcoming -> in-progress, cancelled) |

**Event details include:** title, date/time, virtual vs in-person, location or meeting link, host, attendee count, token requirements, and on-chain attendance badges.

***

### Setup via Conversation

Unlike legacy notification commands, event alerts are created through **natural language conversation** with Nova. Just describe what you want:

#### Example Prompts

> *"Alert me about new Stacks events"* *"Notify me when new virtual events are posted"* *"Alert me when events are about to start"* *"Set up an alert for all event activity"*

#### What Happens

1. Nova interprets your request and builds the alert conditions
2. Nova confirms the setup: *"I'll set up an alert for new Stacks ecosystem events. You'll be notified whenever a new event is posted. Sound good?"*
3. You confirm, and the alert is created
4. Nova polls for events every 30 minutes and notifies you when conditions match

***

### Condition Fields

These are the fields you can filter on (Nova handles this for you based on your description):

| Field                | Values                                               | Description                              |
| -------------------- | ---------------------------------------------------- | ---------------------------------------- |
| **change\_type**     | `new_event`, `status_change`, `starting_soon`, `any` | What kind of event activity triggered it |
| **event\_type**      | `virtual`, `irl`                                     | Virtual or in-person events              |
| **event\_status**    | `upcoming`, `in-progress`, `completed`, `cancelled`  | Current status of the event              |
| **host\_username**   | Any username                                         | Filter by event host                     |
| **tokens\_required** | `true`, `false`                                      | Whether the event requires token staking |

***

### Combining Conditions (Premium)

Premium users can combine multiple conditions:

> *"Alert me about new virtual events only"* (change\_type = new\_event AND event\_type = virtual) *"Notify me when in-person events are starting soon"* (change\_type = starting\_soon AND event\_type = irl)

***

### Browsing Events

You can also ask Nova to show events without setting up alerts:

> *"What Stacks events are coming up?"* *"Show me past events"* *"Any virtual events this week?"* *"Search events about Bitcoin"*

***

### Free vs Premium

|                           | Free   | Premium  |
| ------------------------- | ------ | -------- |
| Max alerts                | 2      | 50       |
| Conditions per alert      | 1      | Up to 10 |
| Cooldown between triggers | 1 hour | 1 minute |
| Composable conditions     | --     | Yes      |
| Time windows              | --     | Yes      |
| Digest mode               | --     | Yes      |


---

# Agent Instructions: 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:

```
GET https://docs.zeroauthority.xyz/nova-bot/alerts-setup-guides/ecosystem-events-alerts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.