Automations

Runs and the overview

Every run is an item with fields, files and an outcome. The overview turns them into a work list your team can filter, assign and review.

The Overview tab of an automation, and the workspace-wide Activity page, show runs as items. The automation's settings decide what an item is called and which of its fields are columns.

The overview tab

At the top sits a quick-add composer: paste text, drop a file, or fill in the typed inputs, and a run starts right away. Below it a filter bar narrows the list by time (Today, Last 7 days, Last 30 days, a custom range) and status, with a search box. An attention line such as "3 orders need attention" counts the items that are waiting for input, failed, or need review.

Each row shows the item title, its status pill, the assignee, and the columns you configured. Clicking a row opens the run panel.

The run panel

  • Outcome: a summary of at most a few sentences.
  • Fields: the structured values the run set, for example vessel, port and total.
  • Files: deliverables with Preview and Download.
  • Steps and Trace: what ran, in what order, and every call it made.
  • Assignee and review: Approve, Reject, or Clear review.

Fields and review

Steps can be marked to produce fields, and agent steps can set fields explicitly. The automation's overview config can name fields that must not be empty; a run that leaves one empty is flagged Needs review automatically. This is how "flag it when a price is missing" works: the step leaves the price empty and the review flag follows.

Insights

The Insights tab shows runs per day by outcome, runs by hour, the success rate, average duration, credits used, how many runs need review or failed, a breakdown by source and per step, the busiest hours, and recent failures.

The Activity page

Activity in the sidebar lists every task across every automation in the workspace with the same filters plus an automation filter, so an operator can work one list instead of visiting each automation.

Sources

Each run carries its source: the app, a chat, a channel, a meeting, a schedule, an event, Slack, WhatsApp, Telegram, an MCP client or the API. The Insights tab breaks runs down by source.