What are the components of a Flow Action?

Subprocesses are not a defined component of a Flow Action; the processing logic is contained within Action Steps, not a separate subprocess layer.

This option omits Inputs and Outputs, which are essential structural components of a Flow Action that define its data contract with the calling flow.

A Flow Action is a reusable automation unit in Flow Designer structured around three components: Inputs define the data the action receives from the calling flow, Action Steps contain the ordered logic or operations the action performs (such as scripts, REST calls, or record lookups), and Outputs define the data the action returns to the flow after execution.

Indexes are not a component of Flow Actions; this option conflates Flow Action structure with unrelated database or search concepts.