I’m still figuring out n8n and have a rather basic question. I want to have two separate webhooks inside one workflow that get triggered at different times. The first one is started after a registration (workflow first row) and the second one a couple days later, if the user fulfilled certain requirements (workflow second row). A simple example like this:
Does it cause any issues having two different starting points inside one workflow? Or should I rather split up the first and second row into two different workflows?
Hi @Batijko, multiple triggers in a single workflow should be fine. If you have a lot of triggers the workflow might become harder to read but should still work.
It’s just important to know that you won’t be able to access execution data outside your current execution (so if your Webhook 2 node runs it won’t be able to read the data from a previous Webhook 1 run).
Would there be any better solution for this particular workflow? You can imagine the first webhook gets triggered if a customer request a discount code. And after a couple of days whether the discount code is used or not the customer gets the right follow up mail. If everything is in one execution what does n8n do in the days of sending Mail 1 and executing Webhook 2?
What you have will work fine, The workflow will only run when called by the trigger in this case the webhook. Nothing is going to happen in your workflow between the URLs being called it will just be listening and waiting on one of the 2 URLs for the next request.
I have a doubt as you mentioned the webhook will be listening to its events and will trigger its individual flow accordingly.
My doubt is that what if two events happen simultaneously like for example I am having one webhook trigger for Instagram comments and one webhook trigger Facebook page updates.
So in this what if a user comments on Instagram and another user comments on our Facebook page and it happened at the same time, so will the n8n take both events and output as 2 items or how will it work.
I know this is an edge case but I think it is better of to solve this before having every trigger in one workflow.
You’re correct! One node with multiple http methods (i.e. get, post, put …). However, for API/Endpoint paths, i.e. with & without params. e.g. abc.com and abc.com/xyz. One node should be enough but it seems not yet there. Maybe I’m missing something. NMW, thanks for your reply. Happy n8n.
