Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cassidyai.com/llms.txt

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

When a Workflow runs, every action’s output is shown in the results by default. For Workflows with preprocessing steps, API calls, or other internal operations, you may want to hide these from end users to create a cleaner, more focused results view. Hidden actions still execute normally — they just don’t appear in the output that users see when viewing run results.

​
Hide an action

1

Open the Workflow editor

Navigate to the Workflow and click Edit to access the editor.
2

Open the action menu

Click the … button in the top-right corner of the action block you want to hide.
3

Toggle Include in Workflow output

Click Include in Workflow output from the dropdown menu. This toggles the action’s visibility in the results view.
Action block menu showing the Include in Workflow output option
4

Confirm the eye icon

An eye icon appears on the action block, indicating it is now hidden from end-user results.
Action block with eye icon indicating the action is hidden from results
To show the action again, repeat the same steps — click the … menu and toggle Include in Workflow output off.

​
What stays visible

  • Test Workflow — hidden actions are still fully visible when you use the testing interface in the editor. This lets you debug without affecting what end users see.
  • Run results and Previous Runs — hidden actions do not appear in run results or the Previous Runs view.
The Interface tab’s Outputs list is separate: it highlights specific action variables on the Run tab after a successful run. Hiding an action from workflow output does not remove its variables from that list if you explicitly added them as outputs; remove them on Interface if you no longer want them shown there. See Customize the Workflow run view.
Use this feature for actions like Scrape Webpage, Categorize Text, Send API Request, or any step that produces intermediate data your users do not need to see. It keeps the output focused on the final, meaningful results.

​
Next steps

Run and test Workflows

Learn about the testing interface and debugging tools.

Fallback values

Handle errors gracefully when actions fail during a run.