How to Add a Cooldown Time to Workflows (Anti-Spamming)?

[Bonislaw]

Describe the problem/error/question

Is there a way to add a cooldown period to a workflow, so as to prevent frequent Webhook triggering? Like only allow one successful execution every 10 minutes.

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

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

[EmeraldHerald]

Hi @Bonislaw This is a little tricky with webhooks - can you take a look at this thread and see if maybe this has a solution for you?

Wait for several (if any) webhook events and then trigger workflow

I was wondering whether it was possible to wait for let’s say 1 minute, if the same webhook is triggered more than once, and only then trigger a workflow. I had the issue this morning that a webhook was fired four times (it should’ve only triggered once), and then based on this executed a workflow four times instead of just once. This way I could filter out and account for a malfunctioning of this webhook in the future (it is not intended to fire more than once per day. Thanks!

[Bonislaw]

Thanks for providing this idea. This does seem like a tricky question since this solution introduces many extra factors.