Operations Source edition 1.1.0
In-app Notifications
Give customers an inbox inside your app.
Turn events from your backend into personal in-app notifications. Customers can read, dismiss and restore their messages, follow a link back to the app and see how many updates remain unread.
Example scenario
Show a customer their project updates
Your backend records an update and sends a notification to the verified customer who should receive it. They can read it in their inbox, follow a link to the project and dismiss or restore the message.
From setup to the result
- Map verified app users to notification recipients.
- Send a backend event with its stable ID, message and intended recipients.
- Show each customer their own inbox and unread count.
- Let them mark messages read, dismiss them or restore them later.
What the package handles
What you can build with it
- A customer inbox with unread counts, filters and read-state controls.
- One delivery per recipient when a backend event is retried.
- An administrator composer and links restricted to approved app destinations.
Supported behavior
- Notifications from trusted app events, with duplicate-event handling
- Personal inbox, unread counts and read/unread controls
- Dismissal and restoration without losing the original message
- Local or approved HTTPS links, with refresh or app polling
Before you choose
Will it fit your project?
Who it is for
- Products with account, project or workflow updates to show customers.
- Teams replacing scattered notification badges with a saved inbox.
Runtime and connections
Current packages run on Node.js 22.13+ and PostgreSQL 17. You provide hosting and connect the package to your existing app. The included guide describes the supported integration; this is not a hosted service.
Hosting and PostgreSQL costs are separate from the source purchase. A configured external receiver, if used, has its own requirements and costs.
A useful handoff to your coding agent
How setup works
The source package includes local setup instructions, an integration guide, examples, help articles and verification resources. Your agent can use those files without signing in to a hosted reference page.
- Check the requirements. Your agent inspects the application, runtime, database and supported connections before making changes.
- Configure your installation. Answer the product-specific questions below, connect your own accounts where needed and retain the configuration privately.
- Connect and verify. Use the included checks and a representative workflow, then verify any chosen external service separately before relying on it.
Questions to prepare
- Which app events should create a notification, and who should receive each one?
- Which verified customer ID connects each inbox to the existing app account?
- Which destinations may messages link to, and how will retained messages stay within capacity?
What your agent checks
- Replay an event and retain each recipient’s existing read state.
- Reject conflicting reuse of an event ID.
- Check that another customer cannot read or change a notification.
- Fill a recipient’s retained inbox and verify a multi-recipient event fails atomically.
Scope of this edition
Important limits
Updates are stored in the local inbox and refreshed or polled by the app. Email, mobile push and WebSocket delivery are outside this release. Each recipient can retain 1000 notifications, including dismissed messages.
- No email, mobile push, WebSocket server or external notification provider.
- At most 1000 retained notifications per recipient; intake fails atomically at capacity. Dismissed items remain retained.
- Event inspection shows the latest 1000 events. App backend owns identity and recipient selection.
- Messages are plain text; notification links do not grant access to the destination.
Before you decide
Will this work with my existing app?
The package runs on Node.js 22.13+ and PostgreSQL 17. Your coding agent connects it to your application using the included integration guide and supported interfaces. Check the requirements, supported behavior and limits on this page; compatibility with every framework or hosting provider is not promised.
What will my agent need from me?
Your goals, the relevant app details and permission to configure your own accounts. The setup questions on this page help prepare that handoff. Keep credentials in your own private environment; do not paste secrets into a public support request.
What happens if setup fails?
The package includes verification and troubleshooting resources so your agent can inspect the failure and resume the documented setup. Initial setup and reproducible-defect support lasts 30 days from purchase. The refund policy covers material defects we cannot fix, alongside applicable statutory rights.
Is this a subscription?
Helpful Mods sells the source package once. There is no monthly maintenance subscription or automatic renewal. Hosting and connected services have their own costs. Optional major upgrades require a separate purchase.
Can I buy this now?
Purchases are not open yet. You can inspect the product information and use the library planner while checkout is being prepared. A plan is not an order and does not grant source access.