# Give agent runs a structured completion inbox

Give people and agents one notification system for agent-run outcomes outside chat.

Long-running agents often finish after attention has moved elsewhere. FYInbox keeps their outcomes in one structured inbox so people and agents do not have to monitor a chat stream.

Published: 2026-07-31. Updated: 2026-09-03.

## Send the outcome, not the whole transcript

- Use a clear title for completed, failed, skipped or degraded outcomes.
- Put bounded counters, run ID and modelled quality signals in metadata.
- Link to the controlled artifact or run view instead of copying sensitive output.

> **Keep prompts and user data out of the event.** Notification context should be safe to retain and inspect. Send pseudonymous identifiers and aggregate results whenever the full input belongs in another protected system.

> **One system on both sides of an agent run.** Agents can produce project activity and are also among the recipients who need its context. The API reference remains the exact inventory of supported machine operations.

## Use stable IDs across retries and related events

The producer's run ID belongs in metadata and can also anchor the deduplication key. Add an outcome suffix if the same run legitimately reports more than one state transition.

1. **Choose a source per agent workflow.** This keeps permissions revocable and filters predictable without pretending every run is a different integration.
2. **Use tags for durable categories.** Classify research, publication or maintenance runs independently from their changing result 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.

## Sources

- [Logging Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html) — OWASP Cheat Sheet Series; verified 2026-09-03.
- [Create-notification request schema](https://fyinbox.com/json-schema/create-notification.request.schema.json) — FYInbox; verified 2026-09-03.

[Use cases index](/use-cases)