Output Tab

Where to find workflow execution results, what each field means, and how to debug a run from the Output view.

The Output tab is where you inspect, debug, and export everything a workflow produced on a given run. It replaces the older Logs tab and is the primary place to confirm a workflow did what you expected, work with the results directly, and push them into downstream tools.

Opening the Output tab

  1. Open the workflow from the Workflows list.
  2. Switch from Canvas to Output using the view switcher in the workflow header.
  3. Each row in the table is one execution. Click a row to drill into a specific run.

Tip: after a successful Test Flow from the header, Trigify automatically opens the Output tab and refreshes so the new run appears straight away.

The Output table

Executions render as a table with one row per run. The table is built for both quick scanning and deep inspection.

  • Run status column — succeeded, failed, partial, in progress, or cancelled, with the run start time. Manual Test Flow executions are tagged with a Test badge.
  • One column per workflow step — each cell shows an action-specific summary (HTTP status, Slack send state, enrichment results, loop iteration counts, and so on) rather than a raw blob.
  • Running rows show a spinner and a stop button. Click it to cancel the run in flight.
  • Failed rows expose a Go to Error link in the status cell that scrolls straight to the step that broke.
  • The first column is pinned while you scroll horizontally, so status and run info stay visible.
  • Resizable columns — drag a header edge to resize, double-click to reset.
  • Sortable columns — click a header to sort ascending or descending.
  • New rows and freshly populated cells flash briefly so you can see what changed when a workflow is running live.

Auto-refresh and pagination

  • The table auto-refreshes every 5 seconds while you're viewing it. Toggle auto-refresh off in the footer, or hit Refresh now to pull immediately.
  • Pagination sits in the footer. Choose 25, 50, or 100 rows per page and step through history with the page controls. The footer shows the current range, e.g. Showing 1 to 25 of 412 results.

Loop iterations and nested arrays

  • Loop steps can be expanded from the status column into one sub-row per iteration, labelled Iter N/M, with the step output for each iteration.
  • Map an array to a nested sub-table. When a step returns an array of objects, open it from the detail panel and choose Map to Table. Trigify auto-detects columns from the array items and inlines the sub-table beneath the run. Each nested sub-table has its own pagination (25 per page), full-content dialog, remove button, and CSV export.

Inspecting a step in detail

Click any populated step cell to open the detail side panel. From here you can:

  • Switch between Fields (structured browser with type icons and previews for arrays, objects, URLs, and scalars) and Raw Output (full JSON or text).
  • Filter fields with a recursive case-insensitive search that walks through nested objects and arrays.
  • Copy JSON of the resolved output or error payload with one click.
  • For errors: see a summary, detail, location, suggested fix, and retry guidance, and use Fix with AI to open chat pre-loaded with the error context.
  • For workflow-level failures with no failed step, open a synthetic Workflow run detail with the run error and stack.

Adding custom columns

From the Fields view in the detail panel, any scalar field can be promoted to a new column on the Output table.

  • Click Add as column on a scalar field. Give it a custom column name in the popover.
  • Promoted columns persist on the workflow (stored in workflow metadata) so anyone opening Output sees the same columns.
  • Adding the same field twice is a no-op.
  • Hover a custom column header and click the X to remove it.
  • Only scalar fields (strings, numbers, booleans, etc.) can be promoted. Arrays use Map to Table instead.

Viewing full cell content

Long step summaries, custom column values, and nested sub-table cells expose a View full content action that opens a dialog with the formatted value and a copy button. Use this for long text, large JSON payloads, or anything that doesn't fit comfortably in a row.

Exporting to CSV

  • Click Export CSV in the top right of the Output tab. A popover lets you select or deselect individual columns, or toggle Select all, before downloading.
  • The file is named {workflow-slug}-outputs-{YYYY-MM-DD}.csv.
  • Exports use comma delimiters with proper quote escaping for values that contain commas, quotes, or newlines.
  • The export covers the rows currently loaded in the Output table (the current page). Loop iteration sub-rows and nested sub-table rows are not included in the main export.
  • Nested sub-tables have their own Export CSV button that exports just that sub-table, named {workflow-slug}-{mapping-slug}-{YYYY-MM-DD}.csv.

Using Output to debug a run

If a workflow looks like it "did nothing", walk the Output tab top-down:

  1. Confirm the trigger payload contains what you expected.
  2. Open each step's detail panel and check that its input matches the previous step's output.
  3. If a downstream integration (Slack, Sheets, webhook) shows nothing, check the Output of that step first. The delivery state is reported there, not in the destination tool.
  4. On a failed run, use Go to Error in the status cell, then Fix with AI from the error detail panel to debug with chat.

Empty states

If you've never run the workflow, Output shows No execution logs yet. Run a test to see outputs here. Use Test Flow from the header to produce the first run.

Related articles