Workflow triggers don't support the encryption field on user inputs the way classic self-service Actions do — setting it is silently dropped with no validation error, so sensitive values entered through a Workflow form are transmitted and stored in plaintext. Teams building secret-collection forms (cloud credentials, API keys, certificates) on the newer Workflows feature have no way to guarantee those values are encrypted before reaching their backend, forcing a fallback to classic Actions for this one capability. This blocks migrating existing secret-collecting Actions to Workflows and leaves a real security gap for any org relying on Workflows going forward.