Add the ability to configure workflow level variables and/or global variables

Feature Requests
, ,
1

The idea is:

I’d like to be able to set variables that would be available at the workflow level scope - so any node inside a workflow would be able to access the data. The motivation for this is two-fold.

My use case:

  1. make it easier to set values that could be used throughout the workflow. I know you can do this using a code node, or set node, but if you have multiple triggers in one workflow, you’d have to configure multiple versions of the set/code node to configure these values
  2. make it easier to migrate nodes from different environments - for example, dev/test/prod. You could essentially copy a workflow from test to prod and the variables that would change would already be configured in the workflow settings so your workflow would need minimal modifications between environments.

I think it would be beneficial to add this because:

It will help the developer story that works in multiple environments and reduce the amount of work it takes to change things like Base URL values for a workflow that uses lots of HTTP requests.

Any resources to support this?

Not yet

Are you willing to work on this?

I would work on this - I’d need some high level pointers to get started but I could certainly work on it.

2

Hey @roemhildtg,

This is exactly why we released the variables feature and the upcoming source control feature is the next stage of that so you can do exactly what you are after. These are global variables though rather than workflow level and they can’t be set from a workflow but for setting a URL you can do that with no problem.

2 Likes
3

Thanks @Jon I was just investigating the new Variables in the 1.x release. Looks like its exactly what, or close enough to what I’m looking for!

1 Like