Blog
Give workflow notifications a place outside chat
When a workflow finishes, you may still have something to review. A catalog import can leave rejected records. A draft can be ready for a final check. An agent can return a result with warnings. Keep those outcomes in a notification inbox for people and agents, outside chat and email.
Start with the next step
A useful notification helps you decide whether to act now or review the result later. Give it a clear outcome, a short explanation and a link to the place where the work continues.
In FYInbox, an import, a publishing workflow and an agent run can report to the same account. Sources and tags keep their notifications distinguishable. Bounded metadata preserves the references and values needed to understand each result.
A catalog import that needs attention
An example catalog workflow accepts 148 records and rejects two. Its notification reads Catalog import needs review. The body explains that two records need attention. Metadata holds the batch reference and counts, and Open import report identifies the next destination.
You open the report and inspect the rejected records in the source system. FYInbox keeps the notification available for review, subject to account limits. Opening its link does not correct the records or rerun the import.
Keep the notification separate from the work it describes
Continue a conversation in chat, handle customer correspondence in the appropriate channel, and review operational results in FYInbox. This gives project notifications one destination without turning each result into another conversation.
Use the same FYInbox account in a web browser on your phone or computer. The web inbox refreshes periodically while active; browser push is optional. Access across devices is useful, but it is not an exclusive FYInbox capability.
Agents are part of the notification system too. They can send results and retrieve a known notification ID within their source key's scope. These source-key HTTP operations do not expose an account-wide listing or execute follow-up actions. Consented OAuth MCP connections offer discovery, listing and read/archive updates within approved permissions.
Start with one workflow outcome
Choose a result.
Pick an outcome you regularly need to inspect, such as an import exception or a draft ready for review.
Keep the context small.
Use non-secret references, concise status and a link to the source. Leave full customer records and documents in their owning system.
Preserve event identity.
Use a stable deduplication key across delivery retries. Keep a later, distinct outcome separate.
Connect through a generic HTTP request in your automation tool. Begin with a title and add context only when it helps someone understand the result or find the next step.
Primary sources
Last verified .
Frequently asked questions
- Is this a customer case study?
- No. The workflow, records and results on this page are hypothetical examples. They do not describe a customer or measured business results.
- Does an action run the next step?
- An action opens an HTTPS destination or an email composer. Review, approval and retries happen in the source system; receiving or opening a FYInbox notification does not complete those operations.
- Does FYInbox replace chat or customer messaging?
- FYInbox gives project notifications a central home for people and agents. Conversations and intentional customer messages stay in the tools used to handle them.
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.