If you're talking about using the new Workflow functionality we introduced in Dynamics GP 2013 R2 going forward, everything is already built into the Dynamics GP application, so other than having a Active Directory/domain environment, there is nothing more you really need.
eConnect is not used with default Workflow functionality at all.
Web Services is only used if you want users to be able to approve workflows through email notifications and not have to actually login to the Dynamics GP application.
SharePoint is no longer used at all.
The Workflows themselves are all setup under Administration > Setup > System > Workflow Setup (if setting up emails) otherwise it's all under Administration > Setup > Company > Workflow, where there are multiple windows.
The Workflow Maintenance window is where all the setup and configuration of workflows and workflow steps is done, there is another window where you can add and modify existing workflow email notifications, and then a Workflow Calendar window, where you can setup which days and hours are business days, to use if you want the workflows to move to different approver after a certain period of time.
Workflow uses the user's Windows/domain account, not their GP login, which is why AD is required.
If you're not familiar, I would highly recommend looking at our Dynamics GP blogs, as we have literally tons of Workflow related blogs, including ones that give an overview of the Workflow functionality and also a few On Demand video blogs that go through setting up the various types of workflows available.
Thank you,
