You will first need a custom workflow activity to convert into a custom action. The workflow activity created and deployed in the previous two recipes is a good candidate. Similar to previous extensions done from within Dynamics 365, a System Customizer role is required, along with a Dynamics 365 solution to contain your extension. We will reuse the existing Packt solution created in the previous chapters.