Categories

Additional links

What is a workflow?

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.

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.

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.

Find and use workflows in Rewst

Access workflows in the Rewst platform by navigating to Automations > Workflows in the left side menu.

View specific workflow results

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:

1. Navigate to Automations > Workflows.

2. Search for the specific workflow.
3. 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.

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.

Additional workflow documentation

Welcome to the New Cluck U

We leveled up Cluck University, making learning in Rewst smarter and more flexible than ever.

Now, you can register for courses, track your progress, and explore educational content — all from inside the Rewst app.

What’s new in Cluck U:

• Learn your way – Dive into self-paced courses or join live events on core topics.

• Fresh content – Courses have been revamped based on your feedback.

• Smarter search – Find exactly what you need with new search and filter options.

Ready to jump in?

Additional education resources

Workflow Builder

The workflow settings toolbar

At the top of the workflow builder, you'll find several settings buttons.

Build a workflow

Set up the trigger

2. Name your trigger with something simple but descriptive.

3. Toggle Enabled to on.

6. Set your trigger criteria, if required for your workflow.

7. Think about which organizations you want the trigger to run for.

   1. Selected Organization (Org Name) will be toggled on by default. Toggle to off if desired.

   2. If you want the automation to work for your main org as well as all child organizations, toggle All current and future managed organizations to on.

   3. If you want the automation to apply only for certain organizations, select them manually in the Organizations selector field.

8. Click Submit to save the trigger.

Create the workflow

1. Click Create.

2. Give your workflow a Name, and add any tags you would like via the Tags drop-down selector.

3. Click Submit. This will launch the workflow builder.

Drag the action

1. Search for your desired action in the left side menu.

2. Click on it, drag it, and drop it onto the canvas.

3. Repeat this process to add all needed actions to your workflow.

Configure tasks

1. Click on the placed task, which will open a configuration dialog featuring two sections:

   1. A set of basic details fields at the top:

      1. Name: A user-editable field for the task's identifier.

      2. Reference: The integration pack and task description.

      3. Output: Specifies where the task's output gets stored in the task logs.

      4. Task ID: The unique ID for referencing this task.

      5. Description: A user-fillable text box for additional task information.

      6. Publish Result As: A friendly name you assign for the task's results that you can use as an a context variable for calling it's content in future tasks.

   2. Four distinct tabs beneath the basic details:

      1. Parameters: Unique to each task, this tab houses options for defining the task's behavior during execution, including settings for endpoints, filters, conditions, and query parameters.
      3. Mocking: This tab provides the option to simulate the task's function with a user-defined result, useful for testing and debugging.

      4. Time Savings: In this tab, specify your estimate of the time a human would need to complete the task. This is used for creating Time Entries in PSA platforms.

      5. Security: This tab allows for meticulous redaction of sensitive information within workflow tasks. This is especially vital when using generic HTTP actions for services without official integrations, where API tokens or other sensitive data in headers could be exposed in results.

         2. These queries can be entered manually in the editor, or chosen from the field's drop-down selector.

3. Click Test to see if your workflow executes as desired.

4. Click Publish to save your changes and push them to the desired effect.

Add time saved to a workflow

One of the key metrics you can use to understand the value added by your automations is time saved. You can configure this in Rewst by identifying how long it takes to manually work through your process before automating it and adding it into your workflow.

1. Click on the workflow that you want to configure.

3. Enter the amount of seconds it takes for the process in Time Saved (seconds).

4. Click Submit.

Add, edit, or delete workflow notes

2. Click and drag it to the desired location on the canvas.

4. To delete notes, right-click the note and click Delete Note.

Additional workflow builder features

Select multiple elements on the canvas

Select multiple workflow tasks and notes simultaneously by drawing a selection box around them.

1. Hold shift and drag your mouse, or hold the middle-mouse button and drag your mouse.

2. Once you’ve selected multiple tasks or notes, move them by dragging the selection box to the desired location.

3. With multiple tasks or notes selected, you can perform the following actions:

   1. Delete Items: Press the delete key, or right-click the canvas and select Delete Selected Tasks.

   2. Duplicate Items: Press ctrl+d, or right-click the canvas and select Duplicate Selected Tasks.

Favoriting actions

