You are probably familiar that using SharePoint Designer you can consume SharePoint REST API.
The API is very flexible and allows you to manipulate items, lists and almost every aspect of SharePoint. On the Internet, you can find many articles describing how to use it and how to correctly configure the workflow.
In most cases this will be very simple use cases, it’s supposed that this is because the complexity of the workflow increasing dramatically with number or required requests and processing data.
We are in Plumsail try to simplify things, that is why we added “ Get Items by Query ” workflow action.
Let’s have a look at the following article: Call HTTP Web Service Using SharePoint Designer 2013 (SPD)
A guy describes how to create a simple workflow which gets items from a list and log a Title of each item to the history list.
I reproduced the case and it takes almost half an hour to create it.
After that, it was installed Workflow Actions Pack and it was created the same use casebut using actions from Workflow Actions Pack. Of course, it took just 5 mins and the final workflow looks more clear for anyone who has to maintain it in the future.
Now let’s imagine that you need to implement more complex workflow, indeed in a production environment, it was saw workflows which take 3-5 pages and it’s hard to understand their logic and it’s not mentioned that consultant that creates it costs a lot of money.Using Actions Pack you can save your time and your money. Moreover, Workflow Actions Pack allows you to get data from another site or even tenant, it opens new possibilities comparing with OOB workflows.