Question about WorkflowStaticData

[Eduardo_Moscatelli]

Initially,
I imagined getWorkflowStaticData(‘global’) as a temporary storage area for variables for a specific workflow execution. This seemed fantastic because I wouldn’t need to store these variables in an external database. However, to my surprise, it isn’t a global storage area for a specific workflow execution but rather for the entire workflow as a whole. I discovered by accident that getWorkflowStaticData(‘global’) means that all executions manipulate the same variables.

I would like to know if there is a way to have the same functionality as getWorkflowStaticData(‘global’) but specific to a particular workflow execution?

Information on your n8n setup

• n8n version: 1.37.3
• **Database (default: SQLite):cloud
• **n8n EXECUTIONS_PROCESS setting (default: own, main):cloud
• Running n8n via (n8n cloud): cloud
• **Operating system:Mac OS - 14.2.1

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[dkindlund]

Hey @Eduardo_Moscatelli , take a look at this similar discussion, here:

Create/Read/Update/Delete Static Data Node Types

I read about the concept of “static data” within a workflow here: I find it exceptionally odd that I think the only way to perform CRUD operations on “static data” is to use the Code node types in my workflow. If that assumption is true, then you’re forcing users to use many different Code node types throughout a given workflow anytime they want to perform CRUD operations on static data. The problem, though, is that we know that adding Code node types to any workflow is more likely to cause m…

[Eduardo_Moscatelli]

Thanks @dkindlund.

From what I could see in the documentation in detail, the Custom executions data is suitable for storing static variables at the Workflow Execution level. I read the topic you indicated, and there are some very interesting points. I am still in doubt whether, over time, I will have problems with this storage of static variables at the execution level.

Thank you for the help.

[barn4k]

hello @Eduardo_Moscatelli

@Eduardo_Moscatelli

I would like to know if there is a way to have the same functionality as getWorkflowStaticData(‘global’) but specific to a particular workflow execution?

You can access any variable of executed nodes within one execution by default (if you have outputted them). If you mean that you will need only one specific past execution, then there is no build-in method for that. Consider using an external storage (files, dbs, tables, etc)