See what happened
Read the outcome, source and severity before opening another tool.
Notification system for people and agents
Keep your workflow notifications in one inbox.
Bring results from n8n, Zapier and other HTTP workflows into FYInbox. Keep notifications for people and agents together, with context and a link to the next step, outside Slack, Telegram and email.
Example workflow results
Three sources, one inbox.
Explore synthetic notifications from an import, a publishing workflow and an agent run. Open an example to inspect its context and the link that would lead back to the source.
Example inbox
Synthetic data · no account connected
1 · Send a workflow result
POST /api/v1/notifications2 · Review the notification
3 · Open its context. Open an example to inspect its context and follow-up destination.
Project notifications together
Keep the result where you can review it.
A workflow result may need a quick check or a decision later. FYInbox keeps project notifications for people and agents in one place, outside conversation threads.
Keep useful context
Attach a record reference, a run ID or a short explanation of what needs attention.
Return to the source
Use an explicit link to open the record, report or run where the next step belongs.
Connect a workflow
Start with one outcome you need to review.
Use a generic HTTP request step to send a result into FYInbox. Your workflow keeps doing its work; the notification gives people and agents the context.
1. Create a source
Name the workflow in FYInbox and create its API key. Save the key in your automation tool's credential store.
2. Send the outcome
Send JSON to the notification endpoint. Start with a title, then add useful context and a follow-up link.
3. Review your inbox
Open FYInbox to review the notification. Filter the inbox, open the source record, or mark the notification read and archive it.
Examples of useful outcomes
Imports, publications and agent runs.
These hypothetical scenarios show how different workflows can report to the same notification system for people and agents.
An import needs attention
Keep the batch reference, accepted and rejected counts, and a link to the records that need review.
A draft is ready
Keep the document reference and review status together with a link to the draft.
An agent finishes a run
Keep the run reference, a concise outcome and a link to the result. Use the documented API to retrieve a notification whose ID is already known.
Context you can use
Give each notification a clear next step.
Keep project context structured so people and agents can interpret the outcome without reconstructing a conversation.
Sources and tags
Keep producers distinct and use tags to group related notifications across sources.
Metadata
Store bounded string values such as record references, run IDs and counts. Use exact metadata filters in the web inbox.
Follow-up links
Open the source record over HTTPS, or open an email composer with a mailto link. The action does not execute a workflow or send a message for you.
Stable event identity
Reuse the same deduplication key for delivery retries. While the original notification exists, FYInbox returns it without creating another copy.
Your project activity
One account for the work you need to follow.
FYInbox centralizes your project notifications for people and agents. Conversations and intentional customer correspondence stay in the tools where you handle them.
Review your own workflows
Use the web inbox to follow outcomes from the projects and automations you run. The account model is one person per account.
Continue in the source system
Open the relevant record to review, approve or retry work there. FYInbox stores the notification and its links; those links do not complete the work inside FYInbox.
Choose what you send
Keep credentials separate from notification content.
Store the source key in your automation tool's credentials. Send only the context needed to recognize the event and locate the next step.
Access through your account
Sign in to review your inbox. A source API key can access only the operations and notifications within its source scope.
A key for the source
The key is shown once when created and can be revoked. Keep it out of notification text, links and shared workflow examples.
A reference instead of a full record
Send a non-secret record reference and a link to the source system. Keep customer details and full documents in the system that owns them.
Review the security and data boundaries in the public docs and wire contracts.
Before you connect
Know how the inbox works.
FYInbox brings project notifications together for people and agents. These are the current connection, device and API boundaries.
How do I connect n8n or Zapier?
Use n8n's HTTP Request node or a generic API request in Zapier to send JSON with a source bearer key. API by Zapier is currently in beta and requires a paid Zapier plan. These are generic HTTP connections.
Can I use the same inbox on my phone and computer?
Sign in to the same FYInbox account in a web browser. The inbox uses the same stored notifications and read/archive state across sessions. Each browser still needs its own permission and subscription if you enable Web Push.
How does the inbox show new notifications?
The web inbox refreshes every ten seconds while its tab is visible and focused, and refreshes when it regains focus. This is web polling. The public API does not provide a live subscription to new account notifications.
Do I have to enable push?
No. You can review the web inbox without push. Web Push is optional and configured per browser subscription, with source and preview preferences.
What happens when I open an action?
An HTTPS link opens its destination. A mailto link opens an email composer. FYInbox does not run an approval, retry a workflow or send the email when you receive a notification.
What can an agent do through the public API?
An agent can create notifications, retrieve a known notification ID, and add or modify metadata within its API key's source. These source-key HTTP operations do not list the account inbox, mark items read, archive or execute actions. Consented OAuth MCP connections also support discovery, listing and read/archive updates within approved permissions; see the MCP documentation.
How much history can I keep?
Storage, retention and request limits depend on the account and deployment policy. Check account usage in Settings and read the Limits documentation. The inbox does not promise unlimited history.
Is the TypeScript SDK publicly installable?
The TypeScript SDK is in private preview inside the FYInbox workspace. Use the public HTTP contract for an external integration; public package distribution has not been announced.
Bring your next workflow result into FYInbox.
Keep project notifications for people and agents together, with context and a link to the next step, outside chat and email.
Create account