Prevent duplicate webhook executions with AARI idempotency gate

About

Who this template is for This template is for anyone running n8n workflows that receive webhooks and perform side effects such as payments, emails, database inserts, or API calls. Webhook providers commonly use at-least-once delivery. If a webhook request times out or fails, the provider retries the same event. From n8n’s perspective this appears as a new trigger, which can cause the workflow to execute twice. How it works This workflow adds an idempotency check before any side effect runs.