Commonly used actions can be favorited to easily find and add actions to workflows. When favorited, actions can be found in the favorites section and added on the workflow canvas by right-clicking.

1. Find the action you want to favorite.

3. To add a favorited action to your workflow:

   1. Right-click on the workflow canvas.

   2. Add an action from the favorites section.

Retrieve the name of a workflow

Run the command {{ WORKFLOW.name }} .

Similarly, if you're searching for the name as it relates to completion handlers, run the command {{ COMPLETED_WORKFLOW.WORKFLOW.name }} .

What are task transitions?

Task transitions are the bridges that connect different tasks, ensuring that workflows move forward as designed. They're represented by the small rectangles found directly beneath each task. Depending on the criteria set, one task might branch out to multiple subsequent tasks. When you interact with these rectangles by clicking on them, a configuration menu appears. Note that this is a different menu from what is seen when you click on the task itself.

Task transition configuration options

• Edit Transition: Buttons beside the Edit Transition title give you options to either clone the current transition or remove it if it's no longer needed.

• Custom Label: An editable field allowing you to give a meaningful name to the transition, aiding clarity as your workflow grows.

• Move Left/Right: These are controls that allow you to rearrange the sequence in which transitions are evaluated and executed. Transitions are evaluated from left to right, so order them carefully.

• Condition: This criteria governs the task's progression based on the options defined below. Depending on the outcome of this task, this rule determines which path to follow next. Left to right, these are:

  • Success: if the task succeeds

  • Failure: if the task fails

  • Always: regardless of the outcome of the task

  • Custom Condition: set custom, with Jinja

Transition modes

Workflow input: Input variables

Workflow inputs are commonly known as input variables. The role of input variables is to provide data that can be used by tasks within the workflow, or into a subworkflow.

Input variables can be broken down into two parts:

1. A key

2. The specific data or values that vary

This is an example of a variable where [first_name] is the key and Ashley is the value:

[first_name] : "Ashley"

You can add new variables, or modify existing ones, by navigating to your Workflow > Configure Workflow Settings > Input Configuration.

Click + next to Input Configuration to see a number of new fields.

1. Name: This can be a unique entry relevant to what the aim of the input is going to be. This should not contain spaces.

2. Label: This text field is used to set a friendly name. It's the field name visible at the time of input.

3. Type: Short for data type, this field defines what format the data will be in. The most common types are Text (general string), Integer (whole number), and String (a combo of characters).

4. Default Value: You can specify a value that will be used if no other input is specified manually.

5. Description: You can give a better description of what the field is used for.

Input variables get their values in a Rewst workflow through the workflow's initial trigger event. Any data type that is valid in JSON can be used as an input variable.

Workflow action inputs

In the example below, creating a user in Microsoft 365 using three variables:

1. First Name

2. Last Name

3. Domain

For now, these are all specified directly on the workflow rather than being submitted via a form.

Create an action by dragging it from the integration list on the left menu.

Click on this action to reveal a number of input fields on the right-hand side.

In the image below, see how to use the variables by using CTX, which stands for context, and then the name of the variable. This will autocomplete to make it easier to reference.

Despite the data being static at this point, the process is the same regardless of where the data is coming from.

Workflow output

Similarly to the above, you can configure an output of a workflow. These are generally used in two situations:

1. The other time this would be used is if you have a sub-workflow. A sub-workflow is no different from a standard workflow, except for the fact it lives within another workflow. If you were passing data back from the sub-workflow into the main workflow, this would be done via an output variable.

Workflow action outputs

One of Rewst's ultimate purposes is to integrate various platforms into a workflow and use data from each to do something else.

In this example, you'll get a list of users where the userPrincipalName matches X, then create a ticket using information from that request.

If you ran this action as-is, you would get the list of users, but wouldn't be able to use that data anywhere.

A data alias allows you to create a variable, similar to an input variable, but with data direct from an action API request. In our example below, we are creating a variable with the key called user_details and populating it with the data of the user using Jinja.

Take your create_ticket action from your respective PSA from the actions menu of the workflow builder. In this example, we'll use Datto PSA.

Using your newly created data alias, add the inputs onto that create_ticket input.

This would create a ticket with the title User Exists RewstDocs@rewst.io.

