Scheduled Reports
Deliver a saved report on a schedule instead of making people rebuild it weekly.
What it adds
Recurring rendering and delivery of a saved analytics report to a chosen set of recipients.
What your agent is told to do
5
What your agent is told to do
5-
1
Let a user attach a schedule to a saved report: frequency, send time, and the time zone the schedule runs in.
-
2
Render each send with the filters, date range, and time zone the report author selected — not the recipient's or the server's.
-
3
Re-check every recipient's access to the report AT SEND TIME. Permission granted three months ago is not permission today.
-
4
Record each send as a run with a status, so a failure is visible rather than a report that quietly stopped arriving.
-
5
Do NOT build batching cadence, per-user notification preferences, or urgent-versus-digestible classification here. Those are owned by Notification Digests; route delivery through it.
Edge cases it handles
6
Edge cases it handles
6- A recipient who lost access must be dropped from that send and the owner told — not sent a report they can no longer open.
- A report with no rows should be skipped or labelled as empty by an explicit setting. Silently sending a blank table trains people to ignore it.
- Two schedules on the same report at the same time must not produce two sends. Deduplicate on report, window, and recipient.
- Daylight saving shifts the wall-clock send time. Pick whether the schedule follows local time or fixed UTC and hold to it.
- A failed render must retry with a bounded backoff, then stop and alert the owner. Infinite retries send twelve copies at 3am.
- A worker restart mid-run must not resend an already-delivered report — mark delivery, not just attempt.
Definition of done
8
Definition of done
8- A saved report can be scheduled with a frequency, send time, and time zone.
- Each send reproduces the author's filters, range, and time zone exactly.
- Recipient access is re-evaluated at send time and revoked recipients are excluded.
- Empty reports follow an explicit skip-or-send setting.
- Duplicate schedules and worker retries never produce a duplicate delivery.
- Send history with success and failure status is visible to the report owner.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
UI Event Naming Schema
UI Event Naming Schema
Give every tracked interaction a name that still means the same thing in a year.
What it does
A documented vocabulary and structure for event names and properties, applied across the app's existing tracking.
How it works
- 1 Audit the events the app already sends and list them. The duplicates, the near-synonyms, and the ones nobody can explain are the reason the schema is needed, and they are also the migration list.
- 2 Fix a structure of object, action, and context: what was acted on, what happened to it, and where. Fix a closed set of actions — viewed, clicked, opened, submitted, selected, failed — and require every new event to reuse one of them.
- 3 Keep variable detail in properties, never in the name. A record identifier, a plan name, or a workspace slug baked into an event name produces thousands of unaggregatable one-off events.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ui-event-naming-schema
Amplitude Event Tracking
Amplitude Event Tracking
Send behavioural events to Amplitude with stable users, devices, and account grouping.
What it does
A server-side pipeline that forwards behavioural events, user properties, and account-level groupings to Amplitude.
How it works
- 1 Identify the behaviours worth measuring and emit them from one place in the application layer, so that the set of events is readable in a single file rather than inferred by grepping the codebase.
- 2 Establish the identity model before writing any send code: what identifies a signed-in user, what identifies a device or anonymous session, and how the two are stitched at sign-up and sign-in.
- 3 Map the app's own tenancy — workspace, organisation, or team — onto Amplitude's group concept, and derive it from the record the event belongs to rather than from whatever context the request happened to carry.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/amplitude-event-tracking
Component Analytics Hook
Component Analytics Hook
Instrument shared components once instead of hand-writing events on every screen.
What it does
Interaction tracking attached to the app's shared components, emitting named events carrying the context of where they were used.
How it works
- 1 Identify the shared components that account for most interaction — buttons, links, menus, dialogs, tabs, table rows, form submits — and attach tracking inside them rather than at each of the hundreds of call sites.
- 2 Have each component emit its own identity and the context it was rendered in: the screen, the surface, and a stable identifier supplied by the caller. Position on the page and visible label are not identity.
- 3 Emit exactly one event per user action. A menu item inside a card inside a table row must not produce three overlapping records of the same click.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/component-analytics-hook
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.