Features

https://api.rewst.io/graphql I would like Access to the Rewst GraphQL API from Rewst. Examples: Pulling down list of Workflows Exporting Workflows List Running Workflows

I would like to create custom actions for existing Rewst supported integrations, just like in Custom Integrations v2. Examples of these are, CW PSA, IT Glue, etc. I realize you can use the Generic API action, however that doesn't scale too well if you need to go back to that action many times. Sure, you can use a workflow for that custom action, but that's not a good solution and is kind of a bypass.

title pretty much say it all

Allow listing completion handlers as an action, this could be helpful when sorting for workflows that should have specific completion handlers and are missing them EX workflows that should be alerting on failure but do not have the completion handler attached.

Rippling is an MSP/IT centric workforce management system with a robust REST API. Would be super helpful to have an integration for this. https://www.rippling.com/ https://developer.rippling.com/documentation/rest-api

This is especially needed when using crate workflows as sub-workflows in a wrapper and the crate workflow is expecting to have the CTX.user.username present

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

Some custom integrations using OAuth stop working after about an hour because access tokens expire and are not refreshed in time. Rewst uses the refresh token only once every 24 hours to obtain a new access token, and as a result, workflows fail once the access token expires. While the workaround of making a periodic request may help keep the token active and trigger a refresh, it would be nice to see a proper fix that handles token refresh automatically based on the token's expiration value.

Ability to rerun bulk workflow executions and other bulk tasks. Workflow breaks for whatever reason, you find out a couple days later, hundreds of reruns needed.

When re-running a workflow, currently you only get the option of re-running the entire thing (and any sub-workflows individually). If you run a hefty workflow and find out you did not adequately prepare a prerequisite (such as org variables), it is sometimes detrimental to re-run the whole flow if it does not have checks for pre-existence of certain items. A solution (that's not just changing how your flows are written) would be to allow selective re-running of tasks in the workflow. The one thing I haven't quite figured out in my head is how to properly deal with context. In the situation I outlined above, you would technically want all context to persist besides the missing pre-requisite so that the workflow functions as intended with the new value. IIRC, the current functionality of re-running does not allow that. This may need to be paired with some sort of context editor before the confirmation of the re-run, but folks smarter than me can probably come up with a cleaner solution.