Features

Problem: Currently, checkboxes cannot be dynamically generated from an Options Generator. There is the Multi-Select form field but that's clunky compared to the Radio Buttons in a lot of use cases. Solution: I'd like to see the Checkbox to perform in the same way which Radio Buttons do but allow for multi-select, including the ability for Dynamic Options.

Currently, the form only has an option to select shared mailbox permissions, please add user mailbox section too. Ticket#25735

Currently when an organizations tags are updated it doesn't cause a trigger with the type "Rewst - Managed Organization Updated" to fire. We use tags for many things in REWST up to and including enabling or disabling triggers for certain workflows for organizations or updating cached data in a template.

as a dumb user, I want to put junk in a folder to organize it.

Customer would like an "uninstall crate" button. Desired functionality would allow them to quickly delete all elements unpacked as part of a crate. This is especially important when crates are replaced with new versions. They suggested a wizard that allows the user to view and select all elements of a crate, with a "used in x number of crates" indicator so they could deselect shared sub workflows, and then click "delete all selected."

Problem Description At unpredictable intervals, Webhook Triggers enter a failed or degraded state. When this occurs, the associated workflows stop executing entirely. The main operational issue is that there’s no programmatic or automated way to detect this condition: The only place where the failure is visible is under the Trigger configuration UI, specifically the “External Status” field. There are no alerts, no API surface, no health probe, and no dashboard‑level visibility to indicate that a Trigger is no longer functional. Operational Impact Because this failure mode is silent, the only detection method is manual inspection of each Trigger. Additionally, the only workaround found so far is: Deleting the Webhook Trigger Re‑creating it from scratch This is time‑consuming and error‑prone, especially in environments with many automations. I previously submitted feedback titled “Expose Trigger ‘External Status’ via API”, since having that available programmatically would allow external monitoring and alerting. Until such API support exists, I would like to request an interim solution. Requested Enhancement Please add Import/Export functionality for Webhook Triggers within Rewst. This would allow users to: Quickly recreate a failing Trigger without rebuilding its configuration manually. Reduce recovery time when a Webhook Trigger becomes corrupted or enters an error state. Even without API visibility into Trigger health, this feature would significantly reduce operational overhead and mitigate the impact of Trigger failures. Thanks for considering this improvement.

For auditing purposes we would like detailed audit logs of all actions users take across the platform.

Often, a task fails for some unknown reason (particularly those from integrations) and a simple retry does the trick. However, building a retry loop into every task is quite a hassle and with crate workflows, it means un-syncing or having to use a wrapper workflow and retry the entire crate workflow. Having a built-in task/action retry parameter would help a lot.

As per title, the majority of the time I click "View Results" is just to then load the Context in the Jinja2 Live Editor... would be a nice QoL improvement to have a link to take you straight there from test.

THeres a few sites that we access that have invalid certifications and due to this we cant use the web request function on it. It would be amazing to have an option in the web request block to ignore SSL certs. Kind of like cURL's -k or --insecure option