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 Knock: one inbox across your projects

Deployments, imports and scheduled jobs can report to the same FYInbox account. People and agents get one place for project notifications outside chat and email, with a separate source key for each project.

Updated Sep 17, 20268 min read

Why FYInbox

Built around your projects

Your notification destination works across projects independently of their UI. Each source has its own key, while a shared inbox gives you source filters, tags, exact metadata and read/archive state.

In practice

Connect a deployment script and a data import as separate sources. Review both in FYInbox, narrow the inbox to the project you are investigating, and open the relevant run from its notification.

Project history

Your notification destination works across projects independently of their UI. Each source has its own key, while a shared inbox gives you source filters, tags, exact metadata and read/archive state.

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	Knock
Recipient	People and agents use one central system for project notifications.	Recipients of another product receive workflow-generated messages.
Setup	Create a source and send an authenticated HTTP request.	Model recipients, workflows, templates and feeds, then integrate components.
History and triage	One central inbox with filters plus read and archive state, outside chat and email.	Feeds expose seen, read and archived state for recipient notifications.
Structure	Title, body, severity, source, tags, exact metadata, deduplication and link actions.	Workflow data, recipient properties, feed metadata and notification actions.
Delivery	Optional Web Push by source and device, with content preview controls. The full notification stays in the inbox outside chat and email.	Real-time feeds coordinate with other channels through workflows.
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.	Branching, batching, delays, preferences, feeds and embedded components.
Operation	Managed application: create an account and connect your sources.	Operate product notification logic and integrate it into an application.
Scope	Central structured project-notification system for arbitrary HTTP producers, people and agents.	Notification infrastructure and in-product experiences for end users.

Frequently asked questions

What do I gain with FYInbox?: Your notification destination works across projects independently of their UI. Each source has its own key, while a shared inbox gives you source filters, tags, exact metadata and read/archive state.
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 Novu: a ready inbox for project notifications ComparisonFYInbox vs Courier: bring project activity into one 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