Features

The Core action Sendmail utilizes Rewst branding, but we believe it should be easy to utilize the MSPs logo & primary color instead.

Allow the Confirmation Email action to be customizable: branding, sender, etc.

Allow employees to work within the managing org's workspace to create workflows for clients, but not have access to managing org's tenant.

Sorry if this has been asked, but I couldn't find it which is almost as shocking as it not already existing as a feature. The benefits to Rewst (less developer time) and to the Rewst community would be huge if we could take all the pieces that make up a custom Crate, export it and share it with others. Not 10 separate workflow exports, two form exports and who knows how many scripts, but to be able to bundle it together and share it. I would even highly recommend that Rewst creates a place for Crates to be shared to ensure everyone benefits. Really puzzled how this isn't a feature that is core to the product, even for internal development would be a no brainer?

Feature Request: I would like a way to set up the onboarding/offboarding approval links to instead of being sent to an email to be directly attached to the ticket it creates for the onboarding/offboarding. This is already done with the Pax8 integration, and it would be very helpful for our auditing and keeping track of everything if we can do everything inside our ticketing system. Current Method: We are currently sending the email for approval to our ticketing email, so it creates a ticket in Autotask, we then find that ticket and approve/deny the onboarding/offboarding. This means we have 2 unlinked tickets that are created for the same event. Ideal Method: The ticket created for onboarding/offboarding is directly updated with the approval request. See Pax8 licensing for an example.

We have a bunch of custom integrations that I can see are down as requests already (for things like Cloudflare, ConnectWise Asio/RMM, Backup Radar, Redstor RedApp, Jamf Pro, CloudRadial, etc..) - I'd love to have a place to share these with other MSPs so we can collectively automate the entire world! These "Community Integrations" could be shared with warning that they're not "official" Rewst integrations and may not actively be maintained. If a community integration gains enough traction, it could then become an officially support integration too, with most of the leg work done by the community already.

Make it so that the list of actions auto refresh's once the workflow has been loaded and isn't static. Main use case is when I create a workflow and then plan to have the ability to run it as a single org or multiple. What I typically do is design it for a single org and then clone the workflow and add the cloned version as a sub workflow. Currently you have to refresh the workflow after creating the sub workflow to get it as a selected able action.

Setting up a webhook trigger can sometimes be time consuming and if you need to recreate that same webhook trigger for another workflow, it can be more time consuming beyond that. it'd be nice to have a "bank" of saved custom triggers that can be reused on other workflows, specifically the webhook triggers.

Be able to add an API throttle so if the number of API calls in a given period exceed a certain amount the API calls would be delayed until past that period. HubSpot sets a limit on the number of API calls we can make against it and it would be nice if we could control the amount of calls we are making in a given period so we don't get errors.

There is currently no controls or protections to prevent an internal actor from exporting workflow bundles from Rewst. We would love to see the export function protected by a security role within Rewst to prevent IP theft. We would also like the option of encrypting or password-protecting workflow bundles so that they cannot be used elsewhere without consent. Above all, we would like to see an audit log feature implemented within the platform, focusing on user access and permission changes, export/import requests, etc.