# Automation notifications do not belong in your chat stream

Move project notifications into one structured inbox for people and agents, without turning conversation tools into machine logs.

A chat webhook is an easy first destination for a project result. The cost appears later, when deployment messages, backup reports and agent runs compete with conversation. A central notification record gives people and agents one structured place to keep up.

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

## Chat is optimized for conversation

Chat keeps a team's replies, decisions and shared context close together. A stream of machine output follows a different rhythm: it arrives continuously, often needs no reply and remains useful after the interruption has passed.

- Human messages and automated events compete for the same unread state.
- Structured fields become prose, attachments or ad hoc formatting.
- Reviewing all failed backups later means reconstructing a query from chat history.

## Give machine events a review workflow

1. **Keep the event structured.** Send source, severity, tags, metadata and a stable deduplication key as fields, not as decoration around a chat message.
2. **Interrupt only when useful.** Use optional push per source and device while preserving the full event in the inbox for later review.
3. **Close the loop.** Read, archive or open an explicit link without turning the event into a new conversation by default.

> **Replace the notification channel, not the conversation.** A dedicated inbox replaces Slack, Telegram or email as the default destination for routine project notifications. It does not replace discussion: genuinely collaborative work can still be shared there, while people and agents use FYInbox for project activity.

## 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

- [Sending messages using incoming webhooks](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/) — Slack Developer Docs; verified 2026-09-03.
- [Telegram Bot API: sendMessage](https://core.telegram.org/bots/api#sendmessage) — Telegram; verified 2026-09-03.

[Blog index](/blog)