Workflows
What is a workflow?
Workflows, made up of actions and triggers, 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.
Crates 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 Cluck University. 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.
Why build workflows?
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.
Find and use workflows in Rewst
Access workflows in the Rewst platform by navigating to Automations > Workflows in the left side menu. Create a new workflow from scratch by clicking Create Workflow.

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 At, Updated By, Attributes, and Tags columns each offer the option to filter your results by relevant criteria, with attributes and tags filters operating for both inclusion and exclusion of desired parameters. You can also use Search in the top center of your screen 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 workflow builder, a canvas for assembling your workflows. See our documentation for how to use the workflow builder here.
Synced versus unsynced workflows
Synced workflows unpacked from Crates can't be edited, and automatically update when Rewst makes changes. For more on synced workflows, including how to identify them, see our documentation on Crates and syntonization here.
View specific workflow results
The general results page will show you the results of every workflow that has run in your organization. Apply a date range filter to view execution results from a specific time period, up to 30 days prior.
To see all results for a specific workflow, you can do the following:
Navigate to Automations > Workflows.
Search for the specific workflow.
Select
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.

View triggers for a specific 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.

Subworkflows
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. Sub-workflows help you simplify complex processes, reuse logic, and manage error handling and data gathering cleanly in your Rewst automations. You can create your own subworkflows, or use one of our pre-built subworkflows, cataloged in this section of our documentation site.
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.
When addressing various objects, the equivalent of a for each, we can pass all of the objects to a sub-workflow and get the output back of each object.
Run logic inside a subworkflow to isolate errors, apply retry or skip logic, and handle failures cleanly while using with items, without failing your parent workflow.
This is typically the best method for using with items loops inside Rewst. This allows you to run checks and balances on each iteration to prevent or handle possible failures on a per-item basis.
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.
Configure the subworkflow inputs and output
Click to Navigate to Configure Workflow Settings. Then, configure which data comes into the subworkflow, and which data you want returned to the parent workflow upon completion— your inputs and outputs. There are a variety of input types. Below are a few of the most common ones.
![A screenshot of a sub-workflow configuration screen. At the top, there are sections labeled "Variable Configuration" and "Input Configuration" with a plus icon. Three input fields are defined: list (type: List) with default value {{ [ ] }}, description "used for passing JSON object," optional required checkbox. boolean (type: Boolean) with default value {{ true }}, description "true or false," optional required checkbox. input_configuration (type: Text) with description "configure Inputs in the sub-wf," optional required and multiline checkboxes. Below, an "Output Configuration" section contains a field: output_data with value {{ "The sub-wf test data" }}. Each entry includes text fields for name, label, type, default value, and description, along with a red "Remove" button. At the bottom, there are "Cancel" and "Submit" buttons. Highlighted in red boxes are the "Input Configuration" and "Output Configuration" headers, as well as a pencil icon in the top-right toolbar.](https://docs.rewst.help/~gitbook/image?url=https%3A%2F%2F1835401289-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FAQQ1EHVcEsGKBPVHmiav%252Fuploads%252FMzz2xWTeCU1aqI7WruMI%252Fimage%2520%2866%29.png%3Falt%3Dmedia%26token%3D4a53c87d-1036-4dbd-bbd1-7d623bd94cc6&width=768&dpr=4&quality=100&sign=819ab16&sv=2)

Enable publish results in the parent workflow
This setting publishes the configured output, allowing your parent workflow to use the results of the subworkflow immediately.
Find your desired subworkflow in the Workflows actions menu in the left side of theWorkflow Builder.
Drag your subworkflow from the actions list to the Workflow Builder canvas within your parent workflow.
Click on the subworkflow to expose its configuration settings.
Enter
sub_wf_results
in the Publish Results As field.Click Publish.

Access subworkflow data
Results for subworkflows are nested inside published results for workflows. For example, the following Jinja wiuld contain the subworkflow data.
{{ CTX.sub_wf_results.output_data }}

Additional workflow documentation
Workflow builder: How to set up a workflowActionsTask transitionsData aliasesBest practices for designing workflowsAdvanced workflow operations menuData input and output: Input variables and context variablesOption generator workflowsCompletion handlers and workflow wrappersBoolean logic in Rewst workflowsDocument with RoboRewstyKitsSubworkflowsLast updated
Was this helpful?