# Question about WorkflowStaticData **URL:** \ **Category:** Questions\ **Created:** [May 27, 2024, 4:01pm UTC](https://community.n8n.io/t/question-about-workflowstaticdata/47029 "2024-05-27T16:01:37Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Darien\_Kindlund](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/darien_kindlund/32/62626_2.png) [@Darien\_Kindlund](https://community.n8n.io/u/Darien_Kindlund)\ **Post date:** [May 27, 2024, 6:51pm UTC](https://community.n8n.io/t/question-about-workflowstaticdata/47029/3 "2024-05-27T18:51:54Z")
Hey @Eduardo_Moscatelli , take a look at this similar discussion, here: > [@Create/Read/Update/Delete Static Data Node Types](http://community.n8n.io/t/create-read-update-delete-static-data-node-types/46535): > > 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… --- _[View the full topic](https://community.n8n.io/t/question-about-workflowstaticdata/47029)._