Audit an n8n workflow like a product.

The workflow name explains the outcome, not only the tools used. Each external service dependency is named in the setup notes. Credential names are generic and do not reveal private accounts. The first trigger and final output are easy to identify. Branches for empty, failed, or invalid inputs are handled. Node names explain intent instead of only repeating node types. The export includes no private IDs, emails, tokens, or customer payloads. The workflow can be described in one buyer-facing sentence.