How to Limit Workflow Triggers in n8n

Open your workflow and click the Schedule Trigger node. Change the Trigger Interval from a short value (like every 1 minute) to a longer one that matches your actual needs. For most polling use cases, every 5 or 15 minutes is sufficient. If you use a Cron expression, update it accordingly. For example, change */1 * * * * to */15 * * * * to run every 15 minutes instead of every minute. Click Execute Workflow to test that the new interval works, then toggle the workflow active.

When a trigger like the Gmail Trigger or RSS Feed returns items you have already processed, you waste executions. Add a Code node after the trigger that checks each item's unique ID against a stored list using n8n's static data. Items already in the list are filtered out. New items are added to the list and passed through. This prevents reprocessing the same email, record, or event twice. The static data persists across executions, so the list survives workflow restarts.

1// Code node — Run Once for All Items
2const staticData = $getWorkflowStaticData('global');
3if (!staticData.processedIds) {
4  staticData.processedIds = [];
5}
6
7const newItems = [];
8for (const item of $input.all()) {
9  const id = item.json.id || item.json.messageId || '';
10  if (id && !staticData.processedIds.includes(id)) {
11    staticData.processedIds.push(id);
12    newItems.push(item);
13  }
14}
15
16// Keep only last 500 IDs to prevent memory growth
17if (staticData.processedIds.length > 500) {
18  staticData.processedIds = staticData.processedIds.slice(-500);
19}
20
21return newItems.length > 0 ? newItems : [];

If a workflow takes longer than the trigger interval, multiple instances can run at the same time, causing race conditions and duplicate processing. To prevent this, click the gear icon on the workflow canvas to open Workflow Settings. Under the Error Handling section, find the Save Execution Progress toggle and enable it. For self-hosted n8n, you can also set the environment variable EXECUTIONS_MODE=queue and configure concurrency limits. On n8n Cloud, use the workflow-level timeout setting to stop runaway executions. Set Timeout Workflow After to a reasonable value like 120 seconds.

If your workflow uses a Webhook trigger and receives bursts of requests, add a Code node that enforces a minimum interval between processed requests. Use static data to store the timestamp of the last processed request. If the current request arrives within the cooldown period, respond immediately with a 429 status and skip further processing. This protects downstream API calls from being overwhelmed by rapid webhook fires.

1// Code node — Run Once for All Items
2const staticData = $getWorkflowStaticData('global');
3const COOLDOWN_MS = 5000; // 5 seconds between processed requests
4const now = Date.now();
5
6if (staticData.lastProcessed && (now - staticData.lastProcessed) < COOLDOWN_MS) {
7  // Too soon — skip this execution
8  return [];
9}
10
11staticData.lastProcessed = now;
12return $input.all();