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.

Use case

Give agent runs a structured completion inbox

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.

Updated Sep 3, 20266 min read

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.

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.

Choose a source per agent workflow
This keeps permissions revocable and filters predictable without pretending every run is a different integration.
Use tags for durable categories
Classify research, publication or maintenance runs independently from their changing result values.

Primary sources

Last verified Sep 3, 2026.

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.

GuideSend automation notifications from Python GuideStructure metadata, tags and notification actions Use caseSend no-code workflow results to a dedicated inbox

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.

Create account