Workflows Tab

August 23, 2026 · View on GitHub

The Workflows tab is the default dashboard view. It shows your workflow list, folder structure, and lets you create, edit, and organize workflows.

▶ Watch Workflows demo

Start a Chat

Above the workflow list there is a chat box that greets you by name and asks what you want to automate. Type a prompt, optionally attach one file, and pick the credential and model you want. Both dropdowns are searchable and start on your AI defaults.

Sending creates a new conversation and opens it in the Chat tab, where the reply streams in. Supported attachments are text files, images, and PDFs, one per message, same as the chat composer.

If you have no LLM credential yet, the box shows a link to the Credentials tab and sending stays disabled.

Click the x to hide the box. An Ask AI button then appears next to the Workflows heading and brings it back. The choice is remembered in your browser.

Workflow List

The list is a two-pane view: workflows and folders on the left, a preview of the selected workflow on the right.

  • Each row shows the workflow icon, name, description, when it was last updated, and a status chip
  • Workflows can be in the root or inside folders, and pinned workflows appear in their own Pinned group at the top
  • Click a row to select it and load its preview on the right
  • Double-click a row, or press Enter while it is focused, to open it in the editor
  • Use Ctrl+click (or Cmd+click) to open in a new tab
  • Every row carries its edit, copy, pin, and delete actions on the right. On phones they are hidden so the name keeps the full width; long press a row there to open the actions sheet
  • Pin frequently used workflows in the Quick Drawer so you can run them quickly from the Workflows tab and other internal pages

Workflow Preview

Selecting a workflow fills the preview panel beside the list. On screens narrower than 1280px the same panel opens as a sheet from the bottom of the screen instead.

The panel shows:

  • The workflow name, who created it and when, and when it was last edited
  • Open Workflow – opens the workflow in the editor
  • Run Now – opens the workflow in the Quick Drawer, where you fill in its inputs and start the run without leaving the list
  • Description – the workflow description
  • Trigger Configuration – the schedule for a cron workflow, or the listening trigger for an event workflow. Workflows that are invoked over HTTP show a Copy cURL button instead of the raw endpoint and auth prose: it copies a complete request with the right URL, headers, auth placeholder, and a body built from the workflow's input fields. When the workflow publishes a portal, its public chat link appears here too
  • Last Run Details – the outcome and duration of the most recent run, or a note that the workflow has never run
  • Workflow Steps & Sub-agents – the nodes in execution order, each with its model, operation, or schedule and a dot showing whether it is active. Selecting a step opens that node in the editor with its properties panel already open

The panel stays pinned beside the list while you scroll, so it remains readable in a long workflow list.

Workflow Status

Every row carries a status chip derived from the workflow's trigger nodes, its live run state, and — for workflows with no trigger node — how its most recent run was started:

StatusMeaning
RunningThe workflow has an execution in progress right now
ScheduledIt has an active cron trigger
ListeningIt has an active event trigger, such as a Slack, Telegram, IMAP, or WebSocket trigger
PausedIt has trigger nodes, but every one of them is deactivated
APIIt has no trigger nodes and was last run by an HTTP call to its execute endpoint
SubWorkerIt has no trigger nodes and was last run as a sub-workflow by a parent workflow
PortalIt has no trigger nodes and was last run from its portal
WEBIt has no trigger nodes and its only terminal is an HTML output mapper, so calling it returns a rendered web page
ManualIt has no trigger nodes and has never run, or its last run came from somewhere else
Remove ScheduledIt is scheduled for deletion

The API, SubWorker, and Portal chips read the single most recent entry in the workflow's execution history, so a workflow that is called two ways shows whichever came last. WEB is decided from the graph instead, so it takes precedence over those three: a page-serving workflow reads WEB even after it has been called over HTTP. Trigger nodes always win over all of them: a cron workflow that someone also calls over HTTP stays Scheduled.

Use the Status dropdown beside the search field to show only one status. The dropdown lists how many workflows currently match each one. A status filter also reaches inside folders: folders with a match are expanded automatically, and folders without one are hidden until you clear the filter.

Active Workflows

On desktop, the circular badge in the top toolbar shows how many workflows are currently running and refreshes automatically every 10 seconds. Click a non-zero badge to open the active workflow list, which shows up to four rows before scrolling. Select a workflow name to attach the editor to that run's live view. The zero badge is informational and cannot be opened, and the badge is hidden on mobile screens.

Use the workflow search field beside Status, or press Ctrl+F (or Cmd+F), to filter workflows by title or description. Matching workflows inside folders are shown with their folder branches expanded. Press Escape to clear the search.

Folders

  • Organize workflows into folders and sub-folders
  • Create folders with the New Folder button, giving each one a name and an optional description shown under its name in the list
  • Every folder row shows how many workflows it holds, counting sub-folders, alongside its new-subfolder, rename, change-icon, download-as-ZIP, and delete actions. On phones the row shows a single menu button instead
  • Drag a workflow over a folder or sub-folder to see a card-sized destination preview. The highlighted preview shows the full folder path before you drop, and hovering a collapsed folder briefly expands it so you can reach nested folders.
  • Drag workflows between folders or to the root. The dragged card stays visible as a ghost, and the active destination remains highlighted while you scroll.
  • Dropping a workflow back into its current folder is disabled and marked Already in Folder.
  • Rename a folder, or change its description, from its rename action or the right-click context menu

Creating Workflows

  1. Click New Workflow
  2. Enter a name and optional description
  3. The workflow opens in the editor

Import

Drag and drop a JSON workflow file onto the workflow area to create a new workflow. The imported nodes and edges are used to create the workflow; the name comes from the name field in the JSON or the filename. See Download & Import for the JSON format and import options.

Sharing

Open a workflow in the editor and click Share to invite users by email or share with a team. Shared collaborators can view, edit, and run the workflow. Credentials and sub-workflows are not shared automatically; share those separately with the same users or teams. See Workflow Organization and Credentials Sharing.

Editing and Deleting

  • Edit – Change workflow name and description from the row's edit action
  • Delete – Workflows are scheduled for deletion; they move to a trash area before permanent removal

Concurrent Edits

Saving sends the revision your edits are based on, and the server rejects the write if the workflow changed in the meantime — for example because a teammate saved it, or you left the same workflow open in a second tab. Heym then shows a Stale Workflow Detected dialog with two choices:

  • Cancel – Keeps your unsaved changes in the editor so you can reload in another tab and reconcile them
  • Override – Saves anyway, replacing the other person's version

Running a workflow saves it first, so it goes through the same check. If the workflow changed underneath you, the run pauses on the dialog rather than overwriting silently: Override and Run saves your version and starts the run, Cancel Run abandons both and leaves your edits untouched.

The check is part of the save request itself, so it costs no extra round trip and there is no window in which a save could slip past it. Your own changes from elsewhere in the app — a rename, a settings change, a properties-panel toggle — never count as a conflict.

Command Palette

Press Ctrl+K (or Cmd+K) to open the command palette. You can:

  • Search workflows by name
  • Jump to any dashboard tab
  • Open recent workflows