How do I connect my projects?

Create a source in FYInbox and use its API key to send an HTTP request from your script, agent or workflow. Include a title, tags, metadata and links to the run. Results from your sources appear in the same inbox.

Can FYInbox notify me on mobile?

Yes. Enable Web Push on a supported browser or installed web app, choose which sources alert that device, and control whether alerts show their content. On iPhone and iPad, add FYInbox to your Home Screen first. Opening an alert takes you to its notification or grouped source in FYInbox.

How does FYInbox help me follow up?

Filter by source, tag or exact metadata to find related results. Open a notification to inspect its details and follow its links to logs or reports. Mark it as read or archive it when you are done; that state stays with your account across devices.

FYInbox is for people and agents working across projects that produce automated notifications. Scripts, scheduled jobs and workflows report to one inbox, so their results are available together outside Slack, Telegram and email. Agents can send results and retrieve a known notification using its source key.

Comparison

FYInbox vs Pushover for workflow notifications

A mobile alert can tell you an import failed. FYInbox also keeps the run ID, environment and log link where you can find them later: one inbox for people and agents, outside chat and email, with optional Web Push.

Updated Sep 17, 20268 min read

Why FYInbox

Built around your projects

Keep a central record you can return to after dismissing a mobile alert. Filter notifications by source, tag or exact metadata, open the linked run, and keep your review state in the same account across devices.

In practice

Send a failed import with its run ID, environment and log URL. Receive a push on an enabled device, open the notification, then use those fields to find related results when you return to your desk.

Project history

Setup and follow-up

Send a result from your project, find it in the inbox, and follow its link when you need to investigate.

Connect each project with a source key and send structured results over HTTP.
Find related results with source, tag and exact metadata filters; open follow-up links to inspect the original run.
Choose which sources alert each device through Web Push, while keeping the full record in your inbox.

Side-by-side

Criterion	FYInbox	Pushover
Recipient	People and agents use one central system for project notifications.	Users and groups receive messages on registered devices.
Setup	Create a source and send an authenticated HTTP request.	Create a sender application and use the message API, email gateway or an integration. Zapier and IFTTT appear in the official application directory.
History and triage	One central inbox with filters plus read and archive state, outside chat and email.	Messages are stored on receiving devices. Server delivery storage is temporary: acknowledged deliveries are removed, and undelivered messages expire after 21 days. This is not a universal 21-day client-history limit.
Structure	Title, body, severity, source, tags, exact metadata, deduplication and link actions.	Message, title, supplementary URL, priority, sound and device targeting.
Delivery	Optional Web Push by source and device, with content preview controls. The full notification stays in the inbox outside chat and email.	Up to ten devices per account across supported platforms. A platform license can cover several devices on that platform.
Workflows or embedding	A ready inbox with follow-up links; the public API supports ingestion, bounded metadata updates and reading a known notification within its source.	Emergency messages can repeat until acknowledged, with receipt and callback support. Links lead to external destinations.
Operation	Managed application: create an account and connect your sources.	Managed delivery service with client applications. Since May 1, 2026, monthly sending allowances are shared at sender-account level rather than allocated separately to each application.
Scope	Central structured project-notification system for arbitrary HTTP producers, people and agents.	Personal or group device alerts and acknowledgement.

Frequently asked questions

What do I gain with FYInbox?: Keep a central record you can return to after dismissing a mobile alert. Filter notifications by source, tag or exact metadata, open the linked run, and keep your review state in the same account across devices.
How do I connect my projects?: Create a source in FYInbox and use its API key to send an HTTP request from your script, agent or workflow. Include a title, tags, metadata and links to the run. Results from your sources appear in the same inbox.
Can FYInbox notify me on mobile?: Yes. Enable Web Push on a supported browser or installed web app, choose which sources alert that device, and control whether alerts show their content. On iPhone and iPad, add FYInbox to your Home Screen first. Opening an alert takes you to its notification or grouped source in FYInbox.
How does FYInbox help me follow up?: Filter by source, tag or exact metadata to find related results. Open a notification to inspect its details and follow its links to logs or reports. Mark it as read or archive it when you are done; that state stays with your account across devices.
Who is FYInbox for?: FYInbox is for people and agents working across projects that produce automated notifications. Scripts, scheduled jobs and workflows report to one inbox, so their results are available together outside Slack, Telegram and email. Agents can send results and retrieve a known notification using its source key.

ComparisonFYInbox vs ntfy for workflow notifications 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