The Rewst Dashboard is the home screen you'll see when you first log into the platform. Click the drop-down organization selector in the top right to choose which org's information will be displayed in the dashboard at any given time.

Use the dashboard to easily digest key metrics for every workflow executed within a selected timeframe and better understand how Rewst is bringing you value. Identify usage patterns, success rates, and estimated time savings.

Choose to view the data in your desired timespan by clicking the relevant button at the top right of the dashboard for either Weekly or Monthly views. Note that the default for the dashboard timeline is monthly. Click < or > next to the indicated date to skip between date ranges. Click Download CSV to export the report to a file.

The Tasks Performed chart shows all tasks performed in the prior month or week for your selected organization.

The Time Saved chart shows the total time saved by using your Rewst automations in the prior month or week for your selected organization.

The Workflows menu shows stats for how many workflows in your selected time period were running, as well as how many executions were successful and how many errors were given. The time period selected at the top of your dashboard will determine the time period displayed in the widget.

Scroll further down the Rewst Dashboard page to see the Workflows widget. The data in this section updates daily.

This section of the dashboard provides a centralized view of individual workflow usage metrics in separate columns: Success Rate, Total Executions, Total Tasks, and Time Saved. Click on any individual workflow in the widget's workflow list to open that workflow in the workflow builder canvas. Use the fields at the top of each column to enter search and filtering parameters to find your desired workflows. Click Download CSV to export the workflow data to a file.

Get started with Rewst

Not sure where to begin? We recommend these resources. Click on Cluck University links to launch that course in a new tab. Click on documentation links to take you directly to that page in this documentation site.

Cluck University intro courses

Documentation on Rewst platform basics

Use case

You received a list of users from an API that contains the user's ages.

You have mapped to the age attribute of the user dictionaries and would like to calculate the average of the new list of integers to get the average age of the users.

Overview

Returns the average, or arithmetic mean, of a list of numbers.

Parameters

Usage

Results output

Result of example:

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:

Example 2:

Example 3:

Use case

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

Overview

What is a form?

In Rewst, every automation starts with a single click. Forms are powerful tools used to collect the information your workflows need to start. They streamline the data collection process by gathering key details from users such as names, dates, or options. Forms can be manually created, or added as part of .

Rewst's form functionality is designed to empower users with the tools to build interactive, responsive, and customizable forms.

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

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.

Embed forms

There is often a need to embed a form in an iframe to give users the ability to complete a form and trigger automation. The form can be embedded into other web pages that use iFrame links.

Use Case

You have received a date in a response from an API, you are going to use this to dynamically specify the year in another request based on what was received in the response.

Overview

Use case

You would like to set a variable for use later in the workflow

Overview

If a form field of a form unpacked from a Crate isn't populating with information, you have two options.

1. Identify the issue by digging into the form.

2. Open a support ticket with Rewst's support team and have them troubleshoot the issue for you.

Either option will require you to collect information from the form by completing the following steps. As an example, we're using the [Rewst Master v3] User Onboarding Minimalistic form.

1. Navigate to Automations > Forms.

2. Open the form in question.

3. Scroll down in the right side menu. Click on any field that's further down in the field list.

4. Click on the field. This will open its information in the right side menu.

1. Scroll down to see if the field is a dynamic field. If it is, Dynamic Options will be toggled on.

2. Confirm if the field has Workflow Generated toggled on. If so, look at the options generator in the Workflow field beneath it.

3. Open the options generator by clicking .

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. Click in the top toolbar of the workflow builder to start a note for the entire workflow. To add notes on specific elements, drag around an area on the canvas while holding down ctrl + left click , or right click and select Add Note within the workflow builder.

2. Click Generate Auto-Documentation to generate documentation for the entire workflow.

3. A waiting message will display while it runs on your workflow. This may take a moment, if your request holds a large number of 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 have received a time value in epoch time from an API and would like to convert it to a date time string representation.

Overview

Given an integer for epoch time, convert it to a date time string.

Parameters

Usage

Results output

For this example the now( ) method is feeding in a value of 1747395397.

Use case

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

Overview

