Comparison
FYInbox vs Courier: bring project activity into one inbox
Send a project result to FYInbox and review it alongside your other projects. People and agents get one inbox outside chat and email; you choose which sources also send Web Push alerts to your devices.
Why FYInbox
Send a project result to FYInbox and review it alongside your other projects. People and agents get one inbox outside chat and email; you choose which sources also send Web Push alerts to your devices.
Built around your projects
Start with a source key and an HTTP request. Your project results arrive in a ready inbox with tags, metadata filters and follow-up links, without configuring channel providers, message templates or customer journeys.
In practice
Post a nightly report with its environment and report URL. Review it alongside your other project results, open the report, and archive the notification when you are done.
Project history
Start with a source key and an HTTP request. Your project results arrive in a ready inbox with tags, metadata filters and follow-up links, without configuring channel providers, message templates or customer journeys.
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 | Courier |
|---|---|---|
| Recipient | People and agents use one central system for project notifications. | Recipients of an application receive messages across configured channels. |
| Setup | Create a source and send an authenticated HTTP request. | Use inline or templated send operations, or journeys, with recipients and channel configuration. |
| History and triage | One central inbox with filters plus read and archive state, outside chat and email. | An embedded Inbox and delivery inspection support the customer messaging lifecycle. |
| Structure | Title, body, severity, source, tags, exact metadata, deduplication and link actions. | Templates, recipient data, event data, preferences and journey context. |
| Delivery | Optional Web Push by source and device, with content preview controls. The full notification stays in the inbox outside chat and email. | Routing spans Inbox, email, push, chat, SMS and other configured channels. |
| 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. | Journeys include branching, delays, fetches, throttling and inspection. |
| Operation | Managed application: create an account and connect your sources. | Operate channel providers, routing, templates and recipient preferences. |
| Scope | Central structured project-notification system for arbitrary HTTP producers, people and agents. | Multichannel customer messaging and notification orchestration. |
Frequently asked questions
- What do I gain with FYInbox?
- Start with a source key and an HTTP request. Your project results arrive in a ready inbox with tags, metadata filters and follow-up links, without configuring channel providers, message templates or customer journeys.
- 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.
Keep exploring
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.