FYInbox docs
Concepts
Understand the small set of account, source, notification, tag, metadata, action, and push concepts used by the product.
One notification system for people and agents
FYInbox centralizes project notifications outside Slack, Telegram and email in one system for people and agents. The current account model remains one person per account; teams are not part of this version.
Sources and API keys
A source groups notifications from one producer or automation. Its bearer API key selects the source and account on the server. The optional source field inside a payload is descriptive data; it cannot change the source selected by the key.
Structure and delivery
- Tags provide normalized labels for filtering and triage.
- Metadata stores bounded string key/value pairs for exact filters and later context.
- Actions are explicit HTTPS or mailto links shown with a notification.
- Web Push is an optional delivery view of the same inbox item and can be configured per device and source.
Use the same account on your devices
Sign in to the same FYInbox account in a web browser on your phone or computer. Notifications and read/archive state belong to the account and are shared across its authenticated sessions.
The web inbox refreshes every ten seconds while visible and focused, and refreshes when it regains focus. Background tabs do not keep polling. Filter choices live in the URL; sharing a filtered URL does not grant another account access to your notifications.
Configure browser push separately
You can use the web inbox without enabling Web Push. Push requires permission and a subscription in each browser where you want it. Source and preview preferences apply to that subscription.
A browser push subscription is separate from access to the account's stored inbox. Enabling push on one browser does not enable it on your other browsers.
Use the documented operations for agents
A source bearer key can create notifications, retrieve a known notification ID and add or modify metadata within that source. Retrieval does not mark the notification read.
Source-key HTTP operations do not expose an account-wide inbox listing, a notification subscription, read/archive mutations or execution of follow-up actions. Consented OAuth MCP connections additionally support source discovery, notification listing and read/archive updates within approved permissions; see Connect an MCP client. Actions are HTTPS or mailto links; mailto opens a composer and does not send an email.