These operations can be found inside each task's Advanced tab.

Integration overrides

Transition modes

Transition modes in Rewst are responsible for determining how transitions attached to a workflow action are followed. There are two primary modes:

• Follow All: This is the default mode. If your task has multiple conditions attached, the Follow All mode attempts to follow all of the specified transitions. In the workflow visualization, this mode is represented by the standard color blue.

• Follow First: In this mode, conditions are evaluated from left to right and as soon as the first condition is satisfied, the remaining conditions are disregarded. To differentiate these transitions in the workflow visualization, they are color-coded orange.

Task transition criteria sensitivity

Run as org

The Run as Org option allows the workflow action to run in the context of another organization.

The purpose of Run as Org is to temporarily pass the execution of a workflow task into the context of another organization. This is something you may see done when you have a task— be it an individual action or a subworkflow— that needs to be executed as if it were for a different org than the one the workflow is running for.

For example, if you wanted to have something run once for the parent organization that needed to also reference items for a child organization, a Run as Org option would solve this issue. Start by listing all organizations. Then, using Run as Org on a subworkflow, do things within that subworkflow for one or many of your managed organizations.

Or, when a form has an organization picker on it, where the organization ID is passed into the workflow from the form, Run as Org is used to have the actions in the workflow run as if they were for the selected organization, instead of the organization for which the form was loaded.

With items

With Items is the equivalent to a foreachstatement in other languages.

With this, you can pass a number of objects into a certain action and collect the results from each and then do something.

In the example below, you're going to list every user that is enabled in the child organization, and create or update a contact for each one.

List all enabled users, then output this to a data alias called

The data alias has the following Jinja:

You then have a subworkflow that creates or updates a contact. As per the best practice, use a subworkflow with your With Items.

In the Advanced tab, set the With Items field with this data alias.

The action now has the additional icon indicating that it has a With Items set on it.

During testing, or for example if creating tickets from an alert, you may sometimes want to limit the amount of alerts you get during this phase. Test the workflow on a subset of your total users initially to make sure it works as expected.

To achieve this, you could create an input variable on the workflow called max_tickets_to_create_per_actionand set it to the maximum number of times you want that With Items to run.

If set to 1, it will only run on a single object within CTX.all_users.

The below code is what you would use in the With Items field in the Advanced tab.

Use inputs after creating With Items

Iterating through CTX.all_users on the action means you can't use {{ CTX.all_users.X }} as the property for the input.

Instead, you must use {{ item() }}

Say you want to get the first name of each user as an input. On your With Items action you would execute:

Items concurrency

If you're running a workflow task using With Items, this allows you to set how many of these processes run at the same time. It's recommended that no more than 10 concurrent actions be performed at a time to guarantee performance.

Task timeout

This allows you to adjust the number of seconds to wait for a task to complete. The default value is 10 minutes.

When automating certain processes, it's important to use dynamic options that adjust based on the input. Using the same list of options every time can lead to errors by applying choices that don't fit the situation. When an automation gets information from a form, it's important that the data on the form be dynamic, and adjust based on previous inputs or selections on that same form.

An option generator workflow will always be connected to a form, and allows you to provide tailored, dynamic options for specific fields in that form. For example, in an automation that updates a user's group memberships, the list of groups is tailored to the input. You wouldn't want to add an individual to a group that they're already a member of, nor would you want to remove them from a group that they're not a member of. To add a user to a group, you would generate a list of groups that are not already part of the user's group memberships. To remove a user from a group, you would generate the user's current list of group memberships.

Create an option generator workflow

Before you begin, decide which options need to be displayed based on the user’s selection. For this example, the list of groups will change depending on whether the action is to add or remove a user.

3. Click the Workflow Type drop-down selector.

4. Select Option Generator.
6. Click Submit. This will launch the workflow builder.

Create a form to be used with the workflow

Remember, workflow generated options allow forms to be highly dynamic. When a form field is connected to an option workflow, it will return a list of options based on the input.

How the form and workflow come together to generate options

