Skip to main content

Rewst Terminology


Crates are bundles of forms, workflows and triggers to make it easier to deploy a number of components into a single package.

This marketplace is available to all and is getting constant updatess with new additions.

Additional information on crates can be found here.


The workflow is the heart of Rewst. Everything that is done that requires some connection to an API and an action, is done within the workflow UI.

Additional information on workflows can be found here.


The integrations are the various products that Rewst has connections into. You will need to supply various details such as an API key and URL for the product.

Additional information on integrations can be found here.


Templates can be used as a central store for repeated text. For example, if you always want to create a ticket with the same information you could put that in a template and reference the template within the action itself.

Additional information on templates can be found here.


Forms are one of the main ways to get data into a workflow. You can use a selection of fields, both static and dynamic, to retrieve information from a user and then that information is passed into the workflow on submission.

Both dynamic and conditional fields can be used here. For example if you list groups live from your M365 tenant and then set it to a certain group, you can show other fields as a result of that.

Additional information on forms can be found here.


Actions are what live inside of a workflow. Each integration has a number of actions within it (and more added constantly!). You grab these actions from the left menu on a workflow, drag them onto the workflow UI and that is what runs when you run the workflow.

Additional information on actions can be found here here.

Context Variables

Context Variables are variables specific to the running workflow. They are referenced by CTX.variable_name.

Additional information on context variables can be found here


Transitions are found on the bottom of every action. These determine the path the workflow will take. For example if "Success", then you'll have an arrow coming from that transition to the next action. You also have transitions for failure, always and custom conditions.

Additional information on transitions can be found here.