I created a workflow as an example to illustrate my problem (see screenshot above). In this example, I use several webhooks that each receive different data. This data is then processed within the workflow, and I’d like to accumulate it all for processing together.
Problem:
Every time a webhook is triggered, it starts a new execution, and the data from previous webhooks isn’t accessible in that execution.
Question:
How can I configure my n8n workflow so that data from multiple webhook triggers is accumulated and available for processing together, without each new webhook call starting an isolated execution that loses access to previously collected data?
Assuming the multipart form input is not the case here (so multistep n8n forms are not applicable), one viable option is to ensure webhooks are called with an extra bit of information that would allow to identify same session among all competing webhooks invocations. Then storing the received data in a database, and, finally, poll database and implement business logic based on data state and completeness.
This way you’d avoid stale requests and would be able to handle multiple concurrent sessions (invocations by different users) or situations when webhooks are called in a wrong order (e.g. due to network failures).
That’s unfortunately as much as I could theoretize given the amount of context at hands. Maybe someone else will take a look into this with a more robust solution.
But if you find this approach feasible, please mark this post as a Solution.
Solution.