1. When the workflow runs, it should result in a context variable {{ CTX.options }} that contains a list of items with key-value pairs that will be referenced in the form editor.
2. The values here will be used in the Label Field an Value Field for a form field.

   1. The Label is what gets shown to the user who fills out the form as an available choice.

   2. The Value field will be set to the value of the Field Name when that form is submitted. Workflows will reference this as {{ CTX.<field_name> }}

   3. Using the Default Selected Field will evaluate an attribute of the options list for truthiness. Items which evaluate true will be selected by default when this field populates.

Completion handlers

Example workflow use cases for completion handlers

Let's look at a few use cases for using completion handlers:

• Taking additional steps after the onboarding workflow is complete

  • Add additional functionality to an existing synced workflow without having to unsync it from the template.

• Alerting for failed workflow executions, like kicking off the listener based on a failed status

Configure a completion handler in a workflow

1. Navigate to Automations > Workflows.

3. Note the two options in the Completion Handlers section. You'll need to choose which one you want to use:

   1. Run this workflow when...

      1. This will run the workflow when another workflow completes

   2. When this workflow completes...

      1. This will result in something being done when the workflow completes

4. Define your trigger conditions. This step will differ depending on which of the two options you chose in step 3.

   1. For When this workflow completes...

      2. Under Trigger On Statuses, specify the conditions for the trigger, such as succeeded, failed, timed out, or canceled. You can select multiple statuses from the drop-down list.

   2. For Run this workflow when...

      2. Under Trigger On Statuses, specify the conditions for the trigger, such as succeeded, failed, timed out, or canceled. You can select multiple statuses from the drop-down list.

      3. Select your relevant integration or integrations from the drop-down selector.

      4. Open each selected integration's accordion menu to choose your Configuration Selection Mode for that integration.

5. Make sure Enabled is toggled to on.

6. Click Submit to save your settings.

Access the context of the previous workflow

Contexts from the previously run workflow can be accessed with the COMPLETED_WORKFLOW variable. You can access most info via the context including ORG and CTX such as:

1. {{ COMPLETED_WORKFLOW.ORG.VARIABLES.cw_manage_company_id }}

2. {{ COMPLETED_WORKFLOW.CTX.user.username }}

Test completion handlers

In the noop, set all of the variables that will be used in your completion handler in the On Success transition as data aliases.

It’s important that the names of the data aliases you create in the On Success transition of the noop match both:

• the names of the variables that will be used in your completion handler

• the names of the variables that will be used in the live parent workflow that your completion handler is triggered by

Add static values that represent a good test case for ensuring that your completion handler functions the way you expect.

Example

In the example below, we’ve created a workflow with a single noop. In the On Success transition, we’ve added several data aliases that represent user data that could be used to test a workflow listener, which could be used after a user is onboarded or offboarded.

Once you’ve created the noop and added the correct data, attach this workflow to your workflow completion handler as another parent workflow that will trigger the completion handler. This will enable testing.

Click Test to run the workflow. This will feed the variables that you’ve set with your completion handler and trigger it to run, allowing you to confirm if the variables are used as expected. If you need to run your test workflow for organizations other than your parent MSP organization, add a trigger to the workflow which will allow you to select which organization the test workflow runs for.

Alternatively, re-run from the workflow result page of the workflow that kicks off the completion handler. This would still run the workflow in total, but would be a simpler way to achieve it with fewer clicks.

Workflow wrappers

Example workflow use cases for workflow wrappers

Let's look at a few use cases for using workflow wrappers:

• Handle pre and post-onboarding tasks

• Run a Crated workflow against a group of items, in a way it was not originally designed to do

Available Rewst actions

Rewst actions provide you the tools to effectively manage and customize your environment. From setting up organizations and users to associating with multi-tenanted objects, these actions form the foundation of your interaction with the platform. This guide explores each of the available actions in detail, providing you a clear path to maximize the potential of your Rewst functionality.

Jinja2 templating offers powerful capabilities to shape and manipulate data to fit your needs. Sometimes, these actions are common enough to repeat regularly. Data transformation actions provide the ability to modify, combine, and reshape the data you are working with in your workflows. These actions are particularly useful when dealing with complex data structures, such as nested lists and objects. They empower you to transform data according to your needs without additional coding.

Core actions in Rewst are your gateway to the platform's vast array of intrinsic functionalities. These actions, usable right out of the box, offer features ranging from ad-hoc HTTP requests to document parsing.

