Handling Asynchronous Webhooks with Redis: Waiting for Multiple Events Before Proceeding

[Aurangcool]

Hi everyone, I’m facing a major issue. I have a workflow that involves two webhooks, which are triggered at different times — about 2 minutes apart. One webhook contains the title and description, while the other one carries the MP4 file.

I want to store both webhook payloads in Redis using SET, and only proceed with the workflow once both pieces of data have arrived. I’ve been trying to figure this out for days but haven’t been successful so far.

Does anyone have experience with this kind of setup or any tips on how I could achieve it? I’d really appreciate any help. Thanks in advance!

Share the output returned by the last node

Information on your n8n setup

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Franz]

This is not how N8N works.

Every webhook triggers a new execution. Either the top or the bottom path is executed — but never both in the same run.

One possible solution is using a Wait node.

It’s pretty cool and can be set up to wait for a second webhook call.

However, the webhook URLs are different in every execution.

I built you an example where calling the first webhook returns the URL of the second webhook.

Hope that helps!