Comments and Notifications

Automations are team property: one person builds a workflow, another reviews it, and someone else is the first to hear when it fails. This concept keeps that conversation attached to the work itself, with comments pinned to individual nodes on the FluidGrids canvas, and gathers everything that needs attention into a single notifications center.

The problem it addresses is scattered context. Review feedback on automations usually happens in chat threads that lose track of which step is being discussed, and alerts about failed runs, quota limits and mentions arrive through different channels with no clear path back to the cause. The design brings both conversations and alerts into the workspace, next to the workflows they describe.

The first illustration shows a sample Order-to-Cash workflow open on the canvas, with teammates' avatars and an online count in the top bar. A comment badge and an avatar pin sit on the payment invoice node, and a popover shows the thread with React and Resolve actions. A Comments panel filters threads by All, Open and Resolved and shows replies, emoji reactions and an approval-for-activation note, while typing @ in the composer opens a picker of workspace members. The second illustration shows the Notifications page, with tabs for All, Alerts, Runs, System and Mentions. Most entries, from a failed run to a quota warning or a mention, carry a direct action, and a settings card chooses which channels deliver alerts.

Within the wider product, comments sit naturally beside versioning and publishing, since a reviewer can record an approval in the thread before a workflow is activated. Notifications link straight into runs, workflows, templates and connections, so an alert becomes the shortest path to the fix rather than one more message to chase.