Notifications tooling

A monorepo for Guardian notifications tooling.

It currently contains a single editorial tool called Dispatch (under development), used to compose and send notifications.

Contents

• Introduction
• Getting Started
• How It Works
• Useful Links
• Terminology

1. Introduction

Dispatch gives editorial staff one place to compose and send breaking-news notifications.

It replaces a fragmented workflow spread across multiple systems and legacy tooling.

Email delivery currently integrates with Braze, and app push integration with the notifications API.

2. Getting Started

Prerequisites

• This project relies on Bun. On Mac OS install its latest version using Homebrew:

  brew install bun

• dev-nginx
• Docker (optional; required for local Postgres if needed)

First-time setup

./scripts/setup.sh

Run locally

Start the service:

./scripts/start.sh

Local URLs:

• https://dispatch.local.dev-gutools.co.uk

This local setup currently depends on a temporary workaround introduced to support local development. Because panda-auth for Node does not generate cookies, you need to run the login tool locally alongside Dispatch.

This is implemented using the new developer policies. We considered adding these policies to login directly, but both login and Dispatch use the same Composer AWS profile, so only one policy context can be active at a time.

Run apps separately if needed:

cd src/apps/frontend
bun run dev

cd src/apps/backend
bun run dev

Optional local Postgres

Should Postgres be required, there is a minimal working ./docker/docker-compose.local.yml file and two helper scripts to start & stop docker services.

bun run docker:compose:up
bun run docker:compose:down

Tests, linting, formatting, and type checks

Run from the repo root:

bun test
bun run lint
bun run lint:fix
bun run format
bun run format:check
bun run typecheck

Run commands for one workspace package/app when needed:

bun --filter backend test
bun --filter frontend typecheck

Git hooks are managed with lefthook and installed automatically via bun install (prepare script).

3. How It Works

Core technologies

• Bun workspaces for package management and scripts.
• React (frontend) and Express + Zod validation (backend).
• AWS CDK (@guardian/cdk) for infrastructure definitions.

Repository layout

• src/apps/frontend: UI for composing notifications.
• src/apps/backend: API and channel request generation.
• src/packages: shared packages.
• cdk: infrastructure stack and deployment definitions.

Infrastructure model

This is deployed using AWS API Gateway + Lambda.

flowchart LR
    Editor[Editorial user] --> APIGW[API Gateway\ndispatch.gutools.co.uk]
    APIGW --> Lambda[Lambda\nNode.js 24.x\nExpress app via serverless adapter]

    Lambda --> Braze[Braze API\nemail channel]
    Lambda -. planned .-> N10N[mobile-n10n notifications API\napp push channel]

Loading

4. Useful Links

• Braze REST API: https://www.braze.com/docs/developer_guide/rest_api/sending_messages
• App notifications monorepo: https://github.com/guardian/mobile-n10n
• Existing Breaking News tool: https://fronts.gutools.co.uk/breaking-news
• Existing Breaking News tool code: https://github.com/guardian/facia-tool
• Bun documentation: https://bun.sh/

5. Terminology

• Segment: A target audience group (UK, US, AU, EU, ALL).
• Delivery mode: The notification timing strategy (immediate, scheduled, intelligent).
• Channel: A delivery destination such as email or app-notification.