> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/complaints-management/deploy/configure/notifications.md).

# Notifications

Citizens and staff get SMS, WhatsApp and email messages through **novu-bridge** and **Novu**.

#### How it works

1. **Modules publish events** to Kafka (for example, a complaint is filed).
2. **novu-bridge decides** four things for each event:
   * **Who** is told
   * **Which channel** is used (SMS, WhatsApp or email)
   * **Which language** the message is in
   * **What text** it contains
3. **Novu sends** the message.

The decisions come from the **`NOTIFICATIONS.*` MDMS masters**. Operators edit these in the Configurator, so no code change is needed to adjust who gets what.

<table><thead><tr><th width="481.19140625">You want to</th><th>Read</th></tr></thead><tbody><tr><td>Understand what changed for users and product (product, PMs)</td><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/whats-new.md">What's new</a></td></tr><tr><td>Set notifications up and run them (operators, deployers)</td><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/setup-notifications.md">Setup guide</a></td></tr><tr><td>Give each workspace its own Novu account and provider credentials, send citizen sign-in codes</td><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/tenant-notification-account.md">Tenant accounts</a></td></tr><tr><td>Upgrade a 2.12 deployment</td><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/migrate-notifications.md">Notifications migration guide</a></td></tr><tr><td>Connect a module, swap the DIGIT seams (developers)</td><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/developer-guide.md">Developer guide</a></td></tr><tr><td>Understand the providers, DIGIT's worker providers, or add a provider</td><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/providers.md">Providers</a></td></tr><tr><td>Add a new SMS gateway, step by step (developers)</td><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/add-providers.md">Add providers </a>— a worked example from the provider file to a test send on a local stack</td></tr><tr><td>Configure the Kafka / Redpanda topics novu-bridge consumes</td><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/configure-kafka-topics.md">Configure Kafka events</a></td></tr><tr><td>Integrate against the published interface</td><td><a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/notification-contract.md">Notification contract</a> — schemas, OpenAPI, <a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/error-codes.md">error codes</a>, <a href="https://docs.digit.org/complaints-management/deploy/configure/notifications/outputs.md">outputs</a></td></tr></tbody></table>

#### Where the code lives

<table><thead><tr><th width="309.14453125">Part</th><th>Location</th></tr></thead><tbody><tr><td>Bridge</td><td><code>backend/novu-bridge/</code></td></tr><tr><td>Configurator screens</td><td><code>configurator/src/resources/notification-*</code></td></tr><tr><td>Deploy-time seed</td><td><code>local-setup/scripts/seed-notifications.py</code></td></tr><tr><td>Per-tenant migration (2.12 → 2.20)</td><td><code>local-setup/scripts/migrate-notifications.py</code></td></tr><tr><td>Complaint event producer</td><td><code>backend/pgr-services/src/main/java/org/egov/pgr/service/notification/ThinEventBuilder.java</code></td></tr></tbody></table>

Inbound WhatsApp (citizens messaging the chatbot) is a separate feature - details [available on this page](https://docs.digit.org/complaints-management/deploy/configure/notifications).


---

# 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.digit.org/complaints-management/deploy/configure/notifications.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.
