Answer
Not directly — Workflow Designer's steps call projection actions, not raw database procedures, so the PL/SQL needs to be wrapped in a projection's custom action first, and the workflow then calls that action like any other API task. See make a PL/SQL package available as a projection custom action.