Does the current global variable support dynamic assignment in the process. If it doesn’t work, what modification suggestions do you have
The current modification approach is to find the location where the variables are stored, change const to let, and finally register a listener to call the API.
What are the effects of changing the structure of variables.
You’ll need to be more specific about what variables you are referencing and when and how you want to modify their values.
If you are referring to the $getWorkflowStaticData feature, I would recommend experimenting with some test workflows that set/modify and read values in different scenarios where the workflows are executing concurrently (or not), and see how things behave when you use 'global' vs. 'node' scope. The way n8n manages the scope of these values isn’t documented particularly clearly, so it’s best to run your own tests to see what to expect.