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.

As of mid 2025, Rewst also offers kits. A kit is a collection of pre-built, pre-defined tasks that provide a quick start to setting up solutions to specific business needs, or to demonstrate all available actions within a given integration. For example, if you have a Halo PSA kit, there will be an actios or automations Rewst has identified that are smaller use cases compared to our larger Crates.

Kits are a newer feature of our Crate Marketplace. Check back as the collection grows. See our up-to-date list of available kits here.

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.

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. 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.

An example of subworkflows, flowing out of a larger executing workflow
The Subworkflow button, under the Attributes column of the workflows list page

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.

  • 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.

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 here.

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 workflows list page, without any filters applied

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.

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:

  1. Navigate to Automations > Workflows.

  2. Search for the specific workflow.

  3. 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.

When you delete the result of a workflow, consider it to be fully deleted. Only delete results when you are confident that they will not be needed. The result will remain in Rewst's database backup snapshots for a short length of time until it is past the retention period, at which point it will be purged. Meta data and stats about the deleted workflow execution remain in the system. Deleting a workflow execution will not affect time saved or remove time saved.

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.

The dialog that appears when hovering over trigger counts

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 RoboRewstyKitsSubworkflows

Last updated

Was this helpful?