Get the number of days between two dates.

Parameters

Usage

Results output

Result of Example:

Use case

You are building a workflow that checks if the tickets closed date is greater than the expected close date and would like to know if action is needed based on a true/false value.

Overview

This transform will take two dates and an operator, it will then perform a comparison based on the operator and return a boolean value.

Parameters

Usage

Results output

The expected output for this transform is a boolean value based on the comparison of the two dates.

Result Output for Example 1:

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:

You'll often have forms that you want to use across a multitude of clients, but sometimes fields may not be relevant to them all. Rewst has conditional fields that can be used to determine whether you show another field.

Conditional field example

In our example, we will look at the Supervisor field when creating a new user. In the image below, no Supervisor is set, and therefore the following field is another drop-down for further information.

You can then see that if we add content to that supervisor drop-down, which is a list of users pulled dynamically from Microsoft365, a new field appears.

This boolean field is then checked on, which gives access to another relevant field.

Rather than giving fields to a user that bear no relevance, you only give them fields they must fill in.

These conditional fields are set by clicking the field on the form and clicking Set Conditional Field, which presents you with the below.

Jinja for field conditions in forms

There are times where you may need to use criteria for a form condition that is not accounted for by the available drop-down selections, such as when organization information or organization variables are part of the criteria. At these times, you might instead opt to use a Jinja condition, such as {{ ORG.VARIABLES.variable_name == "value" }}.

Another case where the use of Jinja may be required is when multiple conditions need to be met, even if those conditions are normally available in the drop-down selections. An example of this would be {{ (CTX.field_name_1 == "value_1") and (CTX.last_name != "value_2") }} .

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:

Use case

There is a character limit on a field in an upcoming API call, you would like to check the length of the input prior to making the call.

Overview

Measures the length of a String. It will return the number of characters in that string.

Parameters

Usage

Results output

Result of Example:

Available workflows actions

The Workflows actions accordion menu contains any existing workflows in the workflow list for the related child organization. This actions menu is what powers Rewst's subworkflow functionality, by letting you reuse existing workflows as individual tasks in a more broadly scoped integration.

The available actions in this submenu will be different for each of your child organizations. Each time you create a new workflow, the list will grow.

Unpacking a Crate will also add the workflows in that Crate to the Workflows actions accordion menu. You'll gain many of the common automations our team has pre-built workflows for, and can use them to build your own custom workflows.

Note that most workflows actions will use . If present, these will appear in the Parameters tab of the task.

This workflow queries Duo Security to retrieve a comprehensive count of users across all client accounts, serving as a critical building block for MSPs to automate billing, license management, and security compliance reporting. It's particularly valuable for MSPs who bill per user, need to verify MFA deployment completeness, or must generate regular security compliance documentation for clients requiring multi-factor authentication. Technically, the workflow functions by first listing all Duo accounts, then retrieving all users from the Duo platform, and finally merging this data to generate accurate user counts that can feed into reporting systems, PSA tools, or client-facing dashboards.

This workflow contains 7 tasks.

Inputs

This sub workflow has no inputs.

Outputs

• automation_log: Standardized Rewst automation log

• duo_user_count: List of DUO companies and their counts.

Key tasks

• build automation log: Logging

• get_user_count: Data retrieval

• duo_list_accounts: Duo integration: List Accounts

• duo_list_users: Duo integration: List Users

Jinja examples

Example 1

Used in setting the duo_accounts alias.

Use case

You have a string that you would like to split each word/character by a delimiter to create a list.

Overview

Splits text on a delimiter into a list of strings.

Parameters

Usage

Results output

Result of Example:

Use case

An API has returned a value that is base64 encoded and you would like to decode it.

Overview

Decode a base64 encoded string.

Parameters

Usage

Results output

Result of Example 1:

This workflow serves as a foundational building block that retrieves Microsoft 365 user license information and makes it available for consumption by larger automation processes, functioning as a standardized entry point to license data. MSPs can leverage this component for critical scenarios including license auditing, user onboarding/offboarding processes, license optimization to prevent over-provisioning, and generating automated client billing reports. Technically, the workflow executes by calling the "[PROD TASK] M365: Get User Licenses" task to fetch license data from Microsoft 365 tenants, presenting structured license information that other workflows can consume for decision-making and automation tasks.

