Flows workflow logoFlows
Notification System
0/6 steps0%

Step 1 of 6

Define notification types and triggers

Notifications need real causes - name the events first.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Define the notification spec. Specify: the notification model (id, recipient userId, type, title, body, link, read flag, createdAt); the 2-4 real app events that create notifications (e.g. new order received, comment on your item, system announcement) and who receives each; where each notification links to; and retention/ordering rules (newest first).
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A model plus concrete event-to-recipient trigger mapping.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent