Use case
Review cron jobs and backup results in one inbox
Scheduled work often succeeds quietly until one result needs attention. A central inbox keeps every reported outcome out of Slack, Telegram and email for people and agents.
Updated 5 min read
Report success, failure and missed execution distinctly
Send a completion event
Include the schedule window, duration and verification result after the job finishes.
Send a failure event
Use a higher severity, a concise failure stage and a link to the relevant run or log view.
Detect absence separately
Let a supervisor emit a missed-run event when the expected completion signal does not arrive.
Preserve enough structure to compare runs
- Filter by the backup source and error severity during an incident.
- Use tags to separate production, staging and different backup classes.
- Keep size, duration and scheduled window as bounded metadata values.
Frequently asked questions
- Does the producer need a special integration?
- No. The examples use an authenticated HTTPS request, so any script, service or visual workflow that can send HTTP can use the same contract.
- Should credentials be included in notification data?
- No. Keep credentials in the producer's secret store and send only the context needed to understand or locate the event.
- Why send this to FYInbox instead of chat or email?
- FYInbox gives project notifications one structured, reviewable home instead of scattering them through Slack, Telegram and email. Those tools remain useful for conversations and intentional messages.
- Why structure notifications for people and agents?
- People and agents both need stable source, outcome and next-action context. FYInbox keeps that context in one notification record outside conversation streams.
Keep exploring
Put project notifications in their own inbox
Create an account and move the next notification out of chat and into one inbox for people and agents.