Core actions are used in the same way as regular actions within workflows. They are selected from the list of available actions, configured based on their parameters, and then added to the workflow at the appropriate place.

{
  "name": "Rewsty",
  "valid": true,
  "message": "Successfully completed the task."
}

mock_result:
  name: {{ CTX.name }}
  valid: true
  message: Successfully completed the task.

{
  "data": {
    "name": "{{ CTX.name }}",
    "valid": true,
    "message": "Successfully completed the task."
  }
}

text: Testing Debug Action
template: Greeting Message

{
  "template": "# Hey there Rewsty",
  "text": "Testing Debug Action"
}

publish_result_as: news
request_method: GET
URL: https://news.ycombinator.com

html: {{ CTX.news }}
style: find_all
value: a

html: {
  cookies: {},
  data: "<html>...</html>",
  headers: {...},
  status_code: 200
},
query: {
  style: "find_all",
  value: "a"
}

[
  "<a href=\"https://news.ycombinator.com\"><img height=\"18\" src=\"y18.svg\" style=\"border:1px white solid; display:block\" width=\"18\"/></a>",
  "<a href=\"news\">Hacker News</a>",
  "<a href=\"newest\">new</a>",
  "<a href=\"front\">past</a>",
  "<a href=\"newcomments\">comments</a>",
  "<a href=\"ask\">ask</a>",
  "<a href=\"show\">show</a>",
  "<a href=\"jobs\">jobs</a>",
  "<a href=\"submit\">submit</a>",
  "<a href=\"login?goto=news\">login</a>"
]

html: {{ CTX.news }},
style: select
value: .titleline a[href^='https://']

[
  "<a href=\"https://arxiv.org/abs/2308.00676\" rel=\"noreferrer\">Electronic Structure of LK-99</a>",
  "<a href=\"https://www.science.org/content/blog-post/room-temperature-superconductor-new-developments\" rel=\"noreferrer\">A room-temperature superconductor? New developments</a>",
  "<a href=\"https://sophiehoulden.com/randomstuff/epitime/?revised\" rel=\"noreferrer\">Epicycle Clock</a>",
  "<a href=\"https://howardism.org/Technical/Emacs/new-window-manager.html\" rel=\"noreferrer\">Emacs is my new window manager</a>",
  "<a href=\"https://ploum.net/2023-08-01-splitting-the-web.html\" rel=\"noreferrer\">Splitting the Web</a>",
  "<a href=\"https://twitter.com/zebulgar/status/1686498517227814912\" rel=\"noreferrer\">Unconfirmed video showing potential LK-99 sample exhibiting the Meissner effect</a>",
  "<a href=\"https://magicloops.dev\" rel=\"noreferrer\">Show HN: Magic Loops – Combine LLMs and code to create simple automations</a>",
  "<a href=\"https://arxiv.org/abs/2307.08378\" rel=\"noreferrer\">eGPU: A 750 MHz Class Soft GPGPU for FPGA</a>"
]

url: http://books.toscrape.com/catalogue/category/books_1/index.html
request_method: GET
publish_result_as: get_books

{
  "cookies": {},
  "data": "<bookstore>...</bookstore>",
  "headers": {...},
  "status_code": 200
}

input:
  xml: {{CTX.books.data}}
  selector: find
  value: book

{
  "value": "<book category=\"cooking\"><title lang=\"en\">Everyday Italian</title><author>Giada De Laurentiis</author><year>2005</year><price>30.00</price></book>"
}

xml: {{CTX.books.data}}
selector: select
value: book[category='children']

{
  "value": "<book category=\"children\"><title lang=\"en\">Harry Potter</title><author>J K. Rowling</author><year>2005</year><price>29.99</price></book>"
}

What are Data aliases?

A data alias is a shortcut that extracts specific pieces of information from a JSON response and stores them in an easy-to-use variable. Instead of navigating the entire JSON structure every time, a data alias pulls out exactly what you need—like a user’s name or email—and makes it accessible throughout your workflow. Think of data aliases as custom labels you assign to specific data.

Recall that the context is where all data generated, captured, or used in a workflow is stored. Think of it as a shared memory for a specific workflow. Data aliases are stored in the context, making them available for reuse at any step in your workflow without re-fetching the data.

