Skip to content
Echopoint Echopoint Docs

Tags & search

Tags group flows into suites. Tag your critical-path flows smoke, your broader coverage regression, then run an entire suite with one command — locally or in CI.

Tag rules

Section titled “Tag rules”
  • Lowercase only
  • Maximum 20 characters per tag
  • Maximum 32 tags per flow

Flows are searchable by full-text query and by tag, in the UI and the CLI.

Tagging flows

Section titled “Tagging flows”

In the UI, add and remove tags on the flow. From the CLI, use echopoint flows tag:

Terminal window
# Tag specific flows
echopoint flows tag <flow-id> --add smoke --add payments


# Remove a tag
echopoint flows tag <flow-id> --remove payments


# Tag every flow matching a full-text search
echopoint flows tag --query "checkout" --add smoke


# Retag flows selected by their existing tags
echopoint flows tag --match-tag payments --match-tag checkout \
  --match-mode all --add regression

--match-mode controls how multiple --match-tag values combine: any (default) selects flows with at least one of the tags, all selects flows with every tag.

Running a suite by tag

Section titled “Running a suite by tag”

echopoint flows run accepts --tag instead of flow IDs and runs every matching flow, up to a cap of 50 flows per invocation:

Terminal window
# Run the smoke suite
echopoint flows run --tag smoke


# Flows tagged both smoke AND payments, three at a time
echopoint flows run --tag smoke --tag payments --match-mode all --parallel 3

The exit code is 0 when every flow passes and 1 when any flow fails, so tag-based runs slot directly into CI. The GitHub Action takes the same selection through its tags and match-mode inputs:

- uses: nanostack-dev/echopoint-cli@v1
  with:
    api-key: ${{ secrets.ECHOPOINT_API_KEY }}
    organization-id: ${{ secrets.ECHOPOINT_ORG_ID }}
    tags: smoke
    parallel: '3'

Suite pattern

Section titled “Suite pattern”

A simple two-tier setup that scales well:

  • smoke — a handful of fast, critical-path flows (sign-in, create payment, fetch status). Run on every push.
  • regression — the full set, including slower flows with Delay nodes and Module chains. Run before releases.

Because a flow can carry up to 32 tags, the same flow can belong to smoke, payments, and regression at once — tag by both suite and domain, and slice either way at run time.

Next steps

Section titled “Next steps”