Skip to app details
Back to app library
APPNEURAL APP FAMILYCommunication

Notifications

The right notice, on the channel each person chose

Send order, invoice and sign-in notices by email, in-app, SMS or WhatsApp, with each person's preferences.

01 / OVERVIEW

See where it fits in your day.

Each domain keeps templates by key (order.shipped) in a transactional, product or security category, never marketing, with content per channel (email, in-app, SMS, WhatsApp), {{variables}} with fallbacks, a Hindi translation, sample data and a live preview; twelve ready templates cover orders, invoices, payments, appointments, sign-in and one-time codes. Subscribers carry the business's own id, email, phone, name, locale and data, with preferences per category and channel and an hourly or daily email digest on a /preferences/<token> page in the domain's brand; security notices cannot be turned off. POST /api/v1/notify takes a template key, a subscriber and data with an idempotency key, and each channel is queued or skipped with the reason. Delivery runs from D1: a first try at once, then a cron every minute with backoff over six tries, a daily cap per domain and a limit per address; the log shows each channel's status and failure reason, with retry and CSV. Email goes from notifications@appneural.com in the domain's name; SMS and WhatsApp use the business's own MSG91, Twilio, Gupshup or WhatsApp Cloud API account, sealed with VAULT_KEY and off until set up. An in-app feed (GET /api/v1/feed with an HMAC subscriber hash) behind an /embed.js bell, webhooks, and Claude for template drafts and Hindi translation.

A LOOK INSIDEExample layout · sample content
Notices and their delivery
NoticeChannelStatus
Order shippednotificationsEXAMPLE
Invoice readytransactional emailEXAMPLE
New sign-insmsEXAMPLE
Appointment reminderwhatsappEXAMPLE
02 / CAPABILITIES

Built around the work you do.

What Notifications does for you.

01

Templates

Transactional, product and security templates with variables, a Hindi version and a live preview.

02

Preferences

Each person turns categories and channels on or off; security notices always go out.

03

Delivery log

Every channel's status and reason, with retries, digests and daily limits.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Notifications. What you can do depends on your access in the app.

01

Write a template

Start from one of twelve ready templates, or describe one for Claude to draft.

02

Send through the API

Call POST /api/v1/notify with a template key and a subscriber.

03

Watch the log

See what was sent, skipped or failed, and retry.

YOUR NEXT MOVE

Make Notifications part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Each domain keeps templates by key (order.shipped) in a transactional, product or security category, never marketing, with content per channel (email, in-app, SMS, WhatsApp), {{variables}} with fallbacks, a Hindi translation, sample data and a live preview; twelve ready templates cover orders, invoices, payments, appointments, sign-in and one-time codes. Subscribers carry the business's own id, email, phone, name, locale and data, with preferences per category and channel and an hourly or daily email digest on a /preferences/<token> page in the domain's brand; security notices cannot be turned off. POST /api/v1/notify takes a template key, a subscriber and data with an idempotency key, and each channel is queued or skipped with the reason. Delivery runs from D1: a first try at once, then a cron every minute with backoff over six tries, a daily cap per domain and a limit per address; the log shows each channel's status and failure reason, with retry and CSV. Email goes from notifications@appneural.com in the domain's name; SMS and WhatsApp use the business's own MSG91, Twilio, Gupshup or WhatsApp Cloud API account, sealed with VAULT_KEY and off until set up. An in-app feed (GET /api/v1/feed with an HMAC subscriber hash) behind an /embed.js bell, webhooks, and Claude for template drafts and Hindi translation.

Transactional and product notices for a connected domain: templates, subscribers with preferences, an API, an in-app inbox, SMS and WhatsApp through the business's own provider, and a delivery log with retries.

Marketing email belongs to Campaigns; the inbox belongs to Mail; automations that trigger notices belong to Workflows.

Priority
P2
Portfolio
Communication
Capability
Communication
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:12
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

notification schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/notification-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app