One place for people and agents
Keep what changed across every project in one inbox instead of a collection of chats, channels and email threads.
Notification system for people and agents
Project notifications belong in one inbox—not in chat
Bring what happens across your projects out of Slack, Telegram and email and into one central, structured inbox for people and agents.
Create your personal account, verify your email, and keep every project notification in one place.
HTTP request
POST /api/v1/notifications
Authorization: Bearer $FYINBOX_API_KEY
Content-Type: application/json
{
"title": "Backup completed",
"body": "Nightly PostgreSQL backup finished and was verified.",
"severity": "success",
"tags": [
"backup",
"production"
],
"source": "backup-worker",
"deduplicationKey": "backup:2026-07-31",
"metadata": {
"duration": "42s",
"size": "1.8 GB"
},
"actions": [
{
"id": "open-backup",
"type": "link",
"label": "Open backup",
"href": "https://example.com/backups/2026-07-31",
"style": "primary"
}
]
}201{"id":"c7c25c99-bb6d-4fcc-a95a-923d668dd012","created":true}
Backup worker
Backup completed
Nightly PostgreSQL backup finished and was verified.
backupproduction
Move notifications out of chat
Let conversation tools be conversations again.
Slack, Telegram and email scatter project activity across places built for conversation. FYInbox gives those notifications one home for people and agents.
Structured project context
Keep the source, outcome, metadata and next action attached so people and agents work from the same notification record.
Conversation stays conversation
Move routine project notifications out of Slack, Telegram and email while keeping genuinely collaborative work there.
From project to inbox
Three steps from project activity to one notification system.
Send each project outcome through the same structured path, without asking people or agents to monitor a chat channel.
1. Name the source
Give the producer a clear name and create its revocable API key. The secret is shown once.
2. Send one request
POST JSON from a script, service, agent or any workflow that can speak HTTP.
3. Keep it available
The notification stays in one structured inbox for people and agents instead of disappearing into a conversation stream.
One destination for every project
Every project reports to the same inbox.
Use the same small HTTP contract across code and visual workflows so project notifications stop being scattered across conversation tools.
Scheduled jobs and backups
Record completions, missed runs, verification failures and recovery links.
Builds and publications
See successful releases, rollbacks and broken pipelines in one reviewable history.
Agent runs
Give every agent run one place to report its outcome, preserve context and request attention outside chat.
No-code workflows
Use any HTTP request step that can send JSON with a bearer token.
Context both recipients can use
Preserve what people and agents need.
A project update can stay concise while its source, identity and next action remain structured outside the prose of a chat message.
Sources and tags
Keep producers distinct, then group events across them with normalized tags.
Exact metadata
Attach string key/value context and filter it later without putting everything in the title.
Safe retries
A deduplication key returns the original event while it exists instead of creating another copy.
Explicit actions
Attach deliberate HTTPS or email links that open the next place you need to work.
The product boundary
For your project activity, not customer messaging.
FYInbox centralizes the project notifications that people and agents need to know. It is not a campaign builder, embedded customer inbox, on-call escalation system or omnichannel router.
Choose this inbox when
Project activity should leave chat and arrive in one structured place for people and agents.
Choose customer messaging when
Your product needs templates, recipients, preferences and delivery across customer channels.
Private by default
Security by construction.
The product keeps account boundaries and credential handling in the data path, not in marketing promises.
Account-scoped access
Reads and writes are bound to the authenticated account, with database row-level isolation in PostgreSQL.
Revocable source credentials
API key secrets are shown once; only a cryptographic digest is stored for later authentication.
Encrypted sensitive fields
Sensitive business fields are encrypted before PostgreSQL persistence, with root key material kept outside the database and its backups.
Straight answers
Before the first project notification arrives.
FYInbox has one clear job: keep project notifications together for people and agents, outside conversation channels.
What can send a project notification?
Anything that can make an authenticated HTTP request: a script, backend service, scheduled job, agent or visual workflow with an HTTP step.
What does FYInbox replace in Slack, Telegram or email?
It replaces using those tools as the default inbox for project notifications. It does not replace the conversations, coordination or customer messages that belong there.
Who is FYInbox for?
FYInbox is for people and agents that need to know what happens across projects without monitoring Slack, Telegram, email or other conversation channels.
Can I use it from a no-code workflow?
Yes. Use an HTTP request step, send JSON and place the source API key in the bearer authorization header.
What happens when a sender retries?
Send a stable deduplication key. While the original event exists, a retry returns that event instead of creating a duplicate.
Can notifications still reach my device?
Browser push is optional. New subscriptions show a short content preview; each device can switch to a private generic alert or mute individual sources.
Is this an inbox for my product's customers?
No. It centralizes activity from your own projects for people and agents. Customer messaging platforms solve a broader and different job.
How long is history kept?
Events remain available as reviewable history. FYInbox does not currently offer commercial retention tiers.
Your projects already have something to tell you. Give it one inbox.
Move notifications out of Slack, Telegram and email. Keep them together for people and agents.
Create account