This workflow contains 4 tasks.

Inputs

• company_id - string; This would be a Microsoft Entra tenant ID.

Outputs

• automation_log: Standardized Rewst automation log

• license_counts: List of Rewst orgs and their license counts in Office 365.

Key tasks

• BEGIN: Core integration: noop

• workflows_365_get_users: Data retrieval

• Create Automation Log: Creation/initialisation

Jinja examples

Example 1

Example for input parameter 'company_id'

Example 2

Used in publishing 'license_counts'

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 have a string that is URL encoded and you would like to get the original decoded value.

Overview

When given a URL encoded string, this will decode it.

Parameters

Usage

Results output

Results of Example 1:

This workflow serves as a foundational building block that retrieves and quantifies all network devices tracked in Auvik across your client base, providing essential inventory metrics that can be leveraged in reporting, billing automation, or compliance verification processes. For MSPs, this function delivers critical visibility when performing quarterly business reviews, validating managed device counts against service agreements, or identifying growth opportunities within existing clients' networks. Technically, the workflow first retrieves all tenant details from Auvik, then calls a device listing task for each tenant, and finally merges these device counts with company information to produce comprehensive device statistics by client - all accessible via API for integration with your PSA, documentation system, or custom reporting tools.

This workflow contains 7 tasks.

Inputs

This sub workflow has no inputs.

Outputs

• automation_log: Standardized Rewst automation log

• auvik_user_count: List of auvik companies and their counts.

Key tasks

• workflows_dev_task_auvik_list_devices: Workflows integration: [DEV TASK] Auvik: List Devices

• BEGIN: Core integration: noop

• build automation log: Logging

• merge_counts_with_company: Core integration: noop

Jinja examples

Example 1

Used in input parameter 'id'

This workflow automatically retrieves and compiles device counts across all client sites in Datto RMM, serving as a foundational data-gathering component that can feed into billing automation, asset reporting, or resource allocation workflows. It's particularly valuable for MSPs who need accurate device counts for usage-based billing, license management, or regular client reporting without manual inventory checks. Technically, the workflow calls the Datto RMM API to list all sites, then leverages a specialized task to gather device counts across these sites, making this data available for consumption by other automation processes in your MSP operations.

This workflow contains 5 tasks.

Inputs

This sub workflow has no inputs.

Outputs

• automation_log: Standardized Rewst automation log

• rmm_user_count: List of Datto RMM companies and their counts.

Key tasks

• Get_Datto_RMM_Device_Counts: Data retrieval

• datto_rmm_list_sites: Datto RMM integration: List Sites

• build automation log: Logging

• BEGIN: Core integration: noop

Jinja examples

Example 1

Used in input parameter 'site'

This workflow serves as a foundational building block that queries and retrieves organization count data from Proofpoint's email security platform, enabling MSPs to programmatically access client protection metrics for use in larger automation processes like reporting or security audits. It's particularly valuable for MSPs managing multiple clients' email security postures, supporting scenarios such as automated security reporting, license management verification, and identifying gaps in protection across client environments. Technically, the workflow operates by connecting to the Proofpoint API, retrieving organization data using the "proofpoint.get_organization" action which lists all sub-organizations for a specified domain, then processes this data to extract relevant count information while incorporating error handling for reliability. This automation component eliminates manual data collection steps for technical staff and can feed directly into client-facing security reports, RMM dashboards, or PSA ticketing systems to maintain consistent email security monitoring across the MSP's client base.

This workflow contains 7 tasks.

Inputs

This sub workflow has no inputs.

Outputs

• automation_log: Standardized Rewst automation log

• proofpoint_user_count: List of ProofPoint companies and their counts.

Key tasks

• handle failure actions: Core integration: noop

• Get Proofpoint Counts: Data retrieval

• build automation log: Logging

• proof_point_list_organizations: ProofPoint integration: List Organizations

Jinja examples

Example 1

This Jinja expression creates a formatted list of dictionaries containing Proofpoint license information for each managed organization. It accesses the proofpoint_orgs data from the context (CTX) object and extracts key metrics like organization name, active user count, license count, and primary domain for reporting or further processing.

Use case

You have a string that has been grabbed from an API return, however due to bad formatting the string starts or ends with extra spaces that need removed.

Overview

Trim whitespace characters from a variable.

Parameters

Usage

Results output

Result of Example:

In the above return the " characters were kept to show the spaces being removed. These would not be present in the actual return. Only the original string without whitespaces would be returned.

This workflow functions as a reusable building block that creates tickets in Datto Autotask PSA with proper contact association, enabling MSPs to programmatically generate standardized tickets across various automation scenarios. It's particularly valuable for integrating monitoring alerts with ticket creation, automating customer request handling, standardizing ticket generation across technicians, and incorporating ticket creation into complex workflows like onboarding/offboarding processes. Technically, the workflow first validates contact information by searching Datto PSA's contact database, then creates a properly formatted ticket with all required fields and associations, making it a reliable foundation for any automation that requires ticket generation within your PSA.

This workflow contains 8 tasks.

Inputs

• board - string

• summary - string

• company_id - string

• contact_id - string

• category_one - string

• category_two - string

• category_four - string

• child_company - string

• contact_email - string

• category_three - string

• ticket_item_id - string

• ticket_type_id - string

• ticket_priority - string

• ticket_subtype_id - string

• initial_description - string

• default_status_override - string

Outputs

• automation_log: Standardized Rewst automation log

• success: Boolean; States if workflow was successful.

• ticket_id: Returns the ticket ID of the created ticket.

• ticket_data: Return the ticket object of the created ticket.

Key tasks

• BEGIN: Core integration: noop

• create_ticket: Creation/initialisation

• format_output: Core integration: noop

• failed: Core integration: noop

Jinja examples

Example 1

Task: set_variables | Context: Used in publishing 'company_id'

Example 2

Task: set_variables | Context: Used in publishing 'issue_type_id'

This workflow acts as a powerful building block that queries the Pax8 platform to retrieve comprehensive license counts across all client companies, providing essential data for license management, billing verification, and reporting workflows. By connecting to Pax8's API to list companies, gather product information, and enumerate active subscriptions, the workflow delivers accurate license quantity data that MSPs can leverage to identify unused licenses, verify billing accuracy, or trigger procurement processes. MSPs can integrate this into larger automation sequences that generate client-facing license reports, reconcile billing data between Pax8 and their PSA, or build automatic notifications when licenses need attention. The technical implementation is straightforward yet powerful - listing managed companies in Pax8, retrieving product details, and collecting subscription information to create a complete picture of license utilization across the entire client base.

This workflow contains 7 tasks.

Inputs

This sub workflow has no inputs.

Outputs

• automation_log: Standardized Rewst automation log

• subscription_name_and_quantity: List of Pax8 companies and their counts.

Key tasks

• BEGIN: Core integration: noop

• handle failure actions: Core integration: noop

• pax_8_get_product: Data retrieval

• pax_8_list_companies: Pax8 integration: List Companies

Jinja examples

Example 1

Used in publishing 'subscription_name_and_quantity'

This workflow serves as a fundamental building block that queries ConnectWise Automate to retrieve company and computer counts, providing essential inventory data that can be consumed by larger automation processes for reporting, billing, or compliance purposes. MSPs will find this function valuable for client onboarding/offboarding validation, license reconciliation, automated billing workflows, and generating executive dashboards showing managed device statistics across their client base. Technically, the workflow executes by first retrieving the complete list of companies from CWA, then obtaining all managed computers, calculating the relevant counts, and presenting the data in a standardized format that other workflows can easily reference when making automation decisions or populating reports.

This workflow contains 7 tasks.

Inputs

This sub workflow has no inputs.

Outputs

cwa_counts: This output will contain a list of companies from Automate along with their counts.

Key tasks

• connect_wise_automate_list_companies: ConnectWise Automate integration: List Companies

• connect_wise_automate_list_computers: Calculation

• build automation log: Logging

• calculate_final_count: Calculation

Jinja examples

Example 1

Task: connect_wise_automate_list_companies

This expression creates a formatted list of company data by iterating through all companies available in the ConnectWise Automate integration. It extracts each company's name and ID, transforming them into a structured JSON array that can be easily consumed by other workflow steps or displayed in a dashboard.

The expression accesses the CTX.companies object provided by Rewst's ConnectWise Automate integration, which contains all the company records with their properties like Name and Id. MSPs can modify this to include additional company properties by adding more key-value pairs to the dictionary such as \"location\": company.Location or \"contact\": company.PrimaryContact.

There may be times when you want to take an existing form and make slight modifications to apply it to another use case. For example, you may be using the Client: New Employee workflow to onboard new users, and want to have two different forms:

1. One for when you hire internal users at your organization

2. One for adding users for your customers

How to clone and edit a form

1. Navigate to Automations > Forms.

2. Click ⋮ and select the Clone option on the form you want to clone.

3. Rename your form to something unique and define a few other fields:

Shallow clone a form

Shallow cloning is a feature of the Rewst platform that allows you to create a copy of an existing workflow or form. This is useful if you have a workflow that is very similar to another workflow, but which requires a few small changes.

Standard cloning copies the entire resource pack— workflow, forms, templates, triggers, etc— and when cloning into your own org, you end up with multiple duplicates of the same resource. Shallow cloning copies that single selected resource, but re-uses all of the dependencies that it has. If you have a sub-workflow that's part of a main workflow, and you shallow clone that sub-workflow, you will end up with a copy of the sub-workflow. This lets you make changes to the sub-workflow without affecting the original workflow.

There is no difference between the steps to clone or shallow clone a resource. Rewst will automatically detect if you are cloning something into your own org. If so, the platform will shallow clone it instead. Note that this removes the Synchronize button on the dialog, and instead shows a text to explain.

Use case

You have received an API response of a JSON string instead of a JSON object and would like to convert it to a JSON object.

Overview

Parse Text Data into JSON.

Parameters

Usage

Results output

Result of Example:

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

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:

Return from Example 2:

Use Case

You have a string value of a CSV file and you are looking to send it as an attachment using the Send Mail As Impersonated User action via the Microsoft Graph integration which requires the CSV string to be base64 encoded.

Overview

Encode a string in base64.

Parameters

Usage

Results output

Result of Example 1:

Use case

You have a list of users and you would like to grab the first user in the list.

Overview

Returns the Nth element of a string or list

Parameters

Usage

Results output

Result of example 1:

This workflow provides a reliable method for sending emails with attachments through Rewst, functioning as a critical communication component that can be called from other automations to deliver documents, reports, or files to clients or team members. MSPs can leverage this building block to automate client communications for service completion notifications, scheduled security reports, license renewals, or documentation delivery—all with proper attachments and consistent branding. Technically, the workflow accepts inputs including recipient addresses, subject, body content, and attachment details, then determines whether to send via standard email or through Microsoft Graph (allowing for user impersonation), with built-in error handling for failed deliveries or missing user accounts. This reusable component eliminates the need to rebuild email functionality in every workflow, allowing MSPs to standardize client communications while focusing on building more complex automation processes.

This workflow contains 13 tasks.

Inputs

• send_to - array (Required)

  • Default: {{ [ ] }}

• subject - string

• send_as_guid - string (Required)

• use_failover - boolean

  • Default: {{ true }}

• attachment_name - string

• attachment_type - string

• encoded_contents - string

• message_contents - string

• no_failover_attachment - boolean

  • Default: {{ false }}

Outputs

• automation_log: Standardized Rewst automation log

• output: Outputs a dictionary object with a key for success, the value for success is a boolean value indicating whether the workflow was successful or not.

Key tasks

• check_sendas_field: Communication/notification

• Send_Email: Communication/notification

• core_sendmail: Communication/notification

• microsoft_graph_get_user: Data retrieval

Jinja examples

Example 1

Used in input parameter 'subject'

This workflow queries the Huntress security platform to retrieve and compile license usage data across all client organizations, serving as a critical building block for license management, billing reconciliation, and capacity planning automations. For MSPs, this function provides essential visibility for client billing accuracy, license compliance tracking, and identifying opportunities to optimize security coverage across the client base. Technically, the workflow first authenticates with Huntress, then retrieves the complete list of managed organizations, calculates agent deployment counts per organization, and compiles this data for integration with other systems like PSAs for billing or reporting tools for client reviews. This data can be particularly valuable when integrated with onboarding/offboarding workflows or when preparing for quarterly business reviews to assess security tool adoption and coverage gaps.

This workflow contains 6 tasks.

Inputs

Outputs

• automation_log: Standardized Rewst automation log

• huntress_count: List of Huntress companies and their counts.

Key tasks

• huntress_list_organizations: Huntress integration: List Organizations

• get_huntress_agent_count: Data retrieval

• build automation log: Logging

• BEGIN: Core integration: noop

Jinja examples

Example 1

This expression creates a structured list of all client organizations with their Huntress agent deployment statistics. It iterates through each organization in your Huntress integration (CTX.huntress_orgs), extracting the company name, agent count, and company ID into a list of dictionaries, with the |d filter providing empty string defaults for any missing values.

This workflow functions as a data-gathering utility that connects to NinjaRMM, retrieves all managed organizations, and calculates the total count of workstations and servers for each client. As a building block, it provides standardized device inventory data that can be consumed by other workflows for billing automation, client reporting, compliance verification, and device management processes. The workflow executes in three main technical steps: first retrieving the organization list from NinjaRMM, then making separate API calls to collect workstation and server device lists, and finally calculating the per-organization device counts for consumption by other systems. MSPs will find this particularly valuable for usage-based billing automation, reconciling device counts against agreements, generating executive reports for clients, and tracking environment growth trends across their client base.

This workflow contains 8 tasks.

Inputs

This sub workflow has no inputs.

Outputs

• automation_log: Standardized Rewst automation log

• ninja_device_counts: List of Ninja RMM companies and their counts.

Key tasks

• BEGIN: Core integration: noop

• ninja_rmm_list_organizations: NinjaRMM integration: List Organizations

• list_workstations: NinjaRMM integration: List Devices

• list_servers: NinjaRMM integration: List Devices

Jinja examples

Example 1

This expression creates a detailed inventory report by iterating through all organizations in NinjaRMM and counting their workstations, servers, and network devices. It accesses NinjaRMM data stored in the CTX variable (context), filtering devices by organization ID to generate accurate device counts for each client.

This workflow retrieves queue information from Datto PSA, serving as a critical building block for more complex ticket routing and management automations. MSPs can leverage this function when implementing automated ticket assignment processes, workload balancing between teams, or creating custom reporting dashboards that provide visibility into queue status and performance. Technically, the workflow executes a simple API call to Datto PSA's resource role queues endpoint, retrieving the field definitions and structure of available queues, which other workflows can then consume to make intelligent routing decisions or gather queue metrics for service delivery improvements.

This workflow contains 1 task.

Inputs

• choose_variable - string

Outputs

• options: Array of queues.

Key tasks

• datto_psa_resource_role_queues_query_field_definitions: Datto Autotask PSA integration: resource_role_queues_query_field_definitions

Jinja Example

This is used to populate the queues data alias.

This workflow serves as a fundamental data retrieval building block that pulls a complete list of technicians/agents from Halo PSA, providing essential personnel data that can be utilized in more complex automation sequences. MSPs would find this function valuable when building ticket assignment workflows, creating technician availability reports, implementing skill-based routing, or developing any automation that requires filtering or assigning work based on agent attributes. Technically, the workflow executes a straightforward API call to Halo PSA that retrieves all agent records, returning them as a structured array that other workflows can filter, iterate through, or use for decision-making processes without requiring administrators to manually extract this information each time it's needed.

This workflow contains 1 task.

Inputs

• choose_variable - string

Outputs

• options: Array of agent objects.

Key tasks

• list_agents: HaloPSA integration: List Agents

Jinja examples

Example 1

This workflow retrieves all available ticket subtypes from Datto Autotask PSA, serving as a critical reference component for any automation that needs to create, route, or categorize tickets programmatically. MSPs will find this building block invaluable when developing automated ticket creation from RMM alerts, implementing intelligent ticket routing based on issue type, or synchronizing ticket classifications between different platforms. Technically, it executes a simple query to the Datto PSA API that returns all defined ticket subtypes and their associated picklist values, making these values available as variables for other workflows. This standardized method for accessing ticket classification data ensures that downstream automations always use valid subtype values, preventing errors when integrating with the PSA.

This workflow contains 1 task.

Inputs

• ticket_type - string

• choose_variable - string

Outputs

• options: Array of ticket subtype objects.

Key tasks

• list_ticket_subtypes: Datto Autotask PSA integration: List Ticket Fields with Picklists

Jinja example

This is used in publishing the ticket_subtypes data alias.

This workflow automatically pulls organization and user data from IT Glue, matches users to their respective organizations, and calculates license utilization across client sites - serving as a foundational building block for license management, billing verification, and capacity planning automations. MSPs will find this particularly valuable for reconciling monthly MyGlue license billing, identifying underutilized licenses for reassignment, preparing client reviews with accurate license metrics, and ensuring compliance with license agreements. Technically, the workflow functions by retrieving a comprehensive list of organizations and users from IT Glue's API, processing this data to match users with their organizations, calculating per-site license counts, and then producing a structured output that can feed into reporting tools, PSA systems, or other automated processes.

This workflow contains 8 tasks.

Inputs

This sub workflow has no inputs.

Outputs

• automation_log: Standardized Rewst automation log

• glue_counts: List of ITGlue companies and their counts.

Key tasks

• it_glue_list_organizations: IT Glue integration: List Organizations

• it_glue_list_users: IT Glue integration: List Users

• BEGIN: Core integration: noop

• calculate_site_counts: Calculation

Jinja examples

Example 1

Creates a list of organizations that have the attribute my-glue-account-id populated.

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

Use case

You are trying to create a list of users from a Microsoft Graph return and want to create a flat list of all the display names for the users.

Overview

Use case

You are working with a list of users however, the dataset contains multiple objects with the same GUID, you would like to remove the duplicates from the list.

Overview

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.

Use case

You have an email with a defanged URL inside of it similar to something like: hXXps[:]//rewst[.]io/aprilfools/surprise.html

You would like to refang it and make the URL directly usable.

Overview

Use case

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

Overview

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

This workflow retrieves the total count of devices managed in ImmyBot, serving as a critical data-gathering building block that can feed into larger workflows for billing, license management, or resource planning automations. It's particularly valuable for MSPs needing to automate client billing based on device count, reconcile asset inventory across platforms, or trigger conditional processes based on current managed device thresholds. Technically, the workflow executes an API call to ImmyBot using the "list_computers" action, processes the returned device data, and makes the count available for downstream automation consumption - creating a simple yet powerful integration point between ImmyBot and your broader automation ecosystem.

This workflow contains 6 tasks.

Inputs

This sub workflow has no inputs.

Use case

You are writing query parameters and the API you are sending them to requires them to be URL encoded.

Overview

When given a string this transform will URL encode it.

Use case

You have received a date time string representation from an API, you would like to utilize this value in another API, however the new API expects it to be in a certain date format.

Overview

This workflow retrieves the standardized list of ticket priorities from Datto Autotask PSA, serving as a fundamental building block that other automations can leverage when creating, updating, or processing tickets. MSPs will find this function valuable when building ticket creation workflows with conditional priority assignment, implementing SLA-based escalation processes, or ensuring consistent priority values across integration points with other tools. Technically, the workflow executes a single API call to Datto Autotask PSA using the "List Ticket Fields with Picklists" action, retrieving the current priority options configured in your PSA. By centralizing this function, MSPs can maintain consistent priority handling across their entire automation ecosystem while easily adapting if priority configurations change in Autotask.

This workflow contains 1 task.

Inputs

This workflow pulls all company status values from Datto PSA with a single API call, making it a key reference point for automations that depend on client status. MSPs can use it to filter clients, trigger conditional actions, or validate status fields before updates. By returning standardized status options, it avoids hardcoding and keeps automations flexible, even when custom statuses are added, ensuring reliable, status-aware workflows across your PSA environment.

This workflow contains 1 task.

Inputs

• choose_variable

Use case

You want to generate an array of integers from 1 to 100 to use in the With Items field of an action. This will cause the action, such as an API call, to run once for each number in the array. During each run, you can reference the current number using item() and use it to dynamically construct values like usernames. For example, the first run would use "User1", the second "User2", and so on up to "User100".

This workflow acts as a critical building block by querying the SentinelOne platform to retrieve client site information, enabling MSPs to effectively track and manage endpoint security licenses across multiple clients. It delivers essential visibility into license distribution and utilization, which directly supports compliance management, client billing accuracy, and renewal planning for cybersecurity services. The workflow functions by connecting to the SentinelOne API, retrieving a comprehensive list of all managed client sites, and preparing this data for license count analysis in subsequent automation processes. MSPs managing multiple SentinelOne deployments can leverage this automation to eliminate manual license auditing processes, proactively identify licensing gaps, and generate accurate reports for both internal operations and client discussions.

This workflow contains 5 tasks.

Inputs

This sub workflow has no inputs.

This workflow retrieves all available company classification types from Datto Autotask PSA, serving as a foundational building block for more complex automation processes that need to categorize or filter clients. MSPs would find this function valuable when automating client onboarding workflows, implementing classification-based automation rules, or synchronizing client categorization between systems. Technically, the workflow executes a single API call to Datto PSA using the "companies_query_field_definitions" action, which returns the standardized classification options configured in your PSA that can then be used in dropdown menus or conditional logic within other workflows. This reusable component eliminates the need to hardcode classification values, ensuring your automations remain current even when PSA configurations change.

This workflow contains 1 task.

Inputs

This utility workflow collects all integration IDs from your Rewst instance, mapping organizations to their connected systems and Microsoft tenant IDs, serving as a fundamental building block for other automation workflows that need to interact with your integrated PSA, RMM, or Microsoft 365 environments. It's particularly valuable for MSPs when creating cross-platform automation workflows, conducting integration audits, or troubleshooting connection issues where accurate integration identifiers are required. Technically, the workflow retrieves all organizations in your Rewst instance, lists the integrations for each organization, collects relevant organization variables, and specifically identifies Microsoft tenant IDs—creating a comprehensive integration mapping that other workflows can reference when executing actions against specific client environments.

This workflow contains 6 tasks.

Inputs

This sub workflow has no inputs.

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.

1. .

2. Click in the top menu bar of your workflow's workflow builder canvas.

3. Click the Workflow Type drop-down selector.

4. Select Option Generator.

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.

See the documentation for how to use our form builder to achieve this step .

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.

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.

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.

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:

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"

Form organization variables are implemented with specific forms that come from Crates. They can be used to set form_org_vars so that you can have specific default values for fields on a form.

Use case

An API has returned a YAML formatted string and you would like to convert it to a JSON object.

Overview

Parses a YAML string and returns the resulting data structure in JSON.

Parameters

Usage

Results output

Use case

You are working with a list of users, however the users are nested in a list.

You would like to flatten the list of lists so it ends up as a list of objects.

Overview

Flatten a nested List.

Parameters

Usage

Results output

Result of Example:

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.

What is a CORS request?

When referencing a Rewst web hook in JavaScript in an App Builder page— or outside of Rewst— you may see the error TypeError: Failed to fetch.

Transform actions, or transforms for short, are a simplified way to achieve commonly required Jinja filters without writing complex code, while providing flexibility to adapt in the Live Editor for more advanced Rewst users. They offer 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.

What is a webhook trigger?

Webhook triggers are an effective way to kick off a workflow with context from external systems. By sending an API request to a webhook trigger, Rewst will fire the workflow and include any data and or queries included in the request.

Anatomy of a webhook URL