Last updated
Was this helpful?
Last updated
Was this helpful?
Workflows, made up of and , are the main component of Rewst's automated business processes. They gather relevant data from integrated tools such as a PSA or RMM, process it using conditional logic, and execute automated actions relating to that data. Workflows are the key to unlocking automation in Rewst.
contain pre-built workflows. Workflows can also be built from scratch, or edited to match your custom needs.
We recommend you only edit the pre-built workflows that come in Crates after taking our courses in . This is a more advanced way to use Rewst.
Before building any workflow, remember to sketch out what you'd like the workflow to look like, and identify the trigger that will kick it off.
While the pre-built workflows in Crates are the quickest way to get started, a workflow built custom to your situation can offer powerful, personalized efficiency measures that fit your particular MSP and customer needs.
A subworkflow is a workflow that is also a part of another workflow. In Rewst, every automation can function as either a larger executing workflow or a smaller subworkflow.
In the example below, you have a main workflow called Create Ticket. In it, you choose which PSA the organization has. Once that has been decided, you then go to a subworkflow, which encompasses the actual creation of the ticket. Note the pink border and icon on the action, denoting that it is a subworkflow.
Click on a subworkflow to navigate directly to it. You can also view subworkflows on the main workflow page, indicated by the green Subworkflow button under the Attributes column. Clicking will reveal which workflow the subworkflow is a part of.
There are a few reasons to set up subworkflows.
Ensure a tidy workflow. Rather than having 20 steps per PSA on a single workflow, we can split it up for convenience and ease of understanding.
Subworkflows allow you to write a workflow once and reuse it multiple times. Subworkflows also accept parameters, making them adaptable for different use cases.
Smaller, self-contained workflows are easier to test and debug individually.
Access workflows in the Rewst platform by navigating to Automations > Workflows in the left side menu.
The general results page will show you the results of every workflow that has run in your organization. To see all results for a specific workflow, you can do the following:
Navigate to Automations > Workflows.
Search for the specific workflow.
Select the graph icon in the far right corner for that specific workflow.
This will take you to a new page that will show all the results of that workflow.
From the workflows page, you can view triggers associated with each workflow, without leaving that page. Hover over the workflow's triggers count in the Attributes column to see a list of every trigger linked to your workflow, and toggle each on or off to suit your needs.
When addressing various objects, the equivalent of a , we can pass all of the objects to a sub-workflow and get the output back of each object.
Workflow wrapper is an informal term sometimes used colloquially by the ROC to describe a situation where a primary workflow is used in a separate workflow as a subworkflow. More information on workflow wrappers can be found .
The list of workflows that appears in the center of your screen will include both the workflows you create and the workflows unpacked from Crates. As you continue to set up automation in Rewst, this list can grow quite a bit. The Updated By, Attributes, and columns each offer the option to filter your results by relevant criteria. You can also use Search in the top right corner to find a particular workflow, and the icon to the right to choose which columns you'd like to see in your workflow list.
Once you create a workflow, you'll be taken to the , a canvas for assembling your workflows. See our documentation for how to use the workflow builder .