For example, imagine that you've set up your Microsoft Graph integration. You send a request via API call to get info about a user. The response comes back to you in JSON format, which can be lengthy and time consuming to search through. A data alias would let you get all of the information, or pinpoint specific information like the user's name or email address, and store it in a simpler variable in the context for use.

Together, variables, data aliases, and the context make your workflows in Rewst more efficient, organized, and adaptable. These tools help you reuse workflows, reduce manual work, and customize data handling to fit any automation need.

Data alias requirements

When adding a new data alias, you'll need the following:

• Key: The name you assign to specific data.

• Value: The actual data it corresponds to. The code editor button allows for the use of Jinja customization for intricate data or expressions.

Data alias context example

If you set an alias such as my_task_result -> {{ RESULT }}, later tasks can refer to this data using {{ CTX.my_task_result }}.

You can also use a data alias to extract specific information and manipulate data. Expanding on our example from above, take the input from the Microsoft Graph get user action and extract the user's name and user principal name for ease of use.

1. Drag the Get User action onto the workflow builder canvas.

2. Add your user into the User ID field.

3. Set your context variable name under Publish Result As. The workflow action results will be stored as the value.
5. Use the following Jinja to create a new dictionary object and set the displayName and userPrincipalName keys.

   Copy

   {{
   {
   "displayName": CTX.user_details.data.value.displayName,
   "userPrincipalName": CTX.user_details.data.value.userPrincipalName
   }
   }}

6. Run the workflow. Then, click View Results

7. Click Load Context.

8. Expand the context to see our data alias filtered_user_details now only showing the displayName and userPrincipalName .

Add a data alias to a workflow

Access data aliases in a workflow

1. Navigate to Automations > Workflows.

2. Search for your desired workflow.

3. Click > to the far right of that workflow to open its workflow builder canvas.

Rewst actions: These actions are for interacting with your Rewst environment. You can perform tasks such as creating organizations and users, associating with multi-tenanted objects, and setting organization variables.

Transform actions: These actions help you shape and modify your data for efficient workflow execution, replacing the need for complex Jinja statements.

Workflows actions: These actions allow you to call other workflows within your environment. They enable you to feed information from the parent workflow as inputs and return the results upon completion.

Known actions issues and errors

This collection of issues related to actions have been reported to Rewst by our customers. If you experience an issue with actions that is not in this list, contact us in your dedicated Discord support channel.

Use case

You would like to programmatically determine what the date was thirty days ago.

Overview

Add or Subtract from a DateTime

Parameters

Usage

Results output

Result from Example 1 (if run on 04/16/2025):

Use case

You are reviewing a list of users, and want to determine if all of the users are enabled. The previous list has been mapped using the map transform action to the attribute enabled , providing a list of boolean True/False values to check against.

Overview

This transform action will look at a list of boolean values and return true if all of the elements in the list are true.

Parameters

Usage

Results Output

This transform will output a boolean value.

Example output from Example 1:

Use case

You are reviewing a list of users and you need to determine if any of the users are enabled. The previous list has been mapped using the map transform action to the attribute enabled , providing a list of boolean True/False values to check against.

Overview

This transform action will look at a list of boolean values and return true if any of the elements are true.

Parameters

Usage

Results Output

This transform will output a boolean value.

Example output from Example 1:

Use case

You're dealing with nested data structures and need to extract results from tasks ran With Items into your original list. You want a unified, easy-to-manipulate list that includes all necessary data.

Overview

The Append With Items Results transform enables effective incorporation of "With Items" task results into your original list. It bridges the gap between the collected results and the original list, making your data manipulation tasks simpler and more efficient.

Parameters

Usage

The below scenario will attempt to illustrate how the Process With Items Results transform can be utilized to simplify With Items results collection.

Input lists

Assume we have a base list called base_list:

And we ran a With Items task against this list to collect additional data from these items that's stored in a new list called collected_list that includes result.result attributes like this

Action parameters:

We want to extract the result.result list from each item in the collected_list and append it to each corresponding item in the base_list as a new attribute named hobbies.

Jinja2 equivalent:

Results output

After processing, your results will look like this:

How does RoboRewsty work?

