Why the trigger appears first in Analyze
Users read workflow previews as a sequence. Showing the trigger first makes the Analyze list feel like a real execution path rather than a detached summary plus a list of unrelated actions.
The old split view created a false step one
When trigger metadata sits in one card and the action list starts with the first non-trigger action, the page implies that the workflow begins at step two. That is a subtle UX mismatch, but it matters when users are validating source order or looking for the root of a branch.
Putting the trigger at the top of the same list makes the numbering and the mental model agree.
Execution order is more useful than category order here
Analyze is a validation view, not just an inventory view. Grouping by connector can be useful later, but the primary list should answer: what happens first, what happens next, and where does the workflow branch or wait?
That is why the trigger row belongs at the top even though it is also represented in summary metadata.
- Better alignment with how users read source workflows
- Clearer step numbering
- Less ambiguity when debugging conversion notes