Workspace Home and Command Search

Automation platforms fail people quietly. A schedule stops firing, one connector starts returning warnings, a teammate publishes a change, and nobody notices until a customer does. This concept addresses that by making the first screen after sign-in an honest status report on everything the workspace is running, and by putting a single search box in front of every object the workspace contains.

The first illustration shows the home view. A persistent left rail carries the main sections of the product - overview, workflows, runs, schedules, connections, nodes, templates, analytics, audit logs and settings - and anchors a usage meter and plan card at its base. The main column opens with a personal greeting, three starting actions for creating a workflow, browsing templates and inviting teammates, and a row of metric tiles for active workflows, runs today, success rate and average run duration, each carrying a change indicator against the previous day. Beneath that, a recent-runs list with per-run status pills sits beside a seven-day run-volume chart, a grid of workflow cards showing state badges and last-run times, a quota ring with a reset countdown, and an activity feed of invitations, completions, warnings and failures.

The second illustration shows a workspace home with the command palette open over it. A shortcut chip sits next to the input, and a short typed query is already fanned out into labeled result groups with per-group counts: workflows with their state and a one-line description, a run identified by its execution reference and outcome, nodes tagged by role such as transform or action, a stored connection showing its provider, and a matching template. A keyboard legend along the bottom edge spells out navigating, opening and dismissing the palette.

Together the two screens define the everyday entry point. The design envisions the dashboard as the place where you notice something, and the palette as the way you reach it in one movement, without learning where each object lives in the navigation. From either surface the intended next stop is the builder, a run detail, or a connection - the deeper surfaces covered by the other concepts in this product.