So when i run this as manual execution, it’s working. When i want to run a automated execution, the pinned data (of the aggregate node) is not recocnized.
How can i acces this pinned data in an automated execution?
Are there any nodes, where i can save it? I did try with a set node, where i did enter it as JSON, but when i ran it, there where alway 2 item coming out of the set node - and it should be only one.
So when i run this as manual execution, it’s working. When i want to run a automated execution, the pinned data (of the aggregate node) is not recocnized.
This is an expected behavior. You may use Set or Code node to “freeze” (substitute) data on production.
How can i acces this pinned data in an automated execution?
You could look into the actual data from the execution in Executions tab.
It is very handy in debugging process.
I did try with a set node, where i did enter it as JSON, but when i ran it, there where alway 2 item coming out of the set node - and it should be only one.
Hard to tell without seeing the actual workflow (I mean the workflow per se, not a screenshot of). Try posting the workflow using </> button and maybe pinning some data in the nodes.
Maybe you have two items at the ingress of Set node therefore it is executed twice.
If anything above helps, please mark this post as a Solution.
Hi @Olek . Thanks for the answer. I did try with the Set node & function node, but with my limited skills, i did not manage to make it work. Here’s the workflow:
So what is it that you try to achieve? In plain words.
What is the problem you try to debug employing “pinned data”?
Also, this fragment will give you a single item as the output. You mentioned you received two items in the output when only one was expected. Is it something that happens in the main workflow that calls the sub-workflow you quoted? Could you post the relevant fragment from the calling workflow?
So, you want to use n8n as a persistent data store?
I think it is not a great idea. n8n is not really designed for this. You may loose your precious data due to a glitch on n8n or by accidental deletion of a node or workflow, or by forgetting to extend the license (and having “unbackuped” workflows lost). Despite the data seemingly present at hand, there is still a ton of things n8n does on the backstage transforming data between nodes so that actual gain may not be there.
Alternatively, you could store your data in a database or as a JSON doc on Google Drive, S3. My personal first choice would be GitHub in this scenario.
Yes, it is an overhead (extra nodes to read the file and extract data) but benefits are also there. The data will be stored reliably, you will be able to edit it using more convenient tools, even have a version of data for testing purpose, it will be reusable and accessible to collaborators when needed.
If you want to “pin” some data temporarily just to figure out what goes wrong, that’s a different story. That is why I asked you what you actually want to achieve with your workflow. You posted a fragment of your workflow but it doesn’t really talk (to me at least).
If you wanted to “pin” the data in production currently actually pinned to Aggregate node, the following would be an equivalent replacement that will work in production:
Is this even close to what you are trying to achieve?
ChatGPT is not notoriously famous in dealing with coding tasks. Try Claude 3.7, Cursor or Copilot, although I’m not sure if they would be able to suggest solutions applicable in n8n context straight away.