Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Subflows page at /fw/subflows lists all reusable workflow fragments (subflows) for the active organization. From here users can create new subflows, edit existing ones, and delete those that are no longer needed.

​
Overview

The Subflows list displays each subflow as a card showing its name, optional description, node count, usage count, and input/output parameter counts. A delete action requires confirmation via an alert dialog. The “Create Subflow” button navigates to /fw/subflows/new.

​
Who it’s for

No explicit permission gate on this route. All authenticated users with an active organization can view the subflows list.

​
Before you start

  • An organization must be active. If no organization is selected the page shows a message and the list is empty.

​
Steps

  1. Navigate to /fw/subflows.
  2. Review the subflow cards. Each shows:
    • Name
    • Description (if set)
    • Node count
    • Usage count (number of times referenced)
    • Input and output parameter counts
  3. Select the edit icon on a card to open the Subflow Editor at /fw/subflows/:id.
  4. Select the delete icon to open a confirmation dialog. Confirm to delete.
  5. Select “Create Subflow” to navigate to /fw/subflows/new and build a new subflow.

​
Key concepts

  • Subflow — A reusable workflow fragment with defined input and output parameters that can be embedded in automation workflows using a subflow node type.
  • Usage count — The number of parent workflows or automations that reference this subflow.
  • Node count — The number of nodes in the subflow’s canvas definition.
  • Input/output parameters — Declared schema entries that define the data interface for the subflow.

Forms & Workflow

Forms & Workflow core overview.

Governance & parity

This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/fw.tsx
  • src/cores/fw/pages/SubflowsListPage.tsx
  • src/cores/fw/hooks/useSubflows.ts