RoboRewsty integrates with the workflow builder canvas. It takes your workflows' JSON objects, and sends them to a private OpenAI Azure instance. The result is a quickly presented, well structured documentation breakdown of all selected tasks in your workflow.

Use RoboRewsty

Via workflow builder

1. Create a new note.

2. Drag your note to encompass all actions in the workflow that you wish to document. This can be a subset of the workflow, or the entire workflow.

6. View the notes generated in your Notes menu. Sections will include:

   1. What's Occurring: Task Overview: Each documentation response begins with a clear and concise overview, providing users with a high-level understanding of the task's purpose and context.

   2. Expected Outcome: Task's Expected Result: Information about the expected outcome or result of the task or group of tasks is presented. This section helps users anticipate the outcomes when the workflow executes the associated tasks.

   3. Special Considerations: Any Crucial Factors: Special considerations or crucial factors related to the tasks are included. These details ensure that users have all the necessary information to understand the workflow path successfully.

   4. An accordion list of all included tasks

Via publish workflow

RoboRewsty is also available to help when you publish a workflow. Click on the RoboRewst icon to generate a detailed change log, then Submit.

Use case

You need to compare two lists and highlight the unique entries or entries exclusive to the first list, A transformation action that simplifies this complex comparison process is required.

Overview

The Diff Lists transform is your solution for list comparison tasks. It uses two methods - Anti-Join and Symmetric Difference - to focus on unique or exclusive entries, thereby streamlining your data comparison process.

Parameters

Here are the parameters you have available to you within the action, and their descriptions:

Usage

Input lists

For this transform, we will want to feed the action two separate lists, that we will then identify the fields in which we want to identify differences. Let's use these two lists as example:

List 1:

list_1: [
  {"id": 1, "name": "John"},
  {"id": 2, "name": "Mary"}
]

List 2:

list_2: [
  {"id": 1, "age": 30},
  {"id": 3, "age": 35}
]

Difference methods

We have two options for the Difference Method you can pick to have the action perform, these method have slight differences that are quite helpful in various situations:

• Anti-join: for scenarios where you want to find entries that are exclusive to the first list.

• Symmetric difference: for comparing two sets of data and identifying unique records in each.

Take a look at examples of both below:

diff_method: anti_join
list_1: List 1
list1_key: id
list_2: List 2
list2_key: id

{% set result = [] %}
{% for item1 in list_1 %}
  {% if all(item1[list1_key] != item2[list2_key] for item2 in list_2) %}
    {% do result.append(item1) %}
  {% endif %}
{% endfor %}


{{ result }}

diff_method: symmetric_difference
list_1: {{ CTX.list_1 }}
list1_key: id
list_2: {{ CTX.list_2 }}
list2_key: id

{% set result = [] %}
{% for item1 in list_1 %}
  {% if all(item1[list1_key] != item2[list2_key] for item2 in list_2) %}
    {% do result.append(item1) %}
  {% endif %}
{% endfor %}
{% for item2 in list_2 %}
  {% if all(item2[list2_key] != item1[list1_key] for item1 in list_1) %}
    {% do result.append(item2) %}
  {% endif %}
{% endfor %}


{{ result }}

Results Output

The results of the two different diff methods can be seen as follows:

Anti join: only Mary's object from list_1 is returned in the output, as she didn't have a correlating id in list_2.

result: [
  {"id": 2, "name": "Mary"}
]

Symmetric difference: both Mary's object from list_1 and the object in list_2 that didn't have a correlating id in list_1 were returned in the returned list.

result: [
  {"id": 2, "name": "Mary"},
  {"id": 3, "age": 35}
]

With a grasp on the Diff Lists transform, you're ready to analyze and compare your lists for unique entries or entries exclusive to the first list. Understanding the differences between Anti-Join and Symmetric Difference methods will aid you in making effective data comparisons.

Convert DateTime to Timezone

Use case

You are working with an API that returns a time in UTC, you would like to localize this value to your timezone or a specific timezone.

Overview

Convert a DateTime to a different timezone.

Parameters

Usage

Results output

Result of Example:

"2025-04-16T05:00:30-04:00"

Use Case

You have a email with a URL in it similar to something like: https://rewst.io/aprilfools/surprise.html You would like to defang it and make it not directly usable.

Overview

