How to store parameters for later node execution

Hi everyone,

I have been struggling with a workflow we are trying to implement. The workflow gets trigger by a webhook that takes two parameters from the query string. A little validation in a postgres DB happens and depending of the result it will go and execute a stored procedure using those same parameters. Later we have something called the notification layer that will also use those params to send a slack notification and create a Jira ticket. Question I have is, is there a way to save those parameters to later use in a node but preventing the execution of the connected notes? I’m attaching the workflow below:

Question I have is, is there a way to save those parameters to later use in a node but preventing the execution of the connected notes?

Hi @jespinoza, I assume by later you mean in a later (separate) workflow execution? n8n does not offer such functionality beyond the static workflow data (which requires code and won’t work when manually executing your workflow). So your best bet might be to store such data in an external database.

1 Like

Hi @MutedJam thanks for replying. Let me explain myself better, I have two parameters that come from a webhook trigger, those two parameters are used throw the workflow to validate if a few Postgres nodes need to be executed or not using an IF node. The issue I am having is when trying to use those two same params at the end of the workflow to send slack notifications, if I connect them from the webhook trigger to a set or execution data node, several notifications will be sent because there is a link between the webhook and the slack notifications. So I was wondering if there is a way to store data to use in a later node without necessarily linking and executing from the webhook.

Regards,
JC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.