Given a URL, this action will 'defang' the url by adding characters to prevent it from being directly usable.

Parameters

Usage

Results Output

The expected result of this transform is a defanged url.

Result from Example 1:

hXXps[:]//rewst[.]io/aprilfools/surprise.html

Overview

This transform action allows you to convert a list of objects into a single object, creating each object's property using user-defined key-value pairs extracted from the list, and simplifying the handling of complicated list structures.

Parameters

Usage

The Convert List to Object transform provides a powerful way to reshape your data to meet specific requirements. The ability to define keys and values, including the ability to access nested data, makes it versatile for a range of scenarios. Let's go through a couple of use-case examples to demonstrate how this transform can be applied to your data.

Results output

In both of these examples, your new output object would look as follows:

Use case

You would like to get the current date/datetime.

Overview

Returns the current date/time in the requested timezone.

Parameters

Usage

Results output

Results of Example:

Get Business Days Between Dates

Use case

You would like to get the count of business days between dates.

Overview

Get the number of business days between two dates.

Parameters

Usage

Results output

Result of Example 1:

Result of Example 2:

Boolean values and their role in automation

Boolean values represent simple yes/no conditions, like on/off or true/false. They define rules and logic in workflows by evaluating conditions.

Boolean values are fundamental in automation workflows, controlling decision-making and process flow. Understanding Boolean logic helps ensure that workflows are efficient, reliable, and easy to maintain.

Key boolean concepts

• Boolean values: Represent true or false, similar to 1 (on) and 0 (off).

• Logical operators: and, or, not determine conditions in workflows.

• Comparison operations: Evaluate conditions (e.g., user_role == "admin").

• Custom conditions in workflows: Enable transitions based on Boolean evaluations.

Boolean operators in Rewst workflows

Boolean logic controls workflow decisions using these key operators:

• and – Requires both conditions to be true.

  • Example: user_logged_in and is_admin

• or – Requires at least one condition to be true.

  • Example: is_manager or is_admin

• not – Inverts a Boolean value.

  • Example: not user_logged_in (returns true if user_logged_in is false).

Boolean logic in action

• True and false = false – Both conditions must be true for and to return true.

• True or false = true – Only one condition needs to be true for or to return true.

• Not false = true – Flips the Boolean value to its opposite.

Best practices for boolean logic in Rewst

To ensure efficiency and maintainability, follow these best practices.

Structuring logical conditions

• Group logic with parentheses: Ensures conditions execute in the correct order.

  • Example: (is_admin and is_active) or is_super_admin

• Use in for cleaner conditions:

  • Before: if role == "admin" or role == "super_admin"

  • After: if role in ["admin", "super_admin"]

Simplifying boolean expressions

• Use ternary operators for concise logic:

  • Syntax: variable = value_if_true if condition else value_if_false

  • Example: status = "Active" if is_active else "Inactive"

• Leverage short-circuit evaluation:

  • Skips unnecessary checks by placing the most likely condition first.

  • Example: if user_logged_in and is_admin: (Skips is_admin check if user_logged_in is false.)

Use case

You have a list of user's that has been returned from an API, you would like to determine the count of user's in the list.

Overview

Measures the length of a List. It will return the number of elements of that list.

Parameters

Usage

Results output

Result of Example:

5

Check If String is Valid JSON

Use case

You are working with an API and the return comes back as a JSON string instead of being a JSON object. You would like to verify that the string is valid JSON before attempting to convert it to JSON.

Overview

This transform will check whether or not a string provided via the 'String to Check' input is a valid JSON string.

Parameters

Usage

{"test":"test"}

I am not a JSON string!

Results Output

This transform will output a boolean value (True/False) based on whether or not the string is a valid JSON string.

Return from Example 1:

True

Return from Example 2:

False

Generate Friendly Password

Use case

You are resetting a user's password and would like to generate a friendly password.

Overview

This action generates an easy password with adjective, name, number, symbol and random caps.

Parameters

There are no parameters for this transform.

Usage

This transform has no parameters, so no usage examples can be given.

Results output

Example 1:

FAirBAnDIcooT39!

Example 2:

GREENBoNoBo73=

Example 3:

KINDSNakE41$

Use case

You would like to get the count of days